Skip to content
ajar.Get started

Verify sign-in code

booking.auth.verify

View connector

Verify sign-in code for a Booking.com account. Development trial; fresh-session live verification is pending. Credentials are sealed into caller-held tokens; the server stores no provider credentials.

POST /v1/connections/booking/verify

Headers

Authorization: Bearer YOUR_CONNECTOR_TOKEN
Content-Type: application/json

Inputs

ParameterExample typeExample value
codestring"ABC123"
continuation_refstring"fictional-continuation"

Example input

{
  "code": "ABC123",
  "continuation_ref": "fictional-continuation"
}

Illustrative response. Keep sealed continuations and account tokens private on your device. Operations use x-booking-token; refresh consumes its separate sealed token.

Example response

{
  "access_token": "YOUR_BOOKING_ACCOUNT_TOKEN",
  "expires_at_epoch_s": 1790814600,
  "refresh_expires_at_epoch_s": 1822350600,
  "refresh_token": "YOUR_BOOKING_REFRESH_TOKEN",
  "token_type": "Bearer"
}
Open JSON schema

Input schema

{
  "additionalProperties": false,
  "properties": {
    "code": {
      "pattern": "^[A-Za-z0-9]{6}$",
      "type": "string",
      "writeOnly": true,
      "x-sensitive": true
    },
    "continuation_ref": {
      "maxLength": 16384,
      "minLength": 1,
      "type": "string",
      "x-sensitive": true
    }
  },
  "required": [
    "continuation_ref",
    "code"
  ],
  "type": "object"
}