# Reconciliation API

Generate and download financial reconciliation reports for your properties. Use the Reconciliation API to request payout reports for a specified date range and set of properties, check the report generation status, and retrieve the available filter and configuration options.

Version: 1.0

## Servers

Test using live endpoint
```
https://payments-api.booking.com/
```

## Security

### bearerAuth

Bearer token for authentication. Use your API credentials to obtain a token.

Type: http
Scheme: bearer

## Download OpenAPI description

 - [Reconciliation API](https://developers.booking.com/_bundle/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification.yaml)

## Reconciliation reports

 - [POST /connectivity-payments/recon-reports](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/reconciliation-reports/generatereconreport.md): Initiates the asynchronous generation of a financial reconciliation report for one or more properties within a specified date range. The report is generated asynchronously. The response returns a `req
## Report status

 - [GET /connectivity-payments/recon-reports/{request-id}](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/report-status/getreconreportstatus.md): Retrieves the current processing status of a reconciliation report generation request. Poll this endpoint after calling the [generate report endpoint](#tag/Reconciliation-reports) until `status` is `R
## Report filters

 - [GET /connectivity-payments/recon-reports/filters](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/report-filters/getreconreportfilters.md): Retrieves the available filter and configuration options for generating reconciliation reports for a given legal entity. Use the returned values to populate `report_configurations` and `report_filters
## About Try it

 - [Environment](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/environment.md): ## Environment You can select between two different environments (top right corner in the UI): **Mock (schema only) (default)**: - Helps to understand the response data schema - Recommended for all wr
 - [Request](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/request.md): ## Request 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
 - [Response](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/response.md): ## Response The Try it feature provides comprehensive response information to the extent supported by the OpenAPI specification:
 - [Status code](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/status-code.md): ### Status code - **2xx**: Success responses (200) - **4xx**: Client errors (400 Bad Request, 401 Unauthorized, 404 Not Found) - **5xx**: Server errors (500 Internal Server Error)
 - [Response body](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/response-body.md): ### Response body - JSON formatted response data If the returned response, by default, is unformatted, select the supported Response body format in the UI.
 - [Response headers](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/response-headers.md): ### Response headers - Content-Type, Content-Length.
 - [Environments](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/environments.md): ## Environments The **Environments** tab allows you to create variables specific to the environment. For example, you can add a variable to hold the value of the `propertyId` placeholder. The portal i
 - [Variables](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/variables.md): ### Variables Most of the endpoints (especially POST/PUT/PATCH/DELETE) require you to add a path or query parameter before sending the request. Path parameters use single braces in the OpenAPI specifi
 - [Path parameters](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/path-parameters.md): #### Path parameters - **Required**: Must be provided to make the request - **Type validation**: Ensures correct data types (integer, string, etc.) - **Example**: `propertyId` in `/properties/{propert
 - [Query parameters](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/query-parameters.md): #### Query parameters - **Optional**: Usually have default values - **Example**: `language_code` with `en-us` as the default value
 - [Request body](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/request-body.md): #### Request body - **Schema validation**: Follows OpenAPI schema definitions - **Example data**: Prepopulated with sample values
 - [Best practices](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/best-practices.md): ## Best practices This section provides some basic practice guidelines.
 - [Authentication](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/authentication.md): ### Authentication - Always use separate machine accounts for test properties vs. properties in production. - When testing with the production endpoint, make sure to use only test properties.
 - [For Read operations (GET)](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/for-read-operations-(get).md): ### For Read operations (GET) - GET requests are non-mutating, but use authorised test properties when testing against the production endpoint. - Use valid IDs that exist in your system - Check respon
 - [For Write operations (POST, PUT, PATCH)](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/for-write-operations-(post-put-patch).md): ### For Write operations (POST, PUT, PATCH) - **Always use Mock (schema only) environment first** - Verify request payload structure - Check response for success confirmation - Test error scenarios wi
 - [For Delete operations (DELETE)](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/for-delete-operations-(delete).md): ### For Delete operations (DELETE) - **Preferable to use Mock (schema only) environment only** - Understand the operation is irreversible - Have backup data when testing using test properties
 - [Troubleshooting](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/troubleshooting.md): ## Troubleshooting
 - [Common issues](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/common-issues.md): ### Common issues **401 Unauthorized** - Check authentication credentials - Verify token is valid and not expired - Ensure credentials match the selected environment **400 Bad Request** - Validate re
 - [Getting help](https://developers.booking.com/connectivity/docs/openapispecs/reconciliation-api/reconciliation-api-specification/about-try-it/getting-help.md): ### Getting help If you encounter issues: 1. Check the response error message for details 2. Verify your request matches the API specification 3. Contact the Connectivity Team for support --- *Thi