Check travelers against their policy’s advance-notice period

Reports, per traveler, whether the matched policy's advance-notice period (gracePeriod) would reject start_date. Creating the trip would be refused with WITHIN_GRACE_PERIOD. The date picker cannot answer this when booking for colleagues: it greys dates by the caller's own policy. 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; destination and start_date (YYYY-MM-DD) are required for this check, the rest feed policy matching. 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.

string
enum
required
Allowed:
travelerIds
array of numbers
required

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

travelerIds*
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