Navan Event Delivery Contract Verification

Overview

Validate and operate the event or change-delivery mechanism actually enabled for a Navan tenant. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Navan's public pages confirm APIs, SFTP, and direct integrations but do not establish a universal webhook endpoint, event taxonomy, or signature header. Use only the tenant's documented delivery mode and keep polling or reconciliation as a recovery path.

Authentication

For callbacks, use the documented verification scheme and secret lifecycle; for polling or files, use the corresponding read-only identity. Never invent a generic vendor-signature header.