Skip to content
Contracting API
/
/
Response

Contracting API (1.0.0)

Use the Contracting API to invite a new partner on Booking.com, check whether a partner has signed the contract, resend invitation mail and retrieve the legal entity of the partner.

Authentication

The Contracting API supports token-based authentication. Each request must have an Authorization header containing a JWT token. Manage your machine accounts in the Connectivity Portal. See also the Authentication page of the documentation.

Message formats

The Contracting API accepts and returns JSON.

Documentation

Read the Contracting API documentation for more details about working with this API.

Download OpenAPI description
contracting-api-specificaion.json
contracting-api-specificaion.yaml
Languages
Servers
Test static response
https://developers.booking.com/_mock/connectivity/docs/openapispecs/contracting-api/contracting-api-specificaion
Test using live endpoint
https://supply-xml.booking.com/contracts-api

Manage contracts

Create, update or resend contract details.

Operations

Request access

Request access to existing partner.

Operations

About Try it

Learn how to effectively use the Try it feature in the Contracting API documentation.

Use the Try it feature to send test request examples to the API endpoints directly from the developer portal and depending on the selected environment either see static, pre-built responses or dynamic responses from a test property.

Request

Using the UI, toggle between Edit and Preview tabs to see the values applied to the path or query placeholders (if there are any). You can also click on any unresolved placeholders to add a value or edit an existing placeholder value.

The portal loads the default request body. Where the specification supports multiple request body examples (for example: Rooms API POST endpoint), you can choose a different request body from the drop-down list.

Some helpful pointers before running a request:

  • Authentication (when using live endpoint): Configure your authentication headers

    • API Key or OAuth token as required. Use the Environments tab.
    • Make sure to manage separate machine accounts for test vs. properties in production.
    • Ensure credentials match your selected environment.

  • Parameters: Fill in required parameters

    • Path parameters (like propertyId)
    • Query parameters (like language_code)
    • Request body for POST/PUT operations

  • Execute: Click Send to send the request

    • The request is sent to the selected environment
    • When sending requests to the live endpoint, real HTTP request is made to the API

Response

The Try it feature provides comprehensive response information to the extent supported by the Open API specification:

Status code

  • 2xx: Success responses (200)
  • 4xx: Client errors (400 Bad Request, 401 Unauthorized, 404 Not Found)
  • 5xx: Server errors (500 Internal Server Error)