Upsert booking

This api can be used to create a booking using external_id as main primary key. ATTENTION: this api will handle multiple request using same external_id. If you send at the same time 2 requests with the same external_id, 2 different bookings will be created. You must handle the true unique constraint of the value.
This api will use external_id as primary key, will ignore id of the booking. If a booking with the external_id is found, will be updated, otherwise will be created. In bookings you need to set a customer_id, in this api setting the booking_customer with the unique uuid will use the reference of the original customer already present.
If customer is not found a new one will be created. Customer constraint must be followed in any case. uuid is always required as well or the company_name or first_name + lastname. If the uuid exists, data of the customer will NOT be overwritten.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

must have customer uuid and external_id

string
required

must use the ISO 8601 standard. In the body of the request it is recommended to use the UTC format. The api response will always use the ISO 8601 standard with the UTC format

booking_customer
object
required
integer
required
string
required

must be unique. Tilby do not check unique contraint on db. First element found will be used.

string
integer
string

must have customer id or pms_reservation_id

string
integer
string
string
enum
required
Allowed:
tables
array of objects
tables
tags
array of objects
tags
Responses

422

Error: Unprocessable Entity

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json