Check travelers for trips already planned in a period

Reports, per traveler, whether they already have an active trip of the same type whose dates overlap start_date–end_date, and that trip's dates. A trip of another type (a business trip during an assignment) does not count, and a trip may start or end on a day another one starts or ends. A business trip longer than three months and a shorter business trip never count against each other, whichever is planned; two such long stays do, and assignments and workations always do. Creating the trip would be refused with OVERLAPPING_TRIP until the booker confirms it with acknowledgeOverlap. Travelers outside the caller's booking scope are refused with 403, as on POST /trips/multiple. Read-only — creates nothing.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
values
object
required

Draft trip values keyed by field; only start_date and end_date are read. Keys are your company's trip-field keys — discover them with GET /trip-fields; they are per-company and must not be copied from an example.

travelerIds
array of numbers
required

Travelers to check. Ids outside the caller’s company are reported as not overlapping. Capped at 100.

travelerIds*
string
enum

Type of the trip being planned. Only existing trips of this type are reported. Omitted: every type counts.

Allowed:
Responses

403

A traveler is outside the caller’s booking scope.

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json