---
title: Navan API Integration on Truto
slug: navan
category: Travel
canonical: "https://truto.one/integrations/detail/navan/"
---

# Navan API Integration on Truto



**Category:** Travel  
**Status:** Beta

## Unified APIs

### Unified User Directory API

- **Users** — The User object represents a User.

## How it works

1. **Link your customer's Navan account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach Navan.** The Proxy API is a 1-to-1 mapping of the Navan API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Automate Navan provisioning from your HRIS platform** — HR and workforce management SaaS companies can push employee directory data into Navan so new hires get instant access with the right cost center, manager approver, and travel policy assigned on day one.
- **Deprovision Navan access on employee offboarding** — Identity and HR platforms can automatically deactivate Navan users the moment an employee is terminated upstream, revoking corporate card and booking access without manual IT intervention.
- **Keep org structure in sync for travel approvals** — When managers, departments, or cost centers change in your customer's source of truth, your product can mirror those updates into Navan so trip approval chains and policy tiers stay accurate.
- **Offer Navan as a native connector in your app** — Instead of building and maintaining Navan's OAuth2 flow, user schema mapping, and pagination logic yourself, ship a native Navan integration to your customers through Truto's unified directory layer.

## What you can build

- **One-click Navan connection for end customers** — Embed a hosted auth flow so your users can connect their Navan workspace without you handling OAuth2 token storage or refresh.
- **Employee directory sync into Navan** — Create and update Navan user records — including name, email, department, and manager — from your product whenever upstream HR data changes.
- **Automated joiner-mover-leaver workflows** — Trigger Navan user creation on hire, attribute updates on role change, and deactivation on termination, all driven by events in your platform.
- **Manager and approver hierarchy mapping** — Resolve manager relationships from your source system and apply them to Navan users so travel approvals route to the correct reviewer.
- **Directory drift detection and reconciliation** — Periodically pull Navan users via the unified directory API and surface mismatches against your customer's system of record so admins can resolve drift.

## FAQs

### How does authentication to Navan work through Truto?

Navan uses OAuth2. Truto handles the end-user authorization flow, token storage, and refresh, so your customers connect their Navan workspace once and your product gets a stable connection to call against.

### Which Navan data is available today through Truto?

Navan is exposed through Truto's Unified User Directory API, covering employee directory records such as name, email, department, cost center, manager, and active/inactive status — the data needed to drive provisioning and approval workflows.

### Can I push users into Navan, or is it read-only?

The Unified User Directory API supports both reading and writing user records, so you can provision new Navan users, update attributes like department or manager, and deactivate users from your application.

### What if I need bookings, expenses, or transaction data from Navan?

Navan's bookings and expenses endpoints aren't wired up yet — those tools are built on request. Reach out to Truto with your use case and we'll prioritize the specific resources and operations you need.

### How fresh is the data synced from Navan?

Truto supports scheduled syncs and on-demand fetches against Navan's REST API. You control the polling cadence per connection, and writes propagate to Navan in real time when your app makes the call.

### How are Navan's custom fields and policy tiers handled?

Navan-specific attributes that don't map to the unified schema — such as assigned travel policy tier — are accessible via passthrough so you can read and write them without losing the benefits of the unified directory model.