Manage booking
- : Read-only access to view booking details.
XONE API Access Token
To get started with the XONE API, you'll first need to obtain an access token. This token acts as a digital key, granting your application permission to make API calls.
This process uses the OAuth 2.0 Client Credentials Grant flow. You'll use your unique client ID and client secret to request a token, which you then include in subsequent API requests.
🔑 Authentication Steps
- Request Token: Send a "Retrieve Token" request to the XONE authorization server's token endpoint.
- Include Credentials: In the request body, provide your
client_idandclient_secretas a JSON object. - Use Token: The server will respond with an
access_tokenthat you can now use to authenticate your API calls by including it in the Authorization header as aBearertoken.
200 OK
401 Unauthorized
- : Permission to modify existing bookings.
XONE API Access Token
To get started with the XONE API, you'll first need to obtain an access token. This token acts as a digital key, granting your application permission to make API calls.
This process uses the OAuth 2.0 Client Credentials Grant flow. You'll use your unique client ID and client secret to request a token, which you then include in subsequent API requests.
🔑 Authentication Steps
- Request Token: Send a "Retrieve Token" request to the XONE authorization server's token endpoint.
- Include Credentials: In the request body, provide your
client_idandclient_secretas a JSON object. - Use Token: The server will respond with an
access_tokenthat you can now use to authenticate your API calls by including it in the Authorization header as aBearertoken.
200 OK
401 Unauthorized
422 Unprocessable Entity
- : Permission to cancel bookings.
XONE API Access Token
To get started with the XONE API, you'll first need to obtain an access token. This token acts as a digital key, granting your application permission to make API calls.
This process uses the OAuth 2.0 Client Credentials Grant flow. You'll use your unique client ID and client secret to request a token, which you then include in subsequent API requests.
🔑 Authentication Steps
- Request Token: Send a "Retrieve Token" request to the XONE authorization server's token endpoint.
- Include Credentials: In the request body, provide your
client_idandclient_secretas a JSON object. - Use Token: The server will respond with an
access_tokenthat you can now use to authenticate your API calls by including it in the Authorization header as aBearertoken.
200 OK
401 Unauthorized
422 Unprocessable Entity
- : Permission to modify existing bookings.
XONE API Access Token
To get started with the XONE API, you'll first need to obtain an access token. This token acts as a digital key, granting your application permission to make API calls.
This process uses the OAuth 2.0 Client Credentials Grant flow. You'll use your unique client ID and client secret to request a token, which you then include in subsequent API requests.
🔑 Authentication Steps
- Request Token: Send a "Retrieve Token" request to the XONE authorization server's token endpoint.
- Include Credentials: In the request body, provide your
client_idandclient_secretas a JSON object. - Use Token: The server will respond with an
access_tokenthat you can now use to authenticate your API calls by including it in the Authorization header as aBearertoken.
200 OK
401 Unauthorized
422 Unprocessable Entity
- : Permission to cancel bookings.
XONE API Access Token
To get started with the XONE API, you'll first need to obtain an access token. This token acts as a digital key, granting your application permission to make API calls.
This process uses the OAuth 2.0 Client Credentials Grant flow. You'll use your unique client ID and client secret to request a token, which you then include in subsequent API requests.
🔑 Authentication Steps
- Request Token: Send a "Retrieve Token" request to the XONE authorization server's token endpoint.
- Include Credentials: In the request body, provide your
client_idandclient_secretas a JSON object. - Use Token: The server will respond with an
access_tokenthat you can now use to authenticate your API calls by including it in the Authorization header as aBearertoken.
200 OK
401 Unauthorized
422 Unprocessable Entity
Last updated