' 'https://api.worldota.net/api/b2b/v3/hotel/order/booking/finish/status/' \
--header 'Content-Type: application/json' \
--data '{
"partner_order_id": "0b370500-5321-4046-92c5-5982f1a64fc6"
}'
```
## Request body
- **partner_order_id** *(String, required)*
The unique partner booking ID.
> [!NOTE]
> * The minimum length is `1` character.
> * The maximum length is `256` characters.
## Response
[//]: # (data_3ds)
- **data_3ds** *(Object)*
The 3D Secure check information.
-
action_url (String)
The URL of a new request for the 3D Secure check.
Must have the data object field as the query parameter.
-
data (Object, optional)
The 3D Secure check information that should be sent back.
-
MD (String, optional)
The payment session ID returned by the card issuer.
-
PaReq (String, optional)
The 3D Secure request data for the issuer.
> [!NOTE]
> The line breaks in the value must be retained in all requests. Otherwise, the transaction will be declined.
-
TermUrl (String, optional)
The URL of the merchant site page to redirect the user to after completing 3D Secure check on the card issuer site.
> [!NOTE]
> * The maximum length is `1024` characters.
-
method (String)
The HTTP method of sending the information.
> [!NOTE]
> * The possible values:
> * `get`.
> * `post`.
[//]: # (partner_order_id)
- **partner_order_id** *(String)*
The external booking ID in the [UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)
format.
The ID remains the same if you cancel a booking that:
- Is successful.
- Is failed.
- Has the fail status response from the [Check booking process](/docs/b2b-api/booking/check-booking-process/)
call.
Use this field for the rest of the booking calls.
> [!NOTE]
> * The value should be unique for the order within the same contact.
> * The minimum length is `3` character.
> * The maximum length is `256` characters.
[//]: # (percent)
- **percent** *(Int, deprecated)*
The order confirmation percentage.
All current statuses are described in the [Result interpretation](/docs/affiliate-api/booking/check-booking-process/#result-interpretation)
section.
The ok status in the response indicates that the order is confirmed.
## Response example
```json
{
"data": {
"data_3ds": null,
"partner_order_id": "0b370500-5321-4046-92c5-5982f1a64fc6",
"percent": 100
},
"debug": null,
"error": null,
"status": "ok"
}
```
## Errors
The `error` field has the value specified in the headers below.
### `block`
The card funds can’t be frozen (blocked) for the booking payment.
### `charge`
The card funds can’t be withdrawn for the booking payment due to:
* A failed freeze.
* Another reason.
### `3ds`
The `MD` field value is invalid.
### `soldout`
The rate is no longer available as its rooms are sold out.
### `book_limit`
The cut-off logic limit for the booking finishing is reached.
### `not_allowed`
There is no permission to use this call for this contract:
1. Contact the API support team.
1. Tell the user the booking error has occurred.
When contacting the API support team, provide at least:
* The hotel name where the booking is in process.
* The `order_id` field with the value from the [Create booking process](/docs/b2b-api/booking/create-booking-process/) call.
* The `user` and `rooms` fields with the values from the [Start booking process](/docs/b2b-api/booking/start-booking-process/) call.
This information will help to identify the request attempt.
### `provider`
A technical error at the rate provider side.
### `order_not_found`
The order with the `partner_order_id` field value isn’t found. Try to change the value.
### `booking_finish_did_not_succeed`
An attempt to request this call without a successful response from the [Start booking process](/docs/b2b-api/booking/start-booking-process/) call.
### `timeout`, `unknown`, and `5xx`
An internal error. Continue to request this call until you get the following response:
* The `status` field has the `ok` value.
* The `error` field has one of the values:
* `3ds`.
* `block`.
* `book_limit`.
* `booking_finish_did_not_succeed`.
* `charge`.
* `decoding_json`.
* `endpoint_exceeded_limit`.
* `endpoint_not_active`.
* `endpoint_not_found`.
* `incorrect_credentials`.
* `invalid_auth_header`.
* `invalid_params`.
* `lock`.
* `no_auth_header`.
* `not_allowed`.
* `not_allowed_host`.
* `order_not_found`.
* `overdue_debt`.
* `provider`.
* `soldout`.
* `unexpected_method`.
> [!NOTE]
> The requests should be sent within the agreed booking timeout.
## Error Handling Diagram
Below is a sequence diagram describing how to handle errors during the booking check process:
```mermaid
sequenceDiagram
participant User
participant API
User->>API: Check booking process
alt status == "ok"
API-->>User: Booking is successfully confirmed
else status == "processing" or error is (timeout/unknown) or HTTP status code 5xx
loop Wait and poll (until status is "ok", final error, or booking timeout reached)
User->>API: Check Booking Process
alt status == "ok"
API-->>User: Booking is successfully confirmed
User->>User: Stop polling
else status == "processing" or error is (timeout/unknown) or HTTP status code 5xx
API-->>User: Still processing or transient error, continue polling
else status is final error (e.g., soldout, provider, book_limit) or booking timeout reached
API-->>User: Return final error or booking timeout
User->>User: Stop polling, show error
end
end
else status is final error (e.g., soldout, provider, book_limit) or booking timeout reached
API-->>User: Return final error or booking timeout
User->>User: Stop, show error
end
```