---
canonical_url: "https://docs.composio.dev/toolkits/navan"
markdown_url: "https://docs.composio.dev/toolkits/navan.md"
product: "platform"
version: null
last_updated: null
---

# Navan

Navan provides business travel, expense, transaction, user, audit, and custom-field APIs for company integrations. This connection currently supports US-hosted Navan companies only; EU accounts require a different host and the EU-only X-ta-region header.

- **Category:** accounting
- **Auth:** S2S_OAUTH2
- **Composio-managed OAuth available?** No
- **Tools:** 26
- **Triggers:** 0
- **Slug:** `NAVAN`
- **Version:** 00000000_00

## Tools

### Download Transaction Receipt

**Slug:** `NAVAN_DOWNLOAD_TRANSACTION_RECEIPT`

Download a transaction receipt, electronic receipt, or missing-receipt affidavit. Navan redirects to a five-minute presigned URL; the redirect is followed immediately and the final PDF, JPEG, or PNG is returned as a file.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `receipt_type` | string ("RECEIPT" | "E_RECEIPT" | "AFFIDAVIT") | No | Receipt artifact to download. RECEIPT automatically falls back to E_RECEIPT when no uploaded receipt is available. |
| `transaction_id` | string | Yes | Transaction whose receipt file to download. Must start with a letter or digit. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Custom Field

**Slug:** `NAVAN_GET_CUSTOM_FIELD`

Get one company Navan Expense custom-field definition by its provider field name. Use the custom-field name, such as customField1 or projects, rather than the field's display label.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `field_name` | string | Yes | Provider custom-field name, not its display label. Must start with a letter or digit; embedded slashes are accepted and encoded. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Custom Field Job

**Slug:** `NAVAN_GET_CUSTOM_FIELD_JOB`

Get the current status, operation counts, timestamps, and up to 50 errors for an asynchronous Navan custom-field option job.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `job_id` | string | Yes | UUID returned when custom-field option operations were submitted. Must start with a letter or digit. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Expense User

**Slug:** `NAVAN_GET_EXPENSE_USER`

