openapi: 3.0.3
info:
title: Navan Bookings Fees and Adjustments API
description: 'The Navan API is the public developer surface for the Navan (formerly TripActions) corporate travel, expense, and corporate card platform. It is a REST/HTTPS API secured with OAuth 2.0 using the client-credentials grant. Administrators generate a client_id / client_secret in the Navan app under Settings > Integrations (API), exchange them for a Bearer access token, and call the API with `Authorization: Bearer <token>`. Access is scoped (e.g. bookings:read, users:read, users:write, users:delete, and the expense read/write scopes).
Endpoint status: the Expense API paths (transactions, fees, adjustments, receipts, custom fields) and the travel/v1 Users paths are CONFIRMED against Navan''s published API reference and third-party integration guides. The Bookings and Webhook subscription-management paths are MODELED - the relevant scopes and capabilities are documented by Navan, but the exact request paths are behind a gated reference and are represented here as a best-effort model. Modeled operations are flagged with `x-endpoint-status: modeled`.'
version: '1.0'
contact:
name: Navan Developers
url: https://developer.navan.com/
x-rebrand-note: Navan was known as TripActions until its February 2022 rebrand to Navan; some legacy hostnames and token paths still carry a `ta-` (TripActions) prefix, e.g. the `ta-auth` OAuth token path.
servers:
- url: https://api.navan.com
description: Navan API (US / global)
security:
- oauth2ClientCredentials: []
tags:
- name: Fees and Adjustments
description: Fees, credit/debit adjustments, daily rebates, and disputes. CONFIRMED.
paths:
/v1/expense/fees:
get:
operationId: listFees
tags:
- Fees and Adjustments
summary: List fees
description: Retrieve direct-reimbursement, FX, and platform fees. CONFIRMED.
parameters:
- $ref: '#/components/parameters/FromDate'
- $ref: '#/components/parameters/ToDate'
responses:
'200':
description: A page of fees.
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionList'
'401':
$ref: '#/components/responses/Unauthorized'
/v1/expense/adjustments:
get:
operationId: listAdjustments
tags:
- Fees and Adjustments
summary: List adjustments
description: Retrieve credit and debit memo adjustments. CONFIRMED.
parameters:
- $ref: '#/components/parameters/FromDate'
- $ref: '#/components/parameters/ToDate'
responses:
'200':
description: A page of adjustments.
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionList'
'401':
$ref: '#/components/responses/Unauthorized'
/v1/expense/daily-rebates:
get:
operationId: listDailyRebates
tags:
- Fees and Adjustments
summary: List daily rebates
description: Retrieve daily rebate transactions. CONFIRMED.
parameters:
- $ref: '#/components/parameters/FromDate'
- $ref: '#/components/parameters/ToDate'
responses:
'200':
description: A page of daily rebates.
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionList'
'401':
$ref: '#/components/responses/Unauthorized'
/v1/expense/disputes:
get:
operationId: listDisputes
tags:
- Fees and Adjustments
summary: List disputes
description: Retrieve dispute transactions. CONFIRMED.
parameters:
- $ref: '#/components/parameters/FromDate'
- $ref: '#/components/parameters/ToDate'
responses:
'200':
description: A page of disputes.
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionList'
'401':
$ref: '#/components/responses/Unauthorized'
components:
responses:
Unauthorized:
description: Missing or invalid access token, or insufficient scope.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
schemas:
TransactionList:
type: object
properties:
data:
type: array
items:
$ref: '#/components/schemas/Transaction'
next_cursor:
type: string
nullable: true
Transaction:
type: object
properties:
id:
type: string
type:
type: string
description: The transaction type (card, connect, manual, repayment, fee, adjustment, rebate, dispute).
status:
type: string
merchant:
type: string
amount:
type: number
currency:
type: string
date:
type: string
format: date-time
userId:
type: string
customFieldValues:
type: object
additionalProperties: true
Error:
type: object
properties:
error:
type: object
properties:
code:
type: string
message:
type: string
details:
type: object
additionalProperties: true
parameters:
FromDate:
name: from
in: query
required: false
description: Start of the date range filter (ISO 8601).
schema:
type: string
format: date-time
ToDate:
name: to
in: query
required: false
description: End of the date range filter (ISO 8601).
schema:
type: string
format: date-time
securitySchemes:
oauth2ClientCredentials:
type: oauth2
description: 'OAuth 2.0 client-credentials flow. Generate a client_id / client_secret in the Navan app under Settings > Integrations (API), then POST grant_type=client_credentials to the token URL to obtain a Bearer access token. US token URL: https://app.navan.com/ta-auth/oauth/token ; EU token URL: https://app-fra.navan.com/ta-auth/oauth/token . (Some integrations reference an https://api.navan.com/ta-auth/oauth/token or /auth/v1/token variant; confirm the current token URL in the Navan developer portal.)'
flows:
clientCredentials:
tokenUrl: https://app.navan.com/ta-auth/oauth/token
scopes:
bookings:read: Read booking (trip) data.
users:read: Read user profiles.
users:write: Create and modify users.
users:delete: Deactivate users.
liquid:read: Read expense data (transactions, fees, receipts, custom fields).
liquid:write: Update expense data.