---
title: "Check Payments by Booking configuration request status"
method: POST
path: "/connectivity-payments/pbb/configurations/status"
tags: ["Payments by Booking configurations status"]
---

# Check Payments by Booking configuration request status

`POST /connectivity-payments/pbb/configurations/status`

Checks the processing status of Payments by Booking configuration update requests for given property IDs or a request ID.

## Headers

- `accept-version` string

## Request body

- PBBConfigurationUpdateStatusRequest
  - `property_ids` integer[], required — <=10 property IDs per request. All `property_ids` in a request should belong to a common legal entity ID. Required if `request_id` is not provided. Set to empty array if using `request_id`.
  - `request_id` string, nullable, required — Identifier of the accepted configuration request. Required if `property_ids` is not provided. Set to null if using `property_ids`.
  - `kyc_callback_url` string, required — Callback URL where the user is redirected after completing pending actions (e.g. KYC submission).

## Response `200`

Request accepted for processing

- PBBConfigurationUpdateStatusLookupResponse — Response of Payments by Booking configurations update request with property-level processing status of accepted configuration change request.
  - `meta` DefaultMeta — Metadata for the response
    - `ruid` string — Request unique identifier
  - `data` PBBConfigurationUpdateStatusLookupDetails — Information regarding accepted Payments by Booking configuration update request status for properties
    - `config_update_details` PBBConfigurationUpdateStatusLookupDetail[] — Status information for accepted Payments by Booking configuration change requests for properties
      - `property_id` string — Property identifier
      - `request_id` string — Idempotency key of the latest accepted Payments by Booking configuration change request
      - `status` string — Payments by Booking configuration change status for property
      - `rejection_reason` string — Reason for rejection of Payments by Booking configuration change request
      - `requested_at` string — Payments by Booking configuration change requested at
      - `actions` Action[] — Pending actions to be performed by the partner
        - `reference` string — Reference to the action to be taken
        - `type` string — Type of action to be taken. Possible values: SUBMIT_KYC.
  - `errors` unknown[]
    - unknown
  - `warnings` unknown[]
    - unknown

## Other responses

- `400` — Invalid request payload.
- `401` — Unauthorized. Missing or invalid authentication token.
- `403` — Access Denied!
- `404` — The request id not found.
- `429` — Rate limit exceeded. Maximum 30 requests per minute.
- `500` — The request failed with an internal server error.

---

[API](https://skmtc.net/booking/apis/payments-by-booking-onboarding-api.md) · [All operations](https://skmtc.net/booking/apis/payments-by-booking-onboarding-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/booking/payments-by-booking-onboarding-api/revisions/16927ccf878d/schema)