For AI agents: markdown of this page — /docs-content-en/entities/booking-resource-types/get.md documentation index — /llms.txt

Get: Booking resource types

GET /v1/booking-resource-types/:id

Returns a booking resource type by its identifier: name, code and the settings for client messages about bookings.

Parameters

Parameter Type Required Description
Parameterid (path) Typenumber Requiredyes DescriptionType identifier. List: GET /v1/booking-resource-types

Examples

curl — personal key

Terminal 
curl "https://vibecode.bitrix24.com/v1/booking-resource-types/31" \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

Terminal 
curl "https://vibecode.bitrix24.com/v1/booking-resource-types/31" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"

JavaScript — personal key

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/booking-resource-types/31', {
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})

const { data } = await res.json()
console.log(data.name, data.code)

JavaScript — OAuth application

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/booking-resource-types/31', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

const { data } = await res.json()
console.log(data.name, data.code)

Response fields

The is*NotificationOn switches are always true or false in the response, even if the strings "Y" / "N" were passed on write. Delays are in seconds.

Field Type Description
Fieldsuccess Typeboolean Descriptiontrue on success
Fielddata.id Typenumber DescriptionType identifier. Pass it in typeId when creating a booking resource
Fielddata.code Typestring DescriptionSymbolic code of the type, unique among the types of the Bitrix24 account
Fielddata.name Typestring DescriptionType name
Fielddata.senderCode Typestring | null DescriptionService that sends messages to the client, for example bitrix24. null — not set
Fielddata.isInfoNotificationOn Typeboolean DescriptionBooking info message to the client
Fielddata.isConfirmationNotificationOn Typeboolean DescriptionBooking confirmation request
Fielddata.isReminderNotificationOn Typeboolean DescriptionBooking reminder
Fielddata.isFeedbackNotificationOn Typeboolean DescriptionFeedback request
Fielddata.isDelayedNotificationOn Typeboolean DescriptionMessage to a client who is running late
Fielddata.isCancellationNotificationOn Typeboolean DescriptionBooking cancellation message to the client
Fielddata.infoNotificationDelay Typenumber | null DescriptionHow many seconds after the booking is made to send the booking info message
Fielddata.confirmationNotificationDelay Typenumber | null DescriptionHow many seconds before the booking to send the first confirmation request
Fielddata.confirmationNotificationRepetitions Typenumber | null DescriptionHow many times to repeat the confirmation request, not counting the first one
Fielddata.confirmationNotificationRepetitionsInterval Typenumber | null DescriptionInterval between repeats of the confirmation request
Fielddata.confirmationCounterDelay Typenumber | null DescriptionHow many seconds before the booking an unconfirmed booking enters the counter
Fielddata.reminderNotificationDelay Typenumber | null DescriptionHow many seconds before the booking to send the reminder. -1 — on the morning of the booking day
Fielddata.delayedNotificationDelay Typenumber | null DescriptionAfter how many seconds of lateness to send the message to the client
Fielddata.delayedCounterDelay Typenumber | null DescriptionAfter how many seconds of lateness the booking enters the calendar counter
Fielddata.cancellationNotificationDelay Typenumber | null DescriptionDelay of the booking cancellation message
Fielddata.templateTypeConfirmation Typestring DescriptionConfirmation request template: inanimate, animate, inanimate_long
Fielddata.templateTypeReminder Typestring DescriptionReminder template: base
Fielddata.templateTypeFeedback Typestring DescriptionFeedback request template: inanimate, animate
Fielddata.templateTypeDelayed Typestring DescriptionLate-arrival message template: inanimate, animate

Response example

JSON 
{
  "success": true,
  "data": {
    "id": 31,
    "code": "master",
    "name": "Technicians",
    "senderCode": null,
    "isInfoNotificationOn": false,
    "isConfirmationNotificationOn": false,
    "isReminderNotificationOn": false,
    "isFeedbackNotificationOn": false,
    "isDelayedNotificationOn": false,
    "isCancellationNotificationOn": false,
    "infoNotificationDelay": null,
    "confirmationNotificationDelay": 86400,
    "confirmationNotificationRepetitions": null,
    "confirmationNotificationRepetitionsInterval": 10800,
    "confirmationCounterDelay": 10800,
    "reminderNotificationDelay": -1,
    "delayedNotificationDelay": 300,
    "delayedCounterDelay": 300,
    "cancellationNotificationDelay": 600,
    "templateTypeConfirmation": "inanimate",
    "templateTypeReminder": "base",
    "templateTypeFeedback": "inanimate",
    "templateTypeDelayed": "inanimate"
  }
}

Error response example

404 — no type with this id:

JSON 
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "Booking record not found"
  }
}

Errors

HTTP Code Description
HTTP404 CodeENTITY_NOT_FOUND DescriptionNo type with this id
HTTP400 CodeINVALID_PARAMS Descriptionid is not a positive integer. Message id must be a positive safe integer
HTTP401 CodeMISSING_API_KEY DescriptionThe X-Api-Key header is not passed
HTTP401 CodeTOKEN_MISSING DescriptionThe key has no Bitrix24 tokens
HTTP403 CodeSCOPE_DENIED DescriptionThe key does not have the booking scope
HTTP429 CodeRATE_LIMITED DescriptionRequest rate exceeded. The effective cap is in the x-ratelimit-limit header
HTTP502 CodeBITRIX_RESPONSE_INVALID DescriptionBitrix24 returned a card of an unexpected shape

Full list of common API errors — Errors.

Known specifics

The type's resources come from a separate request. The type card does not list its resources. To get them, call GET /v1/booking-resources?typeId=31.

The booking message template is not returned in the card. Create and update accept the templateTypeInfo field, but the card does not include it. The current template cannot be read through the API.

See also