Navan Integration Access Intake

Overview

Establish a Navan integration access contract without guessing endpoints, grants, or scopes. 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 publicly confirms Booking API, Expense API, SFTP, direct integrations, SCIM, SAML, and OpenID Connect surfaces. Exact hosts, credentials, scopes, schemas, and enablement are tenant- and contract-specific; copy them from the current in-account source.

Authentication

Record the credential type, issuer, audience or destination, scopes or permissions, expiry, rotation owner, and storage location from the tenant contract. Never infer OAuth client credentials or reuse interactive session cookies.