Navan website screenshot

Navan

Navan (formerly TripActions, rebranded to Navan in February 2022) is a corporate travel, expense, and corporate card management platform. Its public developer surface centers on the Navan Expense API (OAuth 2.0 client-credentials) for retrieving and updating transactions, fees, adjustments, receipts, and custom fields, plus a Travel/User Management API for provisioning users and reading booking data, and webhooks for change notifications. Navan also publishes an MCP server for connecting AI assistants to Navan data. Booking (travel) is offered at no platform cost and funded by supplier commissions and per-trip fees, while Expense is a per-user subscription.

Navan publishes 7 APIs on the APIs.io network, including Bookings API, Custom Fields API, Fees and Adjustments API, and 4 more. Tagged areas include Corporate Travel, Expense Management, Corporate Cards, Spend Management, and T&E.

Navan’s developer surface includes authentication, documentation, engineering blog, and 10 more developer resources.

42.6/100 developing ▬ flat Agent 29/100 agent aware Full breakdown ↓
scored 2026-08-21 · rubric v0.12.0
AccessPaidSelf serve
7 APIs
Corporate TravelExpense ManagementCorporate CardsSpend ManagementT&EFintechBusiness Travel

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-21 · rubric v0.12.0
Composite quality — 42.6/100 · developing
Contract Quality 12.8 / 21
Developer Ergonomics 4.0 / 17
Access Clarity 8.1 / 17
Operational Transparency 3.8 / 11
Contract Governance 0.0 / 10
Discoverability 6.3 / 9
Regulatory Posture 6.3 / 15
Agent readiness — 29/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/navan: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

Navan Bookings API

Booking (trip) records for downstream reporting. MODELED.

Navan Custom Fields API

Company custom fields used for cost-center / GL coding. CONFIRMED.

Navan Fees and Adjustments API

Fees, credit/debit adjustments, daily rebates, and disputes. CONFIRMED.

Navan Receipts API

Receipt URLs and downloads for expense transactions. CONFIRMED.

Navan Transactions API

Expense transactions across Navan card, Connect, manual, and repayment types. CONFIRMED.

Navan Users API

User provisioning and lifecycle under travel/v1. CONFIRMED.

Navan Webhooks API

Webhook subscription management for change notifications. MODELED.

Scroll for all 7

Open Collections 9

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Navan Bookings API

OPEN COLLECTION

Navan Bookings Users API

OPEN COLLECTION

Navan API

OPEN COLLECTION

Scroll for all 9

Pricing Plans 1

Published pricing tiers and plan structures.

Navan Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Navan Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Navan Finops

FINOPS

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Navan Authentication

oauth2 · 1 scheme

SECURITY

Navan Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Navan Trust Center

SOC 2, ISO 27001, PCI DSS, GDPR, CSA STAR

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Navan Scopes

6 scopes · clientCredentials

6 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Navan Agentic Access

29 operations · 7 acting

29 operations · 7 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: navan
url: https://raw.githubusercontent.com/api-evangelist/navan/refs/heads/main/apis.yml
name: Navan
kind: company
description: Navan (formerly TripActions, rebranded to Navan in February 2022) is a corporate travel, expense, and corporate
  card management platform. Its public developer surface centers on the Navan Expense API (OAuth 2.0 client-credentials) for
  retrieving and updating transactions, fees, adjustments, receipts, and custom fields, plus a Travel/User Management API
  for provisioning users and reading booking data, and webhooks for change notifications. Navan also publishes an MCP server
  for connecting AI assistants to Navan data. Booking (travel) is offered at no platform cost and funded by supplier commissions
  and per-trip fees, while Expense is a per-user subscription.
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/navan.png
tags:
- Corporate Travel
- Expense Management
- Corporate Cards
- Spend Management
- T&E
- Fintech
- Business Travel
created: '2026-07-03'
modified: '2026-07-03'
specificationVersion: '0.23'
apis:
- aid: navan:navan-bookings-api
  name: Navan Bookings API
  description: Booking (trip) records for downstream reporting. MODELED.
  humanURL: https://developer.navan.com/api/
  baseURL: https://api.navan.com/v1/expense
  tags:
  - Bookings
  properties:
  - type: OpenAPI
    url: openapi/navan-bookings-api-openapi.yml
  - type: Documentation
    url: https://developer.navan.com/api/
  - type: APIReference
    url: https://developer.navan.com/api/
  - type: PostmanCollection
    url: collections/navan.postman_collection.json
  - type: OpenCollection
    url: collections/navan.opencollection.json
  - type: Documentation
    url: https://app.navan.com/app/helpcenter/articles/travel/admin/other-integrations/booking-data-integration
