Acknowledge the traveler guidance read

Only the traveler of a saved trip can acknowledge the current relevant travel-security or data-privacy guidance. The acknowledgement records awareness and leaves risks and to-dos unchanged. Repeating a request returns the original timestamp; changed guidance requires its new version.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
number
required

Trip ID

Body Params
number

The journey leg, required for a multi-destination trip.

string
enum
required

The traveler guidance read.

Allowed:
string
required

The current version from travelerGuidance.topics in the saved assessment view.

Responses

400

No relevant current guidance for this topic, invalid body, or missing legId for a multi-destination trip

403

The caller may not view the trip or is not its traveler, or is impersonating the traveler

404

Unknown trip or leg

409

The assessment is not ready or the guidance version has changed

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