https://crm.ohrana.ua/
Orders are not coming from Rosetka, today at 09-04 there is an order from Rosetka, but it has not been received in Box. integration settings were not changed
https://crm.ohrana.ua/ Orders are not coming from Rosetka, today at 09-04 there is an order from Rosetka, but it has not been received in Box. integration settings were not changed
Good afternoon. The problem is with the api socket. They removed the authorization tokens, although they were supposed to store them for 24 hours. Perhaps something has changed in the API and the tokens now live less, I look at the information in their API
Good afternoon. The problem is with the api socket. They removed the authorization tokens, although they were supposed to store them for 24 hours. Perhaps something has changed in the API and the tokens now live less, I look at the information in their API
The API receives a token but receiving orders with this token gives an error on the socket side Array ( [success] => [errors] => Array ( [message] => incorrect_access_token [code] => 1020 [description] => Invalid access token [details] => ) ) The outlet replied that it had changed the token generation algorithm, and since we store it 24 hours a day, the old token had been used for the last day and the processes were not working. Updated the token for you.
The API receives a token
but receiving orders with this token gives an error on the socket side
Array
(
[success] =>
[errors] => Array
(
[message] => incorrect_access_token
[code] => 1020
[description] => Invalid access token
[details] =>
)
)
The outlet replied that it had changed the token generation algorithm, and since we store it 24 hours a day, the old token had been used for the last day and the processes were not working.
Updated the token for you.
this is because I flushed the cache of your socket authorization token The documentation says: To work with the API, you use the login and password that were issued to you to access the Personal account. After successful authorization, you receive a temporary token (validity period - 24 hours) using which you can access all requests. Bearer token authorization type should be used for token authorization. That. we received a token, we use it for 24 hours, but the socket itself does not accept it, writes [message] => incorrect_access_token. Maybe they somehow cleared everyone's access tokens yesterday/today. Check the information with their technical staff. support Kosyak is clearly not on our side.
[quote]
Shatokhina Iryna wrote:
only that the order came
[/quote]
this is because I flushed the cache of your socket authorization token
The documentation says:
To work with the API, you use the login and password that were issued to you to access the Personal account. After successful authorization, you receive a temporary token (validity period - 24 hours) using which you can access all requests. Bearer token authorization type should be used for token authorization.
That. we received a token, we use it for 24 hours, but the socket itself does not accept it, writes [message] => incorrect_access_token. Maybe they somehow cleared everyone's access tokens yesterday/today. Check the information with their technical staff. support Kosyak is clearly not on our side.
Ustimenko Igor OneBox production wrote: The API receives a token but receiving orders with this token gives an error on the socket side Array ( [success] => [errors] => Array ( [message] => incorrect_access_token [code] => 1020 [description] => Invalid access token [details] => ) ) The outlet replied that it had changed the token generation algorithm, and since we store it 24 hours a day, the old token had been used for the last day and the processes were not working. Updated the token for you.
WE HAVE THE SAME PROBLEM. ORDERS WILL NOT BE ACCEPTED
[quote]
Ustimenko Igor
OneBox production wrote:
The API receives a token
but receiving orders with this token gives an error on the socket side
Array
(
[success] =>
[errors] => Array
(
[message] => incorrect_access_token
[code] => 1020
[description] => Invalid access token
[details] =>
)
)
The outlet replied that it had changed the token generation algorithm, and since we store it 24 hours a day, the old token had been used for the last day and the processes were not working.
Updated the token for you.
[/quote]
WE HAVE THE SAME PROBLEM. ORDERS WILL NOT BE ACCEPTED
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Donate
You don't have enough funds in your account Top up