openapi: 3.0.3 info: title: Navan Bookings Receipts 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 `. 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: Receipts description: Receipt URLs and downloads for expense transactions. CONFIRMED. paths: /v1/expense/transactions/{id}/receipt: parameters: - $ref: '#/components/parameters/TransactionId' get: operationId: getTransactionReceipt tags: - Receipts summary: Get receipt URLs for a transaction description: Retrieve receipt image URLs for a given transaction. CONFIRMED. responses: '200': description: Receipt URLs. content: application/json: schema: $ref: '#/components/schemas/ReceiptList' '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' /v1/expense/transactions/{id}/receipt/download: parameters: - $ref: '#/components/parameters/TransactionId' get: operationId: downloadTransactionReceipt tags: - Receipts summary: Download a transaction receipt description: Follow a redirect to download the receipt file for a transaction. CONFIRMED. responses: '302': description: Redirect to the receipt file. '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' /v1/expense/transactions/receipts: get: operationId: listReceipts tags: - Receipts summary: Batch list receipt URLs description: Batch-fetch receipt URLs across transactions filtered by date. CONFIRMED. parameters: - $ref: '#/components/parameters/FromDate' - $ref: '#/components/parameters/ToDate' responses: '200': description: Receipt URLs across transactions. content: application/json: schema: $ref: '#/components/schemas/ReceiptList' '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' NotFound: description: The requested resource was not found. content: application/json: schema: $ref: '#/components/schemas/Error' schemas: Receipt: type: object properties: transactionId: type: string url: type: string format: uri fileName: type: string contentType: type: string Error: type: object properties: error: type: object properties: code: type: string message: type: string details: type: object additionalProperties: true ReceiptList: type: object properties: data: type: array items: $ref: '#/components/schemas/Receipt' parameters: TransactionId: name: id in: path required: true description: The transaction identifier. schema: type: string 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.