Skip to main content
ConfigView reads your Navan (travel and expense, formerly TripActions) company through the Navan Expense API (https://api.navan.com/v1/expense), using an API credential that a Navan admin creates. ConfigView sends only GET requests (and one token request). It never creates, changes or deletes anything in Navan. You will end up with 2 required secrets (NAVAN_CLIENT_ID, NAVAN_CLIENT_SECRET) and 1 optional secret (NAVAN_REGION, for EU tenants) in ConfigView when setup is complete.
Scope of this integration today. ConfigView reads who has a Navan account (work email, name, title, department, whether the account is enabled or a guest, expense admin role, card policy and card status, policy level, region, cost center) and keeps a running history of Navan’s audit log (who changed what kind of thing, the event name and operation, and when). It does not read trips, bookings, itineraries, transactions, receipts, card numbers, amounts or phone numbers.

What you need

  • A Navan admin who can open Admin > Travel admin > Settings > Integrations > Navan API Credentials
  • Navan’s public API enabled for your company. If the page is missing, ask your Navan contact to enable it.
  • Whether your company is hosted in the EU (Navan address app-fra.navan.com)

Step 1: Open the Navan page in ConfigView

Open ConfigView in a second browser tab and leave it open: https://{companyname}.configview.com/admin/integrations/navan

Step 2: Create the API credential

  1. In Navan open Admin > Travel admin > Settings > Integrations > Navan API Credentials
  2. Create a new credential and give it read-only access (the Expense: Read scope). ConfigView never writes, so do not grant Expense: Write.
  3. Copy the client ID and the client secret. Copy the secret now; Navan may not show it again.
  4. In the ConfigView tab paste them into NAVAN_CLIENT_ID and NAVAN_CLIENT_SECRET under Credentials and save each
EU tenants only: also set NAVAN_REGION to EU. ConfigView then requests tokens from app-fra.navan.com and sends the X-ta-region: EU header Navan requires on every call. US tenants leave it empty.

Step 3: Connect and verify

  1. Click Connect. ConfigView creates its tables and schedules every collector at your default run time:
  1. Click Verify now. The health check reads the secrets, requests a token, reads one page of users and tries one small audit-log request.
If a check fails:
  • Token request refused. The client ID or secret is wrong, Navan has not enabled the public API for your company, or your tenant is in the EU and NAVAN_REGION is not set to EU.
  • Users fails with 500. An EU tenant that omits the region header gets 500. Set NAVAN_REGION to EU.
  • Audit log shows as skipped. The credential cannot read audit logs. Nothing to fix unless you want that area.

Data Tables

Each table has a run_at column. navan_users keeps only the newest run; navan_audit_logs keeps its history.

Things worth knowing

Leavers. A disabled account that still has an expense admin role or an active card is worth clearing; the catalog has queries for both. No manager or approver. The Navan users API does not return a manager or approver, so ConfigView cannot show who approves someone’s expenses. It shows policy level and card policy instead. Audit log window. Navan returns at most 31 days per request, so ConfigView reads the log in windows. The audit log names actors by Navan user id and name, not email. Rate limit. Navan publishes no numeric limit. It answers HTTP 429 when you go too fast and recommends exponential backoff. ConfigView paces itself at 60 requests a minute and waits as long as Navan asks. Users are read 100 per page. Tokens. Navan tokens last about 12 hours; ConfigView requests a fresh one each run.

What isn’t collected

  • Trips, bookings, itineraries and travel activity
  • Card transactions, fees, adjustments, repayments, disputes, amounts, merchants and receipts
  • Card numbers, phone numbers and any personal contact details beyond work email and name
  • Audit-log free-text descriptions and old/new values
  • The /activities endpoint (it can only be read per transaction)