Any questions

We are happy to help!

Question about Gecko Booking?

If you are unsure whether Gecko Booking is right for you, or if you have other questions, we would love to hear from you!

All good!
Please enter your name.
All good!
Please enter your email.
All good!
All good!
Please enter your question.

Fields marked with an * are required


Guides

Trin for trin-vejledninger til opsætning og brug af systemet.

Guides - REST API

REST API

Please note! API is disabled on your account by default. Contact GECKO Booking in order to activate it.

The API requires technical insight and is not intended for the average user. We can answer questions to a limited extent, but we do not provide help with developing or troubleshooting your own integrations.


Our REST API makes it possible to read and write to the system from external systems. The complete documentation for the API can be found at https://app.geckobooking.com/api/v1 (the URL must be changed to the server your agreement is placed on).

API keys

API keys are created by a super administrator under Access and security settings on the "API keys" tab. On the key you enter a name and a responsible e-mail address, so that we can contact the responsible person if any questions arise regarding the use of the key. By default the key has access to the entire API, but you can instead choose what the key should have access to, and for each part whether it may read, write or both.

When the key has been created, an API token is shown. Copy it to a safe place, because it cannot be viewed again after the window is closed. The token is sent with every call in the header "Authorization: Bearer <token>". The documentation contains a PHP example.

How to use the API

  • All calls must be made over HTTPS.
  • The API uses the methods GET, POST, PATCH and DELETE. Data is sent and returned as JSON.
  • Lists are returned page by page with "page" (the first page is 0) and "rowsPerPage". By default only the id is returned, so use "fields" to choose the fields you need, for example fields=customerId,customerName.
  • Endpoints for, for example, vouchers and SMS require that the module has been purchased.

Errors

Errors are returned as JSON with an error code: 400 (invalid request), 401 (missing or invalid key, or module not purchased), 403 (the key does not have access, or the update/deletion could not be completed), 404 (the object does not exist) and 429 (too many calls).


Important! If too many calls are sent in a short time, the API responds with the error code 429. Always respect the Retry-After header, which states how many seconds must pass before you try again, and do not send new calls before then.


Creations, changes and deletions made via the API do not trigger our webhooks.


 


Try a Free and Non-Binding Demo of Gecko Booking & Administration

Fill out the form, and you will receive a demo as soon as possible.

All good!
Please enter the company name.
All good!
Please enter your phone number.
All good!
Please enter your name.

Fields marked with an * are required