Navan Contract-Bound Adapter

Overview

Design an application-owned Navan adapter pinned to the tenant's actual integration contract. 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

Do not assume a public SDK, base URL, pagination model, or error envelope. Preserve the vendor payload at the boundary, then map it into versioned application types backed by captured schemas and fixtures.

Authentication

Accept a secret-provider callback or file-transfer credential reference, never a literal secret. Bind credentials, tenant identity, and host allowlist together so configuration cannot cross environments.