Subscribe to and parse SAP Concur Itinerary v4 events to keep a downstream system synchronized

Steps

1. Register a subscription on the public.concur.travel.itinerary topic via the Concur Event Subscription Service v4; specify your HTTPS callback endpoint and the event types you need
2. Handle inbound webhook payloads: each event contains the itinerary unique identifier and an event type such as created, updated, cancelled, or anonymized
3. Use the itinerary ID from the event payload to call the Itinerary v4 GET endpoint and retrieve full trip details including segments, dates, and traveler information
4. Map the itinerary status codes: 0 for Confirmed, 1 for Ticketed by agent, and 2 for Cancelled; drive downstream logic from these values rather than free-text fields
5. Handle the anonymized event type for GDPR right-to-be-forgotten compliance by purging or masking PII in your own data store
6. Implement idempotent event processing using the event ID; the platform may deliver duplicate events during retries