OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Selected Expense transaction families have structured GET interfaces.
Navan Expense API reference ↗
Endpoints > Generic API — retrieve all transaction types · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Cursor pages support 1–500 records, subject to required date/type selection.
Navan Expense API reference ↗
Pagination · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Date-modified, business dates, transaction types, status and organizational filters are documented.
Navan Expense API reference ↗
Request parameters > Date range filters; Optional filters; Field selection · Checked 2026-10-16
Access cost barrier -
-
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
Navan Expense API reference ↗
Authentication > Obtaining an access token; Obtaining API credentials for the Update API · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
Navan Expense API reference ↗
Authentication > Obtaining an access token; Obtaining API credentials for the Update API · Checked 2026-10-16
Downstream permission -
-
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
Navan Expense API reference ↗
Authentication > Obtaining an access token; Obtaining API credentials for the Update API · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
PATCH updates named accounting/HR/custom fields, up to 100 transactions; results must be inspected per item.
Navan Expense API reference ↗
Update transactions endpoint (batch update with PATCH); Updatable field groups · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Customer code can call the Expense API with configured client credentials; third-party distribution approval remains unresolved.
Navan Expense API reference ↗
Authentication; Complete example · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Date-modified windows support change polling; allow for four-hour query visibility lag.
Navan Expense API reference ↗
Request parameters > date_modified; Date range filters · Checked 2026-10-16
Limit visibility 7.5/10
Service-specific limits disclosed in runtime headers
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
The provider directs clients to monitor rate-limit response headers and apply exponential backoff; no fixed rate is assumed.
Navan Expense API reference ↗
Errors; Best practices · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Modified transactions are discoverable; no complete hard-delete identity feed is established.
Navan Expense API reference ↗
Request parameters > date_modified; Default transaction fields > modified_timestamp · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Overlap date_modified.from/to queries to refetch selected changed transactions. Allow the documented four-hour visibility lag. This supports bounded refetch, without durable event replay, complete lifetime history or deletion recovery.
Navan Expense API reference ↗
Date-modified filters; synchronization and data availability · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
The caller receives structured selected expense records.
Navan Expense API reference ↗
Endpoints; Pagination; Field selection · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
A customer cancellation retrieval window and any exit charges have not been established.
Navan Expense API reference ↗
Authentication > Obtaining an access token; Obtaining API credentials for the Update API · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Portable selected expense records are established; receipt retrieval is separate and whole-product completeness unverified.
Navan Expense API reference ↗
Endpoints; Field selection; Receipts · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Customer integration code can implement external reconciliation; native policy definition portability is unestablished.
Navan Expense API reference ↗
Complete example; Best practices · Checked 2026-10-16
Rights to custom logic -
-
Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Navan Expense API reference ↗
Authentication > Obtaining an access token; Obtaining API credentials for the Update API · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Create API client credentials in Navan, then exchange client ID and secret for a bearer token. Credentials are read-only by default; PATCH needs Expense: Write, and EU accounts use the EU token host plus X-ta-region=EU on API calls.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
The generic transaction endpoint requires selected types and at least one date selection, including date_modified ranges. Responses use next_cursor and has_next with page size 1–500; optional field groups add ERP, policy, tax and HR fields to the default payload.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Navan customer API | OAuth client credentials | Customer | Not confirmed | Customer-supplied credentials | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The lowest eligible customer plan and any fixed API, partner or setup charges remain unestablished. Payment-processing charges do not by themselves establish an API-access surcharge.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
PATCH /v1/expense/transactions updates selected ERP sync, GL-code, HR-dimension and policy-applicable custom fields, with up to 100 transactions per batch. A 200 response can contain validation errors or not-found items; this is metadata editing, not payment execution.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Use overlapping date_modified windows and commit cursors after processing each complete selected batch. GET visibility can lag an update by four hours; transaction-update polling does not establish complete hard-delete capture or an indefinitely replayable change log. Overlap date_modified.from/to queries to refetch selected changed transactions. Allow the documented four-hour visibility lag. This supports bounded refetch, without durable event replay, complete lifetime history or deletion recovery.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Modified transactions are discoverable; no complete hard-delete identity feed is established. | Navan Expense API reference ↗Request parameters > date_modified; Default transaction fields > modified_timestampChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Overlap date_modified.from/to queries to refetch selected changed transactions. Allow the documented four-hour visibility lag. This supports bounded refetch, without durable event replay, complete lifetime history or deletion recovery. | Navan Expense API reference ↗Date-modified filters; synchronization and data availabilityChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Structured expense records can be held externally, with receipt retrieval a distinct API operation. Selected transaction types, time windows and requested field groups bound the copy; native workflow definitions and complete historical-state recovery remain unestablished.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customer-authored code can reconcile Expense records and update approved accounting fields (subject to the configured write scope). The API contract does not establish ownership or independent execution of Navan’s native policy/approval artifacts.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Selected Expense transaction families have structured GET interfaces. | Navan Expense API reference ↗Endpoints > Generic API — retrieve all transaction typesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Cursor pages support 1–500 records, subject to required date/type selection. | Navan Expense API reference ↗PaginationChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Date-modified, business dates, transaction types, status and organizational filters are documented. | Navan Expense API reference ↗Request parameters > Date range filters; Optional filters; Field selectionChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved. | Navan Expense API reference ↗Authentication > Obtaining an access token; Obtaining API credentials for the Update APIChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. The lowest eligible paid plan and route-specific fixed API charges have not been established. | Navan Expense API reference ↗Authentication > Obtaining an access token; Obtaining API credentials for the Update APIChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | Navan Expense API reference ↗Authentication > Obtaining an access token; Obtaining API credentials for the Update APIChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. PATCH updates named accounting/HR/custom fields, up to 100 transactions; results must be inspected per item. | Navan Expense API reference ↗Update transactions endpoint (batch update with PATCH); Updatable field groupsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Customer code can call the Expense API with configured client credentials; third-party distribution approval remains unresolved. | Navan Expense API reference ↗Authentication; Complete exampleChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Date-modified windows support change polling; allow for four-hour query visibility lag. | Navan Expense API reference ↗Request parameters > date_modified; Date range filtersChecked 2026-10-16 |
| How are integration limits disclosed? | Service-specific limits disclosed in runtime headersNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. The provider directs clients to monitor rate-limit response headers and apply exponential backoff; no fixed rate is assumed. | Navan Expense API reference ↗Errors; Best practicesChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. The caller receives structured selected expense records. | Navan Expense API reference ↗Endpoints; Pagination; Field selectionChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. A customer cancellation retrieval window and any exit charges have not been established. | Navan Expense API reference ↗Authentication > Obtaining an access token; Obtaining API credentials for the Update APIChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Customer integration code can implement external reconciliation; native policy definition portability is unestablished. | Navan Expense API reference ↗Complete example; Best practicesChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Navan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | Navan Expense API reference ↗Authentication > Obtaining an access token; Obtaining API credentials for the Update APIChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedNavan Expense API selected card/Connect/manual transactions and related transaction families, with PATCH accounting metadata; Travel bookings, account-wide audit completeness and native approval rules are not combined. Portable selected expense records are established; receipt retrieval is separate and whole-product completeness unverified. | Navan Expense API reference ↗Endpoints; Field selection; ReceiptsChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
- The lowest eligible paid plan and route-specific fixed API charges have not been established.
- Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
- A customer cancellation retrieval window and any exit charges have not been established.
- Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.