Discussions

Changes in API V1 ?!

over 6 years ago by Thomas BArbut

Hello,

We are pulling some data from the V1 API, which worked fine for a very long time.
Somehow in the last 1-2 months it keeps changing the responses.

Last month it changed the order of the columns in the JSON response.
Example:
Instead of ID, Location, Date we get ID, Date, Location.
We were able to fix this last month.

Now we are facing a new challenge. The employees array within the schedule.shifts response had only one employee before. Now we are having multiple employees in the employees array. (per shift ID)

Are there some recent changes? If so, could be please somehow get an access to the prior version?
We heavily rely on this integration.

over 6 years ago by Isidora Smiljanic

Hi Thomas,

I checked the schedule.shifts response on app version 8.10.0 and there are also multiple employees in the employees array.
That is all I can do with the given information. If you want me to check why you have a problem, please give me your account name and example of the request you send.

Regards,
Isidora

over 6 years ago by Thomas BArbut

This is the call. We didn't have any problems in the past with this call.
Account name: jho@tenging.is is used in the API call.

{
"module": "schedule.shifts",
"method": "GET",
"request": {
"token": "token changed for security reasons",
"start_date": "2018-9-30",
"end_date": "2018-12-31",
"mode": "overview"
}
}

Where can I see the API versions? Maybe any way to access prior versions?
I can say with 100% certainty that it is the first time I see multiple employees in the response.
The code itself written is prepared to handle only 1 employee per shift ID since ~November 2016 and we didn't experience any issues.

over 6 years ago by Thomas BArbut

Isn't there any way we can be unaffected by your changes?
Like defining the API Version in the request so I can get an answer structured exactly like it was before.

over 6 years ago by Aleksandar DjordjevicAdmin

Hello Thomas,

We haven't made any changes to employee array within shifts in the schedule.shifts response, it always returned as many employees as you have on the shift, if you send it without "mode" : "overview" it will return the shifts only for the user who's token you are using. It is the core of our application to have more employees on a single shift.

We do have API v1 and v2 and response will be the same, we don't have older versions of API that you can use.

Thanks

over 6 years ago by Thomas BArbut

Hello Aleksandar,

thanks for the answer.
We'll do some more checks.

best regards,
Thomas Barbut

﻿