booking.auth.sign_in
View connectorRequest 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/sign-inHeaders
Authorization: Bearer YOUR_CONNECTOR_TOKEN
Content-Type: application/jsonInputs
| Parameter | Example type | Example value |
|---|---|---|
| string | "you@example.com" |
Example input
{
"email": "you@example.com"
}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
{
"continuation_ref": "fictional-continuation",
"expires_at_epoch_s": 1790813400,
"interaction": "email-code"
}Input schema
{
"additionalProperties": false,
"properties": {
"email": {
"maxLength": 254,
"minLength": 3,
"type": "string"
}
},
"required": [
"email"
],
"type": "object"
}