navan-upgrade-migration

# Navan Upgrade Migration ## Overview Defensive patterns for maintaining Navan API integrations over time. Navan does not publicly version their API, publish a changelog, or guarantee backward compatibility. Every API response should be treated as potentially different from the last. ## Prerequisites - Existing Navan API integration in production - OAuth credentials (`client_id`, `client_secret`) stored in a secret manager - Baseline API response snapshots for comparison (see Step 1) - `curl`, `jq`, and `diff` for schema comparison ## Instructions ### Step 1 — Capture Response Baselines Store known-good API responses as reference schemas. Compare against these regularly to detect drift. ```bash TOKEN=$(curl -s -X POST "https://api.navan.com/ta-auth/oauth/token" \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=client_credentials&client_id=$NAVAN_CLIENT_ID&client_secret=$NAVAN_CLIENT_SECRET" \ | jq -r '.access_token') BASELINE_DIR="navan-api-baselines/$(date +%Y%m%d)" mkdir -p "$BASELINE_DIR" # Capture response structure (keys only, no values) for ENDPOINT in users bookings; do curl -s -H "Authorization: Bearer $TOKEN" \ "https://api.navan.com/v1/${ENDPOINT}?page=0&size=1" \ | jq '[.data[] | keys] | .[0]' > "$BASELINE_DIR/${ENDPOINT}-schema.json" 2>/dev/null echo "Captured: $ENDPOINT → $(cat "$BASELINE_DIR/${ENDPOINT}-schema.json" | jq length) fields" done ``` ### Step 2 — Schema Drift Detection Run this periodically (daily c...