navan-multi-env-setup

name	navan-multi-env-setup
description	Set up dev/staging/prod environment separation for Navan integrations without a sandbox API. Use when configuring multiple environments, building CI test pipelines, or setting up local development. Trigger with "navan environments", "navan multi env", "navan dev setup", "navan mock server".
allowed-tools	Read, Write, Edit, Bash(npm:*), Grep
version	1.7.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","navan","travel"]
compatibility	Designed for Claude Code

Navan Multi-Environment Setup

Overview

Navan does not offer a sandbox or staging API — every call hits production data with real corporate bookings and expense records. This creates risk for development and testing: a bug in a sync script could modify live itineraries, and CI pipelines cannot safely run integration tests. This skill implements environment isolation using separate OAuth apps, environment variable validation, a local development proxy, and a CI mock server.

Prerequisites

• Navan admin access to create multiple OAuth apps (Admin > Travel admin > Settings > Integrations)
• Node.js 18+ for proxy and mock server
• Understanding of OAuth 2.0 client credentials flow (see navan-install-auth)
• .env management tooling (dotenv, direnv, or cloud secret manager)

Instructions

Step 1: Create Per-Environment OAuth Apps

Create separate API credentials in the Navan admin dashboard for each environment. This provides natural isolation — the dev app can have read-only scopes while production gets full access.

# .env.development — read-only scoped OAuth app
NAVAN_ENV=development
NAVAN_CLIENT_ID=dev-client-id-xxxxx
NAVAN_CLIENT_SECRET=dev-client-secret-xxxxx
NAVAN_API_BASE=https://api.navan.com/v1
NAVAN_READ_ONLY=true

# .env.staging — read + limited write, separate audit trail
NAVAN_ENV=staging
NAVAN_CLIENT_ID=stg-client-id-xxxxx
NAVAN_CLIENT_SECRET=stg-client-secret-xxxxx
NAVAN_API_BASE=https://api.navan.com/v1
NAVAN_READ_ONLY=false

# .env.production — full access, rotation-managed
NAVAN_ENV=production
NAVAN_CLIENT_ID=prod-client-id-xxxxx
NAVAN_CLIENT_SECRET=prod-client-secret-xxxxx
NAVAN_API_BASE=https://api.navan.com/v1
NAVAN_READ_ONLY=false

Step 2: Build an Environment-Aware Client

import { config } from 'dotenv';

interface NavanConfig {
  env: string;
  clientId: string;
  clientSecret: string;
  apiBase: string;
  : ;
}

 ():  {
   envFile = ;
  ({ : envFile });

   required = [, , ];
   ( key  required) {
     (!process.[key]) {
        ();
    }
  }

   {
    : process.. || ,
    : process..!,
    : process..!,
    : process..!,
    : process.. === 
  };
}

  {
   : ;
   :  |  = ;

  () {
    . = ();
    .();
  }

   (: , : , ?: ): <> {
    
     (.. && method !== ) {
        ();
    }

     (!.) {
      . =  .();
    }

     response =  (, {
      method,
      : {
        : ,
        : 
      },
      : body ? .(body) : 
    });

     (!response.) {
        ();
    }
     response.();
  }

    (): <> {
     res =  (, {
      : ,
      : { :  },
      :  ({
        : ,
        : ..,
        : ..
      })
    });
     { access_token } =  res.();
     access_token;
  }
}