Get one eligible-company Navan Expense user by ID. Site-admin users are not returned and produce a not-found response.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user_id` | string | Yes | Expense user ID. Must start with a letter or digit. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Transaction

**Slug:** `NAVAN_GET_TRANSACTION`

Get one Navan Expense transaction by its ID for an ad-hoc lookup. The response preserves the concrete _type discriminator and provider-specific fields. Use the generic bulk-by-ID transaction action instead of repeatedly calling this action for a list of IDs.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `transaction_id` | string | Yes | Unique transaction identifier returned by a Navan transaction API. Must start with a letter or digit. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Transaction Receipt Links

**Slug:** `NAVAN_GET_TRANSACTION_RECEIPT_LINKS`

Return seven-day presigned receipt, electronic-receipt, and affidavit URLs for one Navan Expense transaction. This endpoint returns JSON links and does not follow the separate receipt-download redirect.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `transaction_id` | string | Yes | Transaction ID whose receipt links to retrieve. Must start with a letter or digit. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Import Trip

**Slug:** `NAVAN_IMPORT_TRIP`

Import an external trip and any supplied flight, hotel, rail, car, or black-car bookings into Navan.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `trip` | object | Yes | Root trip import payload. Source is required; nested bookings retain their documented required fields. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Adjustments

**Slug:** `NAVAN_LIST_ADJUSTMENTS`

Return one cursor page of credit and debit adjustments for a documented date search and optional filters. Navan documents at least one single-date filter or matching date range for normal search. Dates are YYYY-MM-DD UTC, cannot precede the first day of the month two months before the current month, and ranges may not exceed 93 days.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Filter by posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum adjustments in this page (1-500). |
| `cursor` | string | No | Opaque cursor returned by the preceding page. Omit for the first page and pass it back unchanged. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range. |
| `flagged` | boolean | No | Filter by whether the adjustment is flagged. |
| `regions` | array | No | Reporting-data regions to include. |
| `itemized` | boolean | No | Filter by whether the adjustment is itemized. |
| `personal` | boolean | No | Filter by whether the adjustment is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range. |
| `departments` | array | No | Reporting-data departments to include. |
| `flag_reason` | string | No | Flag reason. RECEIPT_MISSING is documented as an example, not a complete enum. |
| `flag_status` | string | No | Flag status. PENDING_APPROVER is documented as an example, not a complete enum. |
| `cost_centers` | array | No | Reporting-data cost centers to include. |
| `subsidiaries` | array | No | Reporting-data subsidiaries to include. |
| `date_modified` | string | No | Filter by modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but the complete value set is not. |
| `legal_entities` | array | No | Reporting-data legal entities to include. |
| `approval_status` | array | No | Approval statuses to include; Navan does not enumerate all values. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not enumerate all values. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range. |
| `transaction_date` | string | No | Filter by transaction date in YYYY-MM-DD UTC. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range. |
| `reimbursement_date` | string | No | Filter by reimbursement completion date; use for flexible reimbursements without posted dates. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit: APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add: BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. POLICY is not returned by default. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range. |
| `last_approver_action_date` | string | No | Filter by approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Audit Logs

**Slug:** `NAVAN_LIST_AUDIT_LOGS`

Return one cursor page of ERP and accounting-settings audit events for eligible companies within a required RFC3339 window of at most 31 days.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `size` | integer | No | Maximum audit events in this page (1-500). |
| `cursor` | string | No | Opaque next_cursor from a preceding page. Omit for the first page and repeat the original time window and filters when continuing. |
| `to_time` | string | Yes | Exclusive RFC3339 event-time window end. It must be after from_time, not be in the future, and be at most 31 days after from_time. |
| `actor_ids` | array | No | Exact actor IDs to include as repeated actor_id query parameters. |
| `from_time` | string | Yes | Inclusive RFC3339 event-time window start. It must precede to_time, be no earlier than the first UTC day of the month two months ago, and start a window of at most 31 days. |
| `event_names` | array | No | Exact audit event names to include as repeated query parameters. |
| `resource_ids` | array | No | Exact audited resource IDs to include as repeated query parameters. |
| `origin_components` | array | No | Origin components to include as repeated query parameters. This filter is not returned in audit rows. |
| `resource_categories` | array | No | Exact warehouse categories or Admin UI labels to include. Values are sent as repeated resource_category query parameters; duplicates are ignored. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Bookings

**Slug:** `NAVAN_LIST_BOOKINGS`

Return one page of company booking rows filtered by booking, trip, status, type, or epoch-second time ranges, optionally including transactions.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Zero-based page number for an explicit page request. |
| `size` | integer | No | Maximum booking rows in this page. |
| `cursor` | string | No | Opaque next_cursor from a preceding page. Omit for the first page and repeat the original filters when continuing. |
| `trip_uuid` | string | No | Return bookings belonging to this trip UUID. |
| `created_to` | integer | No | Latest booking creation timestamp in epoch seconds. |
| `updated_to` | integer | No | Latest booking update timestamp in epoch seconds. |
| `booking_type` | string ("HOTEL" | "FLIGHT" | "CAR" | "RAIL" | "TRANSPORTATION" | "BLACK_CAR") | No | Booking type to include. |
| `booking_uuid` | string | No | Return the booking with this UUID. |
| `created_from` | integer | No | Earliest booking creation timestamp in epoch seconds. |
| `updated_from` | integer | No | Earliest booking update timestamp in epoch seconds. |
| `start_date_to` | integer | No | Latest trip end timestamp in epoch seconds. |
| `booking_status` | string ("CANCELED" | "VOIDED" | "CONFIRMED" | "TICKETED" | "ACCEPTED") | No | Booking status to include. |
| `start_date_from` | integer | No | Earliest trip start timestamp in epoch seconds. |
| `include_transactions` | boolean | No | Whether to include transaction data in booking rows. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Card Transactions

**Slug:** `NAVAN_LIST_CARD_TRANSACTIONS`

Return one cursor page of Navan card transactions for a documented date search and optional transaction filters. At least one date filter is required; dates use YYYY-MM-DD UTC, the earliest allowed date is the first day of the month two months before the current month, and ranges may span at most 93 days.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum transactions on this page (1-500). |
| `cursor` | string | No | Opaque next_cursor from a preceding page. Omit for the first page and pass it back unchanged to continue. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the transaction is flagged. |
| `regions` | array | No | Reporting-data regions to include. |
| `itemized` | boolean | No | Filter by whether the transaction has line items. |
| `personal` | boolean | No | Filter by whether the transaction is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | Reporting-data department names to include. |
| `flag_reason` | string | No | Flag reason. RECEIPT_MISSING is documented as an example, not a complete enum. |
| `flag_status` | string | No | Flag status. PENDING_APPROVER is documented as an example, not a complete enum. |
| `cost_centers` | array | No | Reporting-data cost centers to include. |
| `subsidiaries` | array | No | Reporting-data subsidiaries to include. |
| `date_modified` | string | No | Modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but the complete value set is not. |
| `legal_entities` | array | No | Reporting-data legal entities to include. |
| `approval_status` | array | No | Approval statuses to include; Navan does not document a complete enum. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not document a complete enum. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Transaction date in YYYY-MM-DD UTC. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Reimbursement completion date in YYYY-MM-DD UTC; use this for flexible reimbursements without a posted date. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit. Documented groups are APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, and VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add. POLICY is not returned by default; documented groups are BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, and VENDOR. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action date range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action date range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Connect Transactions

**Slug:** `NAVAN_LIST_CONNECT_TRANSACTIONS`

Return one cursor page of external card-integration transactions. At least one single-date or date-range filter is required; dates use YYYY-MM-DD UTC, must be within Navan's documented lookback, and ranges cannot exceed 93 days.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Filter by posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum transactions in this page (1-500). |
| `cursor` | string | No | Opaque cursor returned as next_cursor by the preceding page. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the transaction is flagged. |
| `regions` | array | No | Reporting-data regions to include. |
| `itemized` | boolean | No | Filter by whether the transaction has line items. |
| `personal` | boolean | No | Filter by whether the transaction is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | Reporting-data departments to include. |
| `flag_reason` | string | No | Flag reason. RECEIPT_MISSING is a documented example, not a complete enum. |
| `flag_status` | string | No | Flag status. PENDING_APPROVER is a documented example, not a complete enum. |
| `cost_centers` | array | No | Reporting-data cost centers to include. |
| `subsidiaries` | array | No | Reporting-data subsidiaries to include. |
| `date_modified` | string | No | Filter by modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but the complete value set is not. |
| `legal_entities` | array | No | Reporting-data legal entities to include. |
| `approval_status` | array | No | Approval statuses to include; Navan does not document a complete value set. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not document a complete value set. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Filter by transaction date in YYYY-MM-DD UTC. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Filter by reimbursement completion date in YYYY-MM-DD UTC. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit. Documented values are APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, and VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add. Documented values are BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, and VENDOR. POLICY is not returned by default. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Filter by approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Custom Fields

**Slug:** `NAVAN_LIST_CUSTOM_FIELDS`

List all Navan Expense custom-field definitions for the company.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Daily Rebates

**Slug:** `NAVAN_LIST_DAILY_REBATES`

Return one cursor page of daily rebates for a required documented date search and optional transaction filters.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum daily rebates in this page (1-500). |
| `cursor` | string | No | Opaque cursor returned as next_cursor by the preceding page. Omit for the first page and pass it back unchanged. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the rebate is flagged. |
| `regions` | array | No | ERP region names to include; multiple values use OR logic. |
| `itemized` | boolean | No | Filter by whether the rebate has line items. |
| `personal` | boolean | No | Filter by whether the rebate is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | ERP department names to include; multiple values use OR logic. |
| `flag_reason` | string | No | Flag reason to include. RECEIPT_MISSING is documented as an example, not a complete enum. |
| `flag_status` | string | No | Flag status to include. PENDING_APPROVER is documented as an example, not a complete enum. |
| `cost_centers` | array | No | ERP cost-center names to include; multiple values use OR logic. |
| `subsidiaries` | array | No | ERP subsidiary names to include; multiple values use OR logic. |
| `date_modified` | string | No | Modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but Navan does not enumerate the complete value set. |
| `legal_entities` | array | No | ERP legal-entity names to include; multiple values use OR logic. |
| `approval_status` | array | No | Approval statuses to include; Navan does not enumerate all values. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not enumerate all values. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Transaction date in YYYY-MM-DD UTC. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Reimbursement completion date in YYYY-MM-DD UTC. Use this for flexible reimbursements that have no posted date. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit: APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add: BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Disputes

**Slug:** `NAVAN_LIST_DISPUTES`

Return one cursor page of Navan disputes, including provisional credits and reversals for EUR and GBP, for a required documented date search and optional transaction filters.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum disputes in this page (1-500). |
| `cursor` | string | No | Opaque cursor returned as next_cursor by the preceding page. Omit for the first page and pass it back unchanged. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the dispute is flagged. |
| `regions` | array | No | ERP region names to include; multiple values use OR logic. |
| `itemized` | boolean | No | Filter by whether the dispute has line items. |
| `personal` | boolean | No | Filter by whether the dispute is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | ERP department names to include; multiple values use OR logic. |
| `flag_reason` | string | No | Flag reason to include. RECEIPT_MISSING is a documented example, not a complete enum. |
| `flag_status` | string | No | Flag status to include. PENDING_APPROVER is a documented example, not a complete enum. |
| `cost_centers` | array | No | ERP cost-center names to include; multiple values use OR logic. |
| `subsidiaries` | array | No | ERP subsidiary names to include; multiple values use OR logic. |
| `date_modified` | string | No | Modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but Navan does not enumerate the complete value set. |
| `legal_entities` | array | No | ERP legal-entity names to include; multiple values use OR logic. |
| `approval_status` | array | No | Approval statuses to include; Navan does not enumerate all values. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not enumerate all values. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Transaction date in YYYY-MM-DD UTC. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Reimbursement completion date in YYYY-MM-DD UTC. Use this for flexible reimbursements that have no posted date. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit: APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add: BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. POLICY is not returned by default. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Expense Users

**Slug:** `NAVAN_LIST_EXPENSE_USERS`

Return one cursor page of company Expense users filtered by text, enabled state, guest state, or administrator role. This endpoint is available only to eligible companies and excludes site-admin users.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `role` | string ("ACCOUNT_OWNER" | "ADMIN" | "READ_ONLY_ADMIN" | "EXPENSE_SPECIALIST" | "ACCOUNTANT" | "FPA_SPECIALIST" | "AP_ADMIN" | "AP_SPECIALIST") | No | Expense Admin dashboard role, including Bill Pay roles. USER is not a valid filter. |
| `size` | integer | No | Maximum users in this page (1-100). |
| `guest` | boolean | No | Filter by whether users are guests. |
| `query` | string | No | Text search matching user email, name, or employee ID. |
| `cursor` | string | No | Opaque next_cursor from a preceding page; omit for the first page. |
| `enabled` | boolean | No | Filter by whether users are enabled. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Fees

**Slug:** `NAVAN_LIST_FEES`

Return one cursor page of direct-reimbursement, foreign-exchange, and platform fees. Navan requires at least one single-date filter or date-range bound; dates are UTC YYYY-MM-DD, cannot precede the first day of the month two months before the current month, and complete ranges may not exceed 93 days.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum fees in this page (1-500). |
| `cursor` | string | No | Opaque cursor returned as next_cursor by the preceding page. Omit for the first page and pass it back unchanged. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the fee is flagged. |
| `regions` | array | No | ERP region names to include; multiple values use OR logic. |
| `itemized` | boolean | No | Filter by whether the fee has line items. |
| `personal` | boolean | No | Filter by whether the fee is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | ERP department names to include; multiple values use OR logic. |
| `flag_reason` | string | No | Flag reason to include. RECEIPT_MISSING is documented as an example, not a complete enum. |
| `flag_status` | string | No | Flag status to include. PENDING_APPROVER is documented as an example, not a complete enum. |
| `cost_centers` | array | No | ERP cost-center names to include; multiple values use OR logic. |
| `subsidiaries` | array | No | ERP subsidiary names to include; multiple values use OR logic. |
| `date_modified` | string | No | Modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but Navan does not enumerate the complete value set. |
| `legal_entities` | array | No | ERP legal-entity names to include; multiple values use OR logic. |
| `approval_status` | array | No | Approval statuses to include; Navan does not enumerate all values. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not enumerate all values. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Transaction date in YYYY-MM-DD UTC. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Reimbursement completion date in YYYY-MM-DD UTC. Use this for direct reimbursements without a posted date. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit: APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add: BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. POLICY is not returned by default. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Manual Transactions

**Slug:** `NAVAN_LIST_MANUAL_TRANSACTIONS`

Return one cursor page of manual expenses, reimbursements, and payroll transactions. Navan requires at least one single-date filter or matching date range for normal search; dates are UTC YYYY-MM-DD, cannot precede the first day of the month two months before the current month, and ranges may not exceed 93 days. Parameter combinations remain permissive so Navan can apply its documented contract.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum transactions in this page (1-500). |
| `cursor` | string | No | Continuation cursor returned by a previous page; omit for the first page. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the transaction is flagged. |
| `regions` | array | No | Reporting-data regions to include. |
| `itemized` | boolean | No | Filter by whether the transaction is itemized. |
| `personal` | boolean | No | Filter by whether the transaction is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | Reporting-data departments to include. |
| `flag_reason` | string | No | Flag reason; RECEIPT_MISSING is an example, not a complete enum. |
| `flag_status` | string | No | Flag status; PENDING_APPROVER is an example, not a complete enum. |
| `cost_centers` | array | No | Reporting-data cost centers to include. |
| `subsidiaries` | array | No | Reporting-data subsidiaries to include. |
| `date_modified` | string | No | Modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter; RECEIPT_AFFIDAVIT_SUBMITTED is documented, but the complete value set is not. |
| `legal_entities` | array | No | Reporting-data legal entities to include. |
| `approval_status` | array | No | Approval statuses to include; Navan does not document a complete value set. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not document a complete value set. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Transaction date in YYYY-MM-DD UTC; for manual expenses, this is when the expense occurred. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Reimbursement completion date in YYYY-MM-DD UTC; use for flexible reimbursements without a posted date. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit. Documented groups are APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, and VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add. Documented groups are BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, and VENDOR. POLICY is not returned by default. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Repayments

**Slug:** `NAVAN_LIST_REPAYMENTS`

Return one cursor page of user repayments for a required documented date search and optional transaction filters.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum repayments in this page (1-500). |
| `cursor` | string | No | Opaque cursor returned as next_cursor by the preceding page. Omit for the first page and pass it back unchanged. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the repayment is flagged. |
| `regions` | array | No | ERP region names to include; multiple values use OR logic. |
| `itemized` | boolean | No | Filter by whether the repayment has line items. |
| `personal` | boolean | No | Filter by whether the repayment is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | ERP department names to include; multiple values use OR logic. |
| `flag_reason` | string | No | Flag reason to include. RECEIPT_MISSING is documented as an example, not a complete enum. |
| `flag_status` | string | No | Flag status to include. PENDING_APPROVER is documented as an example, not a complete enum. |
| `cost_centers` | array | No | ERP cost-center names to include; multiple values use OR logic. |
| `subsidiaries` | array | No | ERP subsidiary names to include; multiple values use OR logic. |
| `date_modified` | string | No | Modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but Navan does not enumerate the complete value set. |
| `legal_entities` | array | No | ERP legal-entity names to include; multiple values use OR logic. |
| `approval_status` | array | No | Approval statuses to include; Navan does not enumerate all values. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not enumerate all values. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Transaction date in YYYY-MM-DD UTC. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Reimbursement completion date in YYYY-MM-DD UTC. Use this for flexible reimbursements that have no posted date. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit: APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add: BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. POLICY is not returned by default. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Statement Payments

**Slug:** `NAVAN_LIST_STATEMENT_PAYMENTS`

Return one cursor page of statement payments and statement payment refunds for a required documented date search. Use activity_type to distinguish Statement Payment from Statement Payment Refund records.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum statement payments in this page (1-500). |
| `cursor` | string | No | Opaque cursor returned as next_cursor by the preceding page. Omit for the first page and pass it back unchanged. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the payment is flagged. |
| `regions` | array | No | ERP region names to include; multiple values use OR logic. |
| `itemized` | boolean | No | Filter by whether the payment has line items. |
| `personal` | boolean | No | Filter by whether the payment is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | ERP department names to include; multiple values use OR logic. |
| `flag_reason` | string | No | Flag reason to include. RECEIPT_MISSING is documented as an example, not a complete enum. |
| `flag_status` | string | No | Flag status to include. PENDING_APPROVER is documented as an example, not a complete enum. |
| `cost_centers` | array | No | ERP cost-center names to include; multiple values use OR logic. |
| `subsidiaries` | array | No | ERP subsidiary names to include; multiple values use OR logic. |
| `date_modified` | string | No | Modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but Navan does not enumerate the complete value set. |
| `legal_entities` | array | No | ERP legal-entity names to include; multiple values use OR logic. |
| `approval_status` | array | No | Approval statuses to include; Navan does not enumerate all values. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not enumerate all values. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Transaction date in YYYY-MM-DD UTC. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Reimbursement completion date in YYYY-MM-DD UTC. Use this for flexible reimbursements that have no posted date. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit: APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add: BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. POLICY is not returned by default. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List TMC Users

**Slug:** `NAVAN_LIST_TMC_USERS`

Return one documented page of TMC company users.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number to return. |
| `size` | integer | No | Number of user records to return per page. |
| `cursor` | string | No | Opaque continuation cursor from a preceding response. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Transaction Activities

**Slug:** `NAVAN_LIST_TRANSACTION_ACTIVITIES`

Return one cursor page of activity history for a single Navan Expense transaction, newest first. The transaction must belong to the connected company; optionally filter to public or administrator-private activity. This endpoint is available only to eligible companies.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `size` | integer | No | Maximum activities in this page (1-500). |
| `cursor` | string | No | Opaque next_cursor from a preceding page; omit for the first page. |
| `transaction_id` | string | Yes | Transaction identifier in a Navan Expense-supported format: expense UUID, ipi ID, Stripe charge or balance ID, Adyen repayment ID, or Connect/external transaction UUID. Authorization IDs (iauth IDs) are not accepted. |
| `is_admin_private` | boolean | No | Filter by administrator-private status. Omit to return both public and administrator-private activities. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Transaction Receipts

**Slug:** `NAVAN_LIST_TRANSACTION_RECEIPTS`

Return one cursor page of receipt links for selected Navan transaction families and a documented date search. Transactions without receipts are included with null links; returned presigned URLs should not be cached.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum receipt rows in this page (1-500). |
| `cursor` | string | No | Opaque next_cursor from a preceding page. Omit for the first page and repeat the original transaction types and date filters when continuing. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the transaction is flagged. |
| `regions` | array | No | Reporting-data regions to include. |
| `itemized` | boolean | No | Filter by whether the transaction is itemized. |
| `personal` | boolean | No | Filter by whether the transaction is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | Reporting-data departments to include. |
| `flag_reason` | string | No | Flag reason. RECEIPT_MISSING is an example, not a complete enum. |
| `flag_status` | string | No | Flag status. PENDING_APPROVER is an example, not a complete enum. |
| `cost_centers` | array | No | Reporting-data cost centers to include. |
| `subsidiaries` | array | No | Reporting-data subsidiaries to include. |
| `date_modified` | string | No | Modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but Navan does not enumerate the complete value set. |
| `legal_entities` | array | No | Reporting-data legal entities to include. |
| `approval_status` | array | No | Approval statuses to include; Navan does not enumerate all values. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not enumerate all values. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Transaction date in YYYY-MM-DD UTC. |
| `transaction_types` | array | Yes | Transaction families whose receipt links to return. Values are sent as repeated type query parameters. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Reimbursement completion date in YYYY-MM-DD UTC. Use this for flexible reimbursements without a posted date. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit: APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add: BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Transactions

**Slug:** `NAVAN_LIST_TRANSACTIONS`

Return one cursor page across selected Navan transaction families, or fetch a batch using repeated transaction IDs. Normal search requires transaction types and at least one documented date filter. Bulk-ID mode does not require type or date; Navan does not specify that they must be absent, so combinations are passed through.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Posted date in YYYY-MM-DD UTC. |
| `size` | integer | No | Maximum transactions in this page (1-500). |
| `cursor` | string | No | Opaque next_cursor from a preceding page. Omit for the first page; when continuing, repeat the original normal-search filters or transaction IDs. |
| `fields` | string | No | Comma-separated transaction field names to return. |
| `date_to` | string | No | Inclusive end of the posted-date range in YYYY-MM-DD UTC. |
| `flagged` | boolean | No | Filter by whether the transaction is flagged. |
| `regions` | array | No | ERP region names to include. |
| `itemized` | boolean | No | Filter by whether the transaction has line items. |
| `personal` | boolean | No | Filter by whether the transaction is personal. |
| `date_from` | string | No | Inclusive start of the posted-date range in YYYY-MM-DD UTC. |
| `departments` | array | No | ERP department names to include. |
| `flag_reason` | string | No | Flag reason. RECEIPT_MISSING is an example, not a complete enum. |
| `flag_status` | string | No | Flag status. PENDING_APPROVER is an example, not a complete enum. |
| `cost_centers` | array | No | ERP cost-center names to include. |
| `subsidiaries` | array | No | ERP subsidiary names to include. |
| `date_modified` | string | No | Modification date in YYYY-MM-DD UTC. |
| `receipt_state` | string | No | Receipt-state filter. RECEIPT_AFFIDAVIT_SUBMITTED is documented, but Navan does not enumerate the complete value set. |
| `legal_entities` | array | No | ERP legal-entity names to include. |
| `approval_status` | array | No | Approval statuses to include; Navan does not enumerate all values. |
| `erp_sync_status` | array | No | ERP synchronization statuses to include; Navan does not enumerate all values. |
| `transaction_ids` | array | No | Transaction IDs for bulk lookup, sent as repeated id query parameters. Navan recommends batches of 100-500 IDs. Type and date filters are not required in this mode, and Navan does not say they must be omitted. |
| `date_modified_to` | string | No | Inclusive end of the modification-date range in YYYY-MM-DD UTC. |
| `transaction_date` | string | No | Transaction date in YYYY-MM-DD UTC. |
| `transaction_types` | array | No | Transaction families for normal search. Required with at least one date filter when transaction_ids is omitted. Sent as one comma-separated type query value. |
| `date_modified_from` | string | No | Inclusive start of the modification-date range in YYYY-MM-DD UTC. |
| `reimbursement_date` | string | No | Reimbursement completion date in YYYY-MM-DD UTC. Use this for flexible reimbursements without a posted date. |
| `transaction_date_to` | string | No | Inclusive end of the transaction-date range in YYYY-MM-DD UTC. |
| `exclude_field_groups` | string | No | Comma-separated default field groups to omit: APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. |
| `include_field_groups` | string | No | Comma-separated field groups to add: BOOKING, ERP, INVITER, MILEAGE, POLICY, TAX, TRAVELER_HR, APPROVAL, CUSTOM_FIELD, EXCHANGE_RATE, FEE, FLAG, LINE_ITEM, RECEIPT, REIMBURSEMENT, REPORTING_DATA, or VENDOR. POLICY is not returned by default. |
| `reimbursement_date_to` | string | No | Inclusive end of the reimbursement-date range in YYYY-MM-DD UTC. |
| `transaction_date_from` | string | No | Inclusive start of the transaction-date range in YYYY-MM-DD UTC. |
| `reimbursement_date_from` | string | No | Inclusive start of the reimbursement-date range in YYYY-MM-DD UTC. |
| `last_approver_action_date` | string | No | Approval action date in YYYY-MM-DD UTC. |
| `last_approver_action_date_to` | string | No | Inclusive end of the approval-action range in YYYY-MM-DD UTC. |
| `last_approver_action_date_from` | string | No | Inclusive start of the approval-action range in YYYY-MM-DD UTC. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Submit Custom Field Option Operations

**Slug:** `NAVAN_SUBMIT_CUSTOM_FIELD_OPTION_OPERATIONS`

Submit 1 to 5,000 CREATE, UPDATE, UPSERT, or DELETE operations for one Navan custom field as an asynchronous job. This action can delete options; poll the returned job ID to determine completion.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `field_name` | string | Yes | Provider identifier of the custom field whose options should be changed. Must start with a letter or digit; embedded slashes are accepted and encoded. |
| `operations` | array | Yes | One to 5,000 ordered option mutations for the asynchronous job. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Transactions

**Slug:** `NAVAN_UPDATE_TRANSACTIONS`

Update supported ERP, accounting, HR, and custom-field values for 1 to 100 Navan transactions. Navan processes each item independently, so a successful HTTP response can contain both successful and failed item outcomes. Updated transaction data may take up to four hours to appear in GET results.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `transactions` | array | Yes | One to 100 transaction updates, processed independently by Navan. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |