Navan (formerly TripActions) is a corporate travel and expense management platform unifying travel booking, corporate cards, expense reporting, and analytics. It helps companies manage travel policies, track spending, monitor compliance, and cut costs across flights, hotels, and ground transport. Its API exposes booking records, admin reporting, travel spend analytics, carbon emissions, and performance metrics.
Power end-to-end data operations for your Navan API API with Nexla. Our bi-directional Navan API connector is purpose-built for Navan API, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Navan API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Navan API workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
The Navan API uses two-legged OAuth 2.0 (client credentials grant) for service-to-service authentication. This approach does not require user interaction or a browser-based authorization flow — Nexla exchanges your Client ID and Client Secret directly for a short-lived Bearer access token, which is then used to authenticate all API requests.
To create a Navan API credential in Nexla, you will need a Client ID, Client Secret, and the Access Token URL from Navan. These credentials are generated in the Navan Admin portal by a Navan company administrator.
Follow the steps below to generate API credentials in your Navan account:
Sign in to the Navan Admin portal at app.navan.com using an account with administrator privileges.
Navigate to Travel > Settings > Integrations in the left-hand navigation menu.
Locate the Navan API Credentials section and click Create New.
In the Description field, enter a descriptive name for this API credential (for example, Nexla Integration). The description helps you identify the credential later if you need to rotate or revoke it.
Optionally, enter one or more Allowed IP Addresses or a Subnet Mask to restrict which IP addresses may use this credential. This is a recommended security practice for production integrations.
Click Create. A pop-up window will display your newly generated credentials, including:
Client ID — The unique public identifier for this API credential.
Secret Key — The confidential password paired with the Client ID.
Important
Copy your Client ID and Secret Key immediately and store them securely. Once the pop-up is closed, the Secret Key cannot be retrieved again. If you lose the Secret Key, you must delete the credential and create a new one.
Click Copy All to copy all credential details to your clipboard, or copy each value individually. Store these values in a secure location (for example, a password manager or secrets vault) before closing the dialog.
Click Done to close the pop-up.
The Access Token URL for Navan is https://api.navan.com/ta-auth/oauth/token. This is the endpoint Nexla will use to exchange your Client ID and Client Secret for a Bearer access token. The default value is pre-populated in the Nexla credential form.
Additional information about Navan API credential setup is available in the Navan Help Center.
To create a new Navan API credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
The Navan API connector uses two-legged OAuth 2.0, also called the client credentials grant. In this flow, Nexla uses your Client ID and Client Secret to request an access token directly from Navan's token endpoint, without redirecting a user to a browser. The resulting Bearer token is automatically attached to each API request Nexla makes on your behalf.
Enter the Client ID obtained from the Navan Admin portal in the Client ID field. The Client ID is the unique public identifier assigned to your API credential.
Enter the Client Secret (Secret Key) obtained from the Navan Admin portal in the Client Secret field. The Client Secret is treated as a password and is masked after entry.
The Client Secret is stored securely and encrypted at rest. Nexla will never display it in plain text after the credential has been saved.
Verify the Access Token URL field. The default value https://api.navan.com/ta-auth/oauth/token is pre-populated and is the correct token endpoint for the Navan production environment. Update this value only if Navan has provided a different token endpoint for your account.
Verify the API Base URL field. The default value https://app.navan.com is pre-populated as the base URL for Navan API endpoints. Update this value only if Navan has provided a different base URL for your account.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Navan API connector tile, then select the credential that will be used to connect to your Navan account, and click Next; or, create a new Navan API credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Navan API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Cancel Booking Invoice Task
Cancels an in-progress booking invoice generation task by its unique task UUID. Use this endpoint when a previously initiated invoice generation task must be stopped before it completes — for example, when it was started with incorrect parameters.
Enter the UUID of the invoice generation task to cancel in the Task UUID field. This UUID is returned when an invoice task is started using the Start Booking Invoice Task endpoint.
This endpoint performs a cancellation action (HTTP PUT) rather than retrieving data. It is primarily useful for operational workflows that manage multi-step invoice generation processes. Additional details about booking invoice tasks are available in the Navan Booking Invoice API documentation.
Get Carbon Calculations (Batch)
Calculates carbon emissions for multiple travel segments in a single request. Use this endpoint when you need to compute emissions data for a batch of trips simultaneously, which is more efficient than submitting segments one at a time.
This endpoint accepts a batch of travel segment objects in the request body. No additional template configuration parameters are required beyond selecting this endpoint. The request body is pre-configured by the template.
The endpoint returns an array of carbon emissions calculations in the $.data[*] path of the response, with one record per input travel segment.
Navan supports three globally recognized carbon calculation methodologies: DEFRA, ICAO, and TREMOD. The methodology used is determined by your Navan account configuration. For more details, see the Navan Carbon API documentation.
Get Carbon Calculations
Calculates carbon emissions for travel segments with a specified calculation method and reference identifier. Use this endpoint when you need detailed carbon calculations for individual travel segments and want to specify the calculation methodology.
Configure the following template parameters:
Reference — A unique reference string you assign to this calculation request, used to correlate the response with your input data.
Calculation Methods — The carbon calculation methodology or methodologies to apply (for example, DEFRA, ICAO, or TREMOD). Navan supports multiple globally recognized standards.
Segments — The travel segment or segments for which emissions should be calculated. Each segment typically includes origin, destination, travel class, and travel type.
For detailed information about supported calculation methods and segment formats, see the Navan Carbon API documentation.
Get Performance Summary
Retrieves performance metrics for a company, including spend, user adoption rates, and other key performance indicators. Use this endpoint to monitor overall travel program health and report on adoption and engagement trends.
Configure the following template parameters:
Company UUID — The unique identifier for your Navan company account. This value can be found in the Navan Admin portal under company settings.
Spend Params — Parameters defining the spend metrics to include in the summary.
Active Users Params — Parameters defining how active user metrics are calculated and filtered.
Adoption Params — Parameters controlling adoption rate calculations and thresholds.
Hotel Attachments Params — Parameters for hotel attachment rate metrics, which measure how often hotel bookings accompany flight bookings.
Initiates an asynchronous task to generate invoices for bookings, with optional filters for date range and specific booking UUIDs. Use this endpoint to trigger invoice generation for a batch of bookings, then poll or retrieve the results once the task completes.
Configure the following optional filter parameters to control which bookings are included in the generated invoices:
Booking UUIDs — A list of specific booking UUIDs to include. Leave blank to include all bookings within the specified date range.
From Booking UUID — A cursor-based starting point for paginated invoice generation. Useful for resuming a large invoice task.
From Invoice Date — The start date (inclusive) for filtering bookings by invoice date, in YYYY-MM-DD format.
To Invoice Date — The end date (inclusive) for filtering bookings by invoice date, in YYYY-MM-DD format.
Page Size — The number of bookings to process per page in the invoice task.
The endpoint returns a task identifier in the $.data path of the response. Use this identifier with the Cancel Booking Invoice Task endpoint if you need to stop the task before it completes.
Initiates a report generation task for unused travel credits, with filters for credit status, expiration date range, and export format. Unused travel credits represent airline credits from cancelled or changed bookings that have not yet been applied to new bookings.
Configure the following parameters to control report generation:
Role — The administrative role context for the report (for example, admin or superadmin). Determines the scope of data accessible in the report.
File Type — The output format for the generated report (for example, CSV or XLSX).
Statuses — Filter credits by their status (for example, active, expired, or redeemed).
Expiration Date From — The start date for filtering credits by expiration date, in YYYY-MM-DD format.
Expiration Date To — The end date for filtering credits by expiration date, in YYYY-MM-DD format.
Format Context — Additional formatting context for the report output.
Unused Tickets — Filter to include or exclude unused ticket records.
Create Elastic Scroller — Whether to create a server-side scroll context for large result sets.
Initiates a traveler report generation task with filters and export configuration. Use this endpoint to produce reports summarizing traveler activity, booking patterns, and travel behavior for employees within your organization.
Configure the following parameters:
Role — The administrative role context for the report (for example, admin). Determines the scope of traveler data included.
The response data is returned in the $.data path. The report is generated asynchronously, and the response will include a task or download identifier for retrieving the completed report.
Initiates a transactions report with comprehensive filtering options, covering booking dates, travel dates, users, currency, and more. Use this endpoint to generate detailed transaction-level data for expense reconciliation, financial reporting, or audit purposes.
Configure the following filter parameters as needed:
Role — The administrative role context for the report (for example, admin).
From Epoch Seconds / To Epoch Seconds — Filter transactions by booking creation date, expressed as Unix epoch seconds.
From Epoch Seconds Updated Date / To Epoch Seconds Updated Date — Filter transactions by their last-updated date, expressed as Unix epoch seconds.
From Epoch Seconds Travel Date / To Epoch Seconds Travel Date — Filter transactions by the travel date, expressed as Unix epoch seconds.
Text — A free-text search string to filter transactions by traveler name, booking ID, or other text fields.
User UUIDs — Filter to include only transactions for specific user UUIDs.
Currency — The currency in which amounts should be reported (for example, USD or EUR).
Cascading — Whether to include data from subsidiary or child company accounts.
Manager Access Type / Manager Access Values — Parameters that control manager-level data access scope.
Filter By Traveller — Whether to filter results by individual traveler.
Booking IDs — Filter to specific booking identifiers.
Retrieves travel spend analytics with filtering, grouping, and carbon metrics. Use this endpoint to analyze spending patterns by category, department, date range, or other dimensions for financial planning and reporting.
Configure the following parameters to shape the analytics result:
Role — The administrative role context (for example, admin).
Booking Start Epoch Sec / Booking End Epoch Sec — Filter by booking creation date range, expressed as Unix epoch seconds.
Travel Start Date / Travel End Date — Filter by travel date range in YYYY-MM-DD format.
Type — The travel category to filter (for example, flight, hotel, or car).
Source — The booking source channel to filter.
Exclude Type — Travel categories to exclude from results.
Filter By / Exclude — Additional dimensional filters and exclusions.
Merchant Data Category — Filter by merchant category for expense-level analytics.
Date Range Type — Specify whether date ranges apply to the booking date or the travel date.
Group By — The dimension by which results should be aggregated (for example, by department, traveler, or category).
Currency — The output currency for spend amounts.
Amount Field — The spend field to use as the primary amount metric.
Results are returned as an array in the $.data[*] path of the response, with one record per grouping combination.
Downloads travel spend analytics as a file with filtering, grouping, and carbon metrics. Use this endpoint when you need a file-based export of travel spend data rather than a JSON response — for example, to deliver the data to a reporting team or load it into a data warehouse via file transfer.
This endpoint accepts the same filtering and grouping parameters as the Get Travel Spend endpoint, including Role, Booking date ranges, Travel date ranges, Type, Source, Exclude Type, Filter By, Exclude, Merchant Data Category, Date Range Type, Group By, Currency, and Amount Field. Configure these parameters to define the scope and structure of the export.
The response is returned at the $ root path and contains file content or a download reference.
Retrieves average rate metrics for travel spend analysis, filtered by role and date range. Use this endpoint to track average hotel room rates, airfare, or other travel costs over time to benchmark against market rates or policy limits.
This endpoint accepts the same filtering and grouping parameters as the Get Travel Spend endpoint, including Role, Booking date ranges, Travel date ranges, Type, Source, Exclude Type, Filter By, Exclude, Merchant Data Category, Date Range Type, Group By, Currency, and Amount Field.
Results are returned as an array in the $.data[*] path of the response.
Downloads average rate metrics as a file with a configurable format and filters. Use this endpoint when you need a file-based export of average rate data for reporting or data transfer purposes.
This endpoint accepts the same filtering and grouping parameters as the Get Average Rate endpoint. Configure the Role, date ranges, grouping, and currency parameters to define the scope of the export.
The response is returned at the $ root path and contains file content or a download reference.
Retrieves average cost metrics for travel spend analysis by role and date range. Use this endpoint to understand the average all-in cost of travel bookings across different categories, departments, or time periods.
This endpoint accepts the same filtering and grouping parameters as the Get Travel Spend endpoint, including Role, Booking date ranges, Travel date ranges, Type, Source, Exclude Type, Filter By, Exclude, Merchant Data Category, Date Range Type, Group By, Currency, and Amount Field.
Results are returned as an array in the $.data[*] path of the response.
Downloads average cost metrics as a file with a configurable format and filters. Use this endpoint when you need a file-based export of average cost data for reporting or downstream processing.
This endpoint accepts the same filtering and grouping parameters as the Get Average Cost endpoint. Configure the Role, date ranges, grouping, and currency parameters to define the scope of the export.
The response is returned at the $ root path and contains file content or a download reference.
Initiates a detailed query-based report download with extensive filtering options. Use this endpoint when you need a comprehensive, customizable export of booking and transaction data that goes beyond the standard reporting endpoints.
Configure the following filter parameters to scope the report:
Role — The administrative role context for the report.
From Epoch Seconds / To Epoch Seconds — Filter by booking creation date range, expressed as Unix epoch seconds.
From/To Epoch Seconds Updated Date — Filter by last-updated date range.
From/To Epoch Seconds Travel Date — Filter by travel date range.
Text — A free-text search string for filtering records.
User UUIDs — Filter to specific user UUIDs.
Currency — The output currency for amounts.
Cascading — Whether to include data from subsidiary accounts.
Manager Access Type / Manager Access Values — Manager-level data access scope controls.
Filter By Traveller — Whether to filter results by individual traveler.
Booking IDs — Filter to specific booking identifiers.
Results are returned as an array in the $.data[*] path of the response.
Initiates a carrier share analysis report download with airline and alliance filters. Use this endpoint to analyze what percentage of your company's air travel is booked with preferred carriers or alliances, which is important for negotiating corporate airfare agreements.
Configure the following parameters:
Role — The administrative role context for the report.
File Type — The output format for the report (for example, CSV or XLSX).
From/To Epoch Seconds — Filter by booking creation date range, expressed as Unix epoch seconds.
From/To Epoch Seconds Updated Date — Filter by last-updated date range.
From/To Epoch Seconds Travel Date — Filter by travel date range.
Text — A free-text search string for filtering records.
User UUIDs — Filter to specific user UUIDs.
Currency — The output currency for amounts.
Cascading — Whether to include data from subsidiary accounts.
Manager Access Type / Manager Access Values — Manager-level data access scope controls.
Filter By Traveller — Whether to filter results by individual traveler.
Results are returned as an array in the $.data[*] path of the response.
Retrieves travel spend metrics for a specific team event identified by its UUID. Use this endpoint to analyze spending for a particular offsite, conference, or team gathering — enabling event-level cost tracking and budget management.
Configure the following parameters:
Team Event UUID — The unique identifier of the team event. This value can be found in the Navan Admin portal under the Team Events section.
Booking Start/End Epoch Sec — Filter by booking date range for the event.
Travel Start/End Date — Filter by travel date range in YYYY-MM-DD format.
Type, Source, Exclude Type, Filter By, Exclude, Merchant Data Category — Additional filters to refine which spend records are included.
Date Range Type, Group By, Currency, Amount Field — Controls for how results are grouped and expressed.
Results are returned as an array in the $.data[*] path of the response.
Retrieves faceted search results showing the available filter dimensions for a specific team event. Use this endpoint to discover what filter values are available before querying team event spend data, which helps ensure accurate filtering.
Configure the following parameters:
Team Event UUID — The unique identifier of the team event to query.
Booking Start/End Epoch Sec — The booking date range for the facet search.
Travel Start/End Date — The travel date range in YYYY-MM-DD format.
Type, Source, Exclude Type, Filter By, Exclude, Merchant Data Category, Date Range Type — Filters that shape which facet values are returned.
Results are returned as an array in the $.data[*] path of the response.
Get Facet Search Bar for Team Event
Retrieves faceted search bar results with text search support for a specific team event. Use this endpoint to perform free-text searches within the available filter facets for a team event, enabling dynamic filter population in reporting dashboards.
Configure the following parameters, in addition to the standard facet search parameters:
Team Event UUID — The unique identifier of the team event to query.
Text — The free-text search string to apply within the facet values.
Field — The facet field on which the text search should be performed (for example, department or traveler name).
Booking Start/End Epoch Sec, Travel Start/End Date, Type, Source, Exclude Type, Filter By, Exclude, Merchant Data Category, Date Range Type — Standard filters for scoping the facet search.
Results are returned as an array in the $.data[*] path of the response.
Get Average Trip Cost for Team Event
Retrieves average trip cost metrics for a specific team event by its UUID. Use this endpoint to understand the average per-person travel cost for a team event, which is useful for budgeting and benchmarking future events.
Configure the following parameters:
Team Event UUID — The unique identifier of the team event.
Booking Start/End Epoch Sec, Travel Start/End Date, Type, Source, Exclude Type, Filter By, Exclude, Merchant Data Category, Date Range Type, Group By, Currency, Amount Field — Filters and grouping options to shape the average trip cost calculation.
Results are returned as an array in the $.data[*] path of the response.
Generates and downloads the average trip costs report for a team event. Use this endpoint when you need a file-based export of average trip cost data for a specific event, for use in presentations, budget reviews, or financial reporting.
Configure the following parameters:
Team Event ID — The unique identifier of the team event for which the report should be generated.
Booking Start/End Epoch Sec, Travel Start/End Date, Type, Source, Exclude Type, Filter By, Exclude, Merchant Data Category, Date Range Type, Group By, Currency, Amount Field — Filters and grouping options for the report.
The response is returned at the $ root path and contains file content or a download reference.
Download Average Trip Report
Generates and downloads the average trip metrics report for a team event. Use this endpoint when you need a file-based export of average trip data for analysis or sharing outside of the Navan platform.
Configure the following parameters:
Team Event ID — The unique identifier of the team event for which the report should be generated.
Booking Start/End Epoch Sec, Travel Start/End Date, Type, Source, Exclude Type, Filter By, Exclude, Merchant Data Category, Date Range Type, Group By, Currency, Amount Field — Filters and grouping options for the report.
The response is returned at the $ root path and contains file content or a download reference.
Rebook Travel Alert
Triggers a rebook action for a specific travel alert, with an optional message. Use this endpoint to programmatically initiate rebooking for travelers affected by flight disruptions, cancellations, or other travel alerts managed through the Navan platform.
Configure the following parameters:
Alert ID — The unique identifier of the travel alert for which a rebook should be triggered. Travel alert IDs can be retrieved from the Navan Admin portal under Travel Alerts.
Message — An optional message to include with the rebook action, which may be communicated to the affected traveler.
This endpoint performs an action (HTTP POST) rather than retrieving data. It is intended for operational workflows that automate traveler rebooking in response to disruptions.
Update Impacted Users
Updates the list of impacted users associated with a specific travel alert. Use this endpoint to add or modify the list of travelers who are affected by a given travel alert, enabling targeted communications and rebooking actions.
Configure the following parameters:
Travel Alert UUID — The unique identifier of the travel alert to update.
User Emails — A list of email addresses for the users who should be marked as impacted by this alert.
Overridden By — The identifier of the administrator or system overriding the impacted user list.
Import Travel Alerts
Imports travel alerts in bulk from a provided data source. Use this endpoint to programmatically create multiple travel alerts at once, for example when ingesting disruption data from an external travel intelligence feed.
This endpoint submits a bulk import request (HTTP POST) to the Navan travel alert import endpoint. The request body should contain the alert data in the format expected by the Navan API. No additional template-level parameters are required beyond selecting this endpoint.
This endpoint performs a write action. It is intended for operational workflows that automate the creation of travel alerts from external data sources.
Get Spend Summary
Retrieves aggregated spend metrics and performance analytics for a specified date range. Use this endpoint for executive-level summaries of total travel spend, including breakdowns by period and category, as well as carbon-related spend metrics.
Configure the following parameters:
From Epoch Seconds / To Epoch Seconds — Filter by booking creation date range, expressed as Unix epoch seconds.
Start Date From Epoch Seconds / Start Date To Epoch Seconds — Filter by travel start date range, expressed as Unix epoch seconds.
Currency — The currency in which spend amounts should be reported.
Date Range Type — Whether date ranges apply to the booking date or the travel start date.
Source — Filter by booking source channel.
Filter By — Additional dimensional filters for the summary.
Period — The time period granularity for the summary (for example, monthly or quarterly).
Carbon Settings — Configuration for including carbon-related spend metrics in the summary.
Retrieves point of sales metrics and booking channel performance analytics. Use this endpoint to understand what proportion of bookings are made through Navan's platform versus other booking channels, which is useful for tracking adoption and optimizing travel program management.
This endpoint accepts the same filtering parameters as the Get Spend Summary endpoint, including From/To Epoch Seconds, Start Date From/To Epoch Seconds, Currency, Date Range Type, Source, Filter By, Period, and Carbon Settings.
Retrieves compliance and policy adherence metrics for travel bookings. Use this endpoint to measure how consistently travelers are booking within company travel policy, which is a key input for travel program management and savings analysis.
This endpoint accepts the same filtering parameters as the Get Spend Summary endpoint, including From/To Epoch Seconds, Start Date From/To Epoch Seconds, Currency, Date Range Type, Source, Filter By, Period, and Carbon Settings.
Retrieves a paginated list of all company bookings with optional filtering. This is one of the primary endpoints for extracting booking-level data from Navan, making it suitable for downstream financial reconciliation, analytics, and reporting workflows.
This endpoint supports pagination automatically — Nexla will iterate through all available pages, fetching up to 50 records per page, until all bookings have been retrieved or the configured page limit is reached.
The response returns booking records in the $.bookings[*] path of the response. Each record contains booking details such as booking ID, traveler, travel dates, amount, status, and more.
Bookings can be filtered by date range using the createdFrom and createdTo parameters, which accept date values in YYYY-MM-DD format or as Unix epoch timestamps.
For more information about the bookings endpoint, including the full list of available response fields and filter parameters, see the Navan Bookings API documentation.
Query TDS Data
Queries the Navan Travel Data Store (TDS) with filters and facet parameters for advanced reporting. The TDS provides a unified, queryable view of all travel data in your Navan account, enabling complex, ad-hoc data extraction beyond what standard reporting endpoints offer.
Configure the following parameters:
Role — The administrative role context for the query (for example, admin).
This endpoint supports pagination — Nexla will automatically iterate through pages starting at page 0, fetching up to 50 records per page, until all matching records have been retrieved.
Results are returned as an array in the $.data[*] path of the response.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Navan API data sources can also be manually configured to ingest data from any valid Navan API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
The Navan API base URL is https://app.navan.com by default. Most admin reporting endpoints follow the pattern https://app.navan.com/api/adminreporting/v2/{'{role}'}/..., where {'{role}'} is replaced with the appropriate role value such as admin or superadmin, and the bookings API uses the base https://app.navan.com/v1/bookings. The most common methods for Navan endpoints are GET for retrieving paginated lists of records (for example, the List Company Bookings and Query TDS endpoints), POST for endpoints that accept filter parameters in the request body and return analytics results (for example, Get Travel Spend, Get Compliance Metrics, and most admin reporting endpoints), and PUT for endpoints that perform update or cancellation actions (for example, Cancel Booking Invoice Task).
Date/time macros are particularly useful for Navan reporting endpoints that accept date range parameters in the URL or query string — many Navan endpoints accept fromEpochSeconds and toEpochSeconds parameters, which can be populated using Nexla macros to create rolling date-range queries. Lookup-based macros are useful for Navan endpoints that require path parameters such as a Company UUID or Team Event UUID, which you can populate from another Nexla data source rather than hardcoding them in the URL.
Path to Data is essential for Navan API responses that wrap result records within a nested structure — the correct path for most Navan admin reporting endpoints is $.data[*] or $.data, while the List Company Bookings endpoint returns records in $.bookings[*]. Metadata paths are useful for preserving Navan API response context such as total record counts, pagination tokens, or request timestamps that apply to all records in the response. You do not need to include Authorization headers — these are automatically managed by Nexla using the OAuth 2.0 Bearer token from your Navan API credential; additional headers may be required for specific Navan API versions or custom integrations.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Navan API data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
