[#1112] API seems to not work

API General
,
1

Migrated from Redmine #1112 | Author: Sjors sjors
Status: New | Priority: Immediate, there is BUG! | Created: 2023-10-04

We can authenticate and retrieve a authentication token but after that all API endpoints are throwing a 403 forbidden. We tried to create a new user account as well to authenticate with the API but that also doesn’t solve the issue. Can you please have a look to see if the API is functioning? As we tried everything from our end.

2

Sjors sjors wrote:

The API worked fine until this morning where it started throwing 403 forbidden for all API endpoints. What we have tried so far is:

  • Disabled and Enabled again the API custom feature
  • Created a new account with admin privileges and tried to authenticate with that
  • Making sure that we use the right company name, username and password in order to retrieve an authentication token (which works) but after that we receive a 403 forbidden error for all endpoints we are trying to interface with

Let me know if you need any additional information. I tried to contact the Simplybook support chat as well and they told me to open a support ticket here as well. Currently our production environment is impacted hence the IMMEDIATE support request. Thank you.

3

Redmine Admin wrote:

please provide you company login and API endpoint you are using

4

Sjors sjors wrote:

Company login: laraisondelamusique
API endpoint: https://user-api-v2.simplybook.me/admin/bookings

5

Redmine Admin wrote:

you are on EU server, please use https://user-api-v2.simplybook.it/admin/bookings
there are 3 reasons why to use it:

  1. No transfer of data outside EU
  2. faster response
  3. no problems because of possible network issues
6

Sjors sjors wrote:

Legend! That seems to be working (for now). Is this a recent change? We followed the documentation which tells us to use the .me API endpoint. It would be good to update the documentation if EU users should be using the .it API endpoint (if not already). We will continue monitoring it from our side and will let you know if we experience any issues, but so far so good.

Appreciate the quick reply and assistance.

7

Redmine Admin wrote:

this is very old change however it seems you are very old user and registered before it was 100% clear.
We are doing upgrade of servers today and issue with cache caused this for some part of EU users who are using US (.me) endpoint.
We apologize for the inconvenience

8

Sjors sjors wrote:

Thank you. Would it be possible to fully migrate our environment to the EU servers? We will make sure to use the .it endpoints across all our integrations as well.

9

Redmine Admin wrote:

you are on EU servers already, .me API endpoint is working for both EU and US servers.