Skip to main content

​
About Navan

Navan (formerly TripActions) is a corporate travel and expense platform. The Serval integration connects to the Navan Booking Data API so your workflows can pull your company’s travel booking report, including per-booking detail like passengers, pricing, policy compliance, and carbon emissions. The integration ships with one pre-installed workflow, “Get Navan Bookings from Last Week”. Serval sends your credentials only to the Navan host for the region you select on the connection. That is api.navan.com for the US and app-fra.navan.com for Europe/Frankfurt. Authentication: OAuth 2.0 client credentials (Client ID + Client Secret issued from the Navan Admin Dashboard). No user sign-in, no consent screen, and no scopes to configure. You do select the region your Navan account is hosted in. Data sync: On-demand only. Navan data is read when a workflow step runs - there is no background sync, no webhooks, and no scheduled imports.

​
What the Navan integration enables

The integration currently models a single resource from the Navan API: the company booking report. Other Navan endpoints are not yet available through Serval.

​
Get your credentials

Serval needs a Navan API credential - a Client ID and Secret Key - created from the Navan Integrations settings. You must have access to the Navan Admin Dashboard to create one.
1

Open the Navan Admin Dashboard

Log in to Navan on the web, click the Navan logo in the top left, and select Admin - or go directly to the Admin Dashboard.
2

Go to Integrations settings

Navigate to Travel, then Settings, then Integrations in the left menu, or use the direct link.
3

Create a new API credential

Scroll to the Navan API Credentials section and click Create new.
4

Name and create the credential

Enter a Description (this serves as the credential’s name). Optionally restrict it by Allowed IP Addresses or Subnet Mask. Click Create.
5

Copy the Client ID and Secret Key immediately

Copy both values from the confirmation pop-up - use Copy All to grab the Description, Client ID, and Secret Key together. Once the pop-up closes, the Secret Key is no longer accessible.
Navan shows the Secret Key exactly once, in the creation pop-up. If you lose it, use Rotate Key on the credential to get a new secret with the same Client ID, then update the Serval connection.
The Description and Client ID cannot be changed after creation. The Edit menu on an existing credential supports editing the allowed IP addresses or subnet masks, Rotate Key (new secret, same Client ID), and Revoke.

​
Connect in Serval

1

Open the Navan connection form in Serval

Find the Navan integration and start a new connection.
2

Enter an Instance Name

A free-text label for the connection (placeholder: “My Company”). It is used as both the connection’s identifier and its display name.
3

Select the API Region

Choose the region your Navan account is hosted in. US (api.navan.com) is the default, and an EU-hosted account must select Europe / Frankfurt (app-fra.navan.com). The wrong region makes authentication fail.
4

Enter the Client ID

Paste the Client ID from your Navan API credential.
5

Enter the Client Secret

Paste the Secret Key from your Navan API credential. After saving, this field displays masked (bullet characters plus the last 4 characters) with a control to replace it.
6

Submit the form

There are no scopes to configure. Serval talks to the API host for the region you selected.
The credential fields are not marked required, so the form will accept a blank submission. Bad or missing credentials only surface afterward through the connection test - double-check your values before saving.
When editing an existing connection, you do not need to re-enter the Client Secret: leaving a field blank (or leaving the masked secret untouched) keeps the stored value. Only replace the secret when you have rotated the key in Navan. Connections made before the API Region dropdown existed keep working unchanged. They use the US host, and their settings form shows US selected.

​
Verifying the connection

The integration includes one health check, Test Navan Connection. It requests a small sample of your booking report covering the last 90 days - Navan requires date filters on booking queries, so the check supplies them automatically - and confirms that authentication succeeds and booking data is accessible. Serval also re-runs the health check automatically when you save changes to the connection. On success: “Successfully connected to Navan Booking Data API and retrieved booking information ([number] total bookings available)” On failure (invalid credentials): “Unable to connect to Navan Booking Data API. The OAuth client credentials are invalid or expired. Please verify your Client ID and Client Secret in the Navan integration settings.”
If the connection test is green but a workflow returns no bookings, the date filters are the usual culprit: booking queries effectively require them, and the values must be epoch seconds. See “Booking queries return empty results” below.

​
Gotchas and troubleshooting

Every failure message starts with “Unable to connect to Navan Booking Data API.” For failures Serval recognizes, a status-specific explanation follows; otherwise that base message appears alone. If Navan rejects the credentials (401), the message continues: “The OAuth client credentials are invalid or expired. Please verify your Client ID and Client Secret in the Navan integration settings.” If the client lacks permission (403): “The OAuth client is not authorized to access Navan. Please ensure the client has been granted the necessary permissions in Navan.” If Navan itself errors (500, 502, or 503): “Navan returned a server error during authentication. This is likely a temporary issue - please try again later.”
An EU-hosted account left on the US region cannot authenticate. Serval sends the OAuth token exchange to api.navan.com, which does not know a credential issued for a Frankfurt-hosted account. The exchange is rejected, so every request fails. Navan rejects the credential rather than reporting a region mismatch, so the connection test reads as an authentication problem and points you at your Client ID and Secret Key. Check the region first. To fix it, edit the connection, select Europe / Frankfurt (app-fra.navan.com), and save. Serval re-runs the health check when you save, so you see the result immediately.
Navan only shows the Secret Key in the creation pop-up. There is no way to view it again. Use Rotate Key on the credential in Navan’s Integrations settings (you get a new secret with the same Client ID), then edit the Serval connection: choose to replace the masked Client Secret and paste the new value.
The connect form’s credential fields are not required, so a first-time submit with blank credentials is accepted by the UI. The problem only shows up when the connection test runs and reports invalid credentials. If this happens, edit the connection and fill in the Client ID and Client Secret.
No. The settings screen shows the Client Secret masked (bullet characters plus the last 4 characters), and saving with a blank or untouched secret preserves the stored value - the same applies to the Instance Name and Client ID. Renaming the instance or changing the Client ID alone is safe. Only re-enter the secret when rotating the key in Navan.
Navan’s booking report expects date filters, and all date values must be epoch seconds (whole-number Unix timestamps) - not milliseconds and not ISO date strings. This applies to all six date filters: createdFrom, createdTo, updatedFrom, updatedTo, startDateFrom, and startDateTo. Missing filters or wrong units yield empty results or a request error. The pre-installed workflow and the health check both supply created-date filters automatically.
There are no scopes to set. Navan does not use explicit scopes, because a single bookings-read capability always comes with the credential. There is no company domain or subdomain to enter either. The one host setting is the API Region dropdown, which chooses between api.navan.com for the US and app-fra.navan.com for Europe/Frankfurt.
Booking report pages are zero-based: Serval’s shipped workflow and health check start at page 0. The pre-installed workflow keeps requesting pages until the reported current page reaches the last page, and treats a response with no total page count as the end of the results. If you build your own pagination, also stop when a page returns fewer rows than you requested.
The integration currently covers a single resource: the company booking report. There is no dedicated single-booking endpoint - to fetch one booking, filter the report by its booking or trip identifier instead - and Navan’s people, policy, and invoice APIs are out of scope until they appear in the API specification.
Need help? Contact support@serval.com for assistance with your Navan integration.