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 API contracts indexed 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.

The Navan catalog on APIs.io includes 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

32.7/100 thin ▬ flat Agent 35/100 agent ready Front door AI 5/6 prominent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract 1 MCP Servers

Corporate Travel Expense Management Corporate Cards Spend ManagementT&EFintech Business Travel

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Developer Platform & API Ecosystem Management

BC-4270

Webhooks

POST /v1/expense/webhooks

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 32.7/100 · thin

Contract Quality 10.0 / 19

Developer Ergonomics 4.8 / 15

Access Clarity 2.4 / 15

Operational Transparency 1.0 / 10

Contract Governance 1.2 / 9

Discoverability 5.1 / 8

Regulatory Posture 3.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 35/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 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

Delegated User Identity 0 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/navan/"><img src="https://apis.io/badge/navan/card.svg" alt="Navan on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 15.8 — up to +16.8 composite points
Developer Ergonomics scores 32.1 — up to +13.6 composite points
Contract Quality scores 53.2 — up to +11.7 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/navan/apis.yml: open an issue on github.com/api-evangelist/navan to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Procurement and B2B Buying (source-to-pay suites, spend management)	mixed	35.9	-	-
Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)	mixed	35.9	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 4

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

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 8

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

Navan Bookings API

OPEN COLLECTION

Navan Bookings Custom Fields API

OPEN COLLECTION

Navan Bookings Fees and Adjustments API

OPEN COLLECTION

Navan Bookings Receipts API

OPEN COLLECTION

Navan Bookings Transactions API

OPEN COLLECTION

Navan Bookings Users API

OPEN COLLECTION

Navan Bookings Webhooks API

OPEN COLLECTION

Navan API

OPEN COLLECTION

Scroll for all 8

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Navan MCP Server

Remote MCP server at mcp.navan.com over HTTP.

MCP SERVER

Navan API pricing

Not yet checked against Navan's own pricing page. Compiled by API Evangelist on 2026-07-03 from navan.com/pricing; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Business Travel free	—
Business Expense paid	—
Enterprise (Unified T&E) enterprise	—

Plan details, limits and sources →

Rate limits

API Requests: not published requests
Access Token Lifetime: short-lived (refresh via client-credentials) token
Pagination Page Size: cursor-based, bounded per page records

Compiled by API Evangelist, not yet checked against Navan's documentation. Rate-limit details →

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

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Navan

SLA

FinOps 1

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

Navan Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Navan API Rules

59 rules · 51 errors 7 warnings 1 info

SPECTRAL

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

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

DomainSecurity

Authentication

OAuthScopes

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

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.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  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:
  - Booking
  tags_raw:
  - 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: CapabilityMap
  url: capabilities/navan-capability-edges.yml
  name: Navan Business Capability Map
- 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

Navan API — frequently asked questions

Does Navan have an API?

Yes. APIs.io lists 7 APIs from Navan, including Navan Bookings API, Navan Custom Fields API and Navan Fees and Adjustments API, and 4 more.

Is there an OpenAPI specification for the Navan API?

Yes. APIs.io indexes 7 OpenAPI specifications for Navan, each linked for download from this page.

How do I authenticate with the Navan API?

Navan documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Navan Authentication.

How much does the Navan API cost?

APIs.io lists 3 pricing plans for Navan, with each plan's price, limits and inclusions under Pricing on this page.

Does Navan have an MCP server?

Yes. APIs.io lists 1 MCP server for Navan: Remote MCP server at mcp.navan.com over HTTP.

Is the Navan API ready for AI agents?

Navan has a Kin Score of 32.7 out of 100 (thin) and an Agent Readiness score of 34.9 (agent-ready), scored by API Evangelist on 2026-11-06.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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