APapaleo
Authorization

Creates authorization by using a previously created payment account

Changed on

<br>You must have this scope: 'authorizations.manage'.<br>For fine-grained clients, you must have this permission: 'core.authorizations.create'.

post/booking/v1/authorizations/by-payment-account

Request

  • Base URL
    https://api.apaleo.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.apaleo.com/booking/v1/authorizations/by-payment-account
  • Auth
    OAuth 2
    Implicit: https://identity.apaleo.com/connect/authorize
    Scopes: authorizations.manage, admin

Headers

Idempotency-Keystring

Unique key for safely retrying requests without accidentally performing the same operation twice. We'll always send back the same response for requests made with the same key, and keys can't be reused with different request parameters. Keys expire after 24 hours.

Request body

accountOwner'Guest' | 'Booker'

Account owner of the payment account, default is Guest. Will be ignored if PaymentAccountId is provided. - <b>DEPRECATED: AccountOwner is deprecated, use PaymentAccountId instead. This field will be removed on May 15, 2026. From this date onwards, PaymentAccountId will be a required parameter.</b>

paymentAccountIdstring nullable

Optional payment account id. If passed, it is verified that the provided payment account is available for the target. From Feb 15, 2026 onwards, PaymentAccountId will be a required parameter.

Example request

{
  "target": {
    "type": "Booking",
    "id": "KYKXKLWL",
    "propertyId": "MUC"
  },
  "amount": {
    "amount": 150,
    "currency": "EUR"
  },
  "accountOwner": "Guest",
  "paymentAccountId": "UBMFXUFH"
}

Response

Authorization was created and will be processed

idstring required

Created authorization id

Example response

{
  "id": "HDQFGFOS"
}

Changes