- aid: navan:navan-custom-fields-api
  name: Navan Custom Fields API
  description: Company custom fields used for cost-center / GL coding. CONFIRMED.
  humanURL: https://developer.navan.com/api/
  baseURL: https://api.navan.com/v1/expense
  tags:
  - Custom Fields
  properties:
  - type: OpenAPI
    url: openapi/navan-custom-fields-api-openapi.yml
  - type: Documentation
    url: https://developer.navan.com/api/
  - type: APIReference
    url: https://developer.navan.com/api/
  - type: PostmanCollection
    url: collections/navan.postman_collection.json
  - type: OpenCollection
    url: collections/navan.opencollection.json
  - type: Documentation
    url: https://app.navan.com/app/helpcenter/articles/travel/admin/other-integrations/booking-data-integration
- aid: navan:navan-fees-and-adjustments-api
  name: Navan Fees and Adjustments API
  description: Fees, credit/debit adjustments, daily rebates, and disputes. CONFIRMED.
  humanURL: https://developer.navan.com/api/
  baseURL: https://api.navan.com/v1/expense
  tags:
  - Fees and Adjustments
  properties:
  - type: OpenAPI
    url: openapi/navan-fees-and-adjustments-api-openapi.yml
  - type: Documentation
    url: https://developer.navan.com/api/
  - type: APIReference
    url: https://developer.navan.com/api/
  - type: PostmanCollection
    url: collections/navan.postman_collection.json
  - type: OpenCollection
    url: collections/navan.opencollection.json
  - type: Documentation
    url: https://app.navan.com/app/helpcenter/articles/travel/admin/other-integrations/booking-data-integration
- aid: navan:navan-receipts-api
  name: Navan Receipts API
  description: Receipt URLs and downloads for expense transactions. CONFIRMED.
  humanURL: https://developer.navan.com/api/
  baseURL: https://api.navan.com/v1/expense
  tags:
  - Receipts
  properties:
  - type: OpenAPI
    url: openapi/navan-receipts-api-openapi.yml
  - type: Documentation
    url: https://developer.navan.com/api/
  - type: APIReference
    url: https://developer.navan.com/api/
  - type: PostmanCollection
    url: collections/navan.postman_collection.json
  - type: OpenCollection
    url: collections/navan.opencollection.json
  - type: Documentation
    url: https://app.navan.com/app/helpcenter/articles/travel/admin/other-integrations/booking-data-integration
- aid: navan:navan-transactions-api
  name: Navan Transactions API
  description: Expense transactions across Navan card, Connect, manual, and repayment types. CONFIRMED.
  humanURL: https://developer.navan.com/api/
  baseURL: https://api.navan.com/v1/expense
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/navan-transactions-api-openapi.yml
  - type: Documentation
    url: https://developer.navan.com/api/
  - type: APIReference
    url: https://developer.navan.com/api/
  - type: PostmanCollection
    url: collections/navan.postman_collection.json
  - type: OpenCollection
    url: collections/navan.opencollection.json
  - type: Documentation
    url: https://app.navan.com/app/helpcenter/articles/travel/admin/other-integrations/booking-data-integration
- aid: navan:navan-users-api
  name: Navan Users API
  description: User provisioning and lifecycle under travel/v1. CONFIRMED.
  humanURL: https://developer.navan.com/api/
  baseURL: https://api.navan.com/v1/expense
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/navan-users-api-openapi.yml
  - type: Documentation
    url: https://developer.navan.com/api/
  - type: APIReference
    url: https://developer.navan.com/api/
  - type: PostmanCollection
    url: collections/navan.postman_collection.json
  - type: OpenCollection
    url: collections/navan.opencollection.json
  - type: Documentation
    url: https://app.navan.com/app/helpcenter/articles/travel/admin/other-integrations/booking-data-integration
- aid: navan:navan-webhooks-api
  name: Navan Webhooks API
  description: Webhook subscription management for change notifications. MODELED.
  humanURL: https://developer.navan.com/api/
  baseURL: https://api.navan.com/v1/expense
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/navan-webhooks-api-openapi.yml
  - type: Documentation
    url: https://developer.navan.com/api/
  - type: APIReference
    url: https://developer.navan.com/api/
  - type: PostmanCollection
    url: collections/navan.postman_collection.json
  - type: OpenCollection
    url: collections/navan.opencollection.json
  - type: Documentation
    url: https://app.navan.com/app/helpcenter/articles/travel/admin/other-integrations/booking-data-integration
common:
- type: AgenticAccess
  url: agentic-access/navan-agentic-access.yml
- type: TrustCenter
  url: security/navan-trust-center.yml
- type: DomainSecurity
  url: security/navan-domain-security.yml
- type: Authentication
  url: authentication/navan-authentication.yml
- type: OAuthScopes
  url: scopes/navan-scopes.yml
- type: GitHubOrganization
  url: https://github.com/navan-public
- type: LinkedIn
  url: https://www.linkedin.com/company/navan
- type: Website
  url: https://navan.com
- type: Documentation
  url: https://developer.navan.com/
- type: Plans
  url: plans/navan-plans-pricing.yml
- type: RateLimits
  url: rate-limits/navan-rate-limits.yml
- type: FinOps
  url: finops/navan-finops.yml
- type: Blog
  url: https://navan.com/blog/rss.xml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/navan"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/navan/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/navan/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.