Navan Offline Development Loop

Overview

Develop Navan integrations against sanitized contract fixtures with networking denied by default. 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

Local development should exercise the application-owned contract, not depend on a live tenant. Fixtures must preserve structural edge cases while removing traveler, payment, itinerary, and credential data.

Authentication

Local tests require no Navan credential. An optional live smoke uses a separate non-production secret and must be explicitly enabled outside the normal test command.