APapaleo
Authorization

Creates the authorization based on an existing pre-authorization created prior directly with the payment service provider

Creates the authorization based on an existing pre-authorization created prior directly with the payment service provider. For the pre-authorization, please ensure to set the respective metadata in the original authorization request. The flow type has to be set to <i>BlockNHold</i>. For more information, please refer to the documentation of <a href="https://apaleo.dev/guides/pay-integration/authorizations" target="_blank">how to do an authorization hold for future charges</a>.<br>You must have this scope: 'authorizations.manage'.<br>For fine-grained clients, you must have this permission: 'core.authorizations.create'.

post/booking/v0-nsfw/authorizations/by-authorization

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/v0-nsfw/authorizations/by-authorization
  • 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

transactionReferencestring required

Reference to the original authorization transaction

Example request

{
  "target": {
    "type": "Booking",
    "id": "KYKXKLWL",
    "propertyId": "MUC"
  },
  "amount": {
    "amount": 150,
    "currency": "EUR"
  },
  "transactionReference": "K9DTTJQD4HNG5S82"
}

Response

Authorization was created and will be processed

idstring required

Created authorization id

Example response

{
  "id": "HDQFGFOS"
}

Changes

No operation changes recorded.