Navigatr API

Name: Navigatr API API
Brand: Navigatr API
Availability: InStock

✓ Official Vendor SpecIdentity AuthDirectory ServicesapiKey1 EndpointsREST

For Agents

Look up a Navigatr user record by ID using a single authenticated GET request.

Connect the Navigatr API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Navigatr API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Navigatr API API.

Retrieve a Navigatr user detail record by user ID via GET /user_detail/{id}

Authenticate Navigatr requests using the X-Access-Token header

Pull Navigatr user attributes into external CRM, analytics, or support systems

Verify that a Navigatr user ID exists before initiating downstream workflows

GET STARTED

Start building with Navigatr API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Navigatr API API for, with concrete tasks.

★ Cross-System User Lookup

Operations and support tooling outside the Navigatr platform often holds only the Navigatr user ID and needs the corresponding profile fields to render context for an agent or CSM. A single GET to /user_detail/{id} returns the user record so the calling system can hydrate its own view without screen-scraping. Wiring the lookup is straightforward because the surface contains only one operation.

Call GET /user_detail/12345 and return the JSON user record for display in the support agent console.

CRM Contact Enrichment

Sales and customer success tools often hold a Navigatr ID against each contact and benefit from refreshing Navigatr profile fields onto the CRM record. Iterating over contacts and calling /user_detail/{id} keeps the CRM record aligned with Navigatr without manual exports. The workflow runs in batches because the API is read-only and per-record.

For each CRM contact carrying a navigatr_id, call /user_detail/{id} and update the CRM record with the latest Navigatr profile fields.

Validation Before Workflow Triggers

Automation tools that reference Navigatr user IDs in upstream events (webhooks, message queues) need a quick existence check before kicking off downstream work. A guarded GET /user_detail/{id} returns the record on success and an error on a missing or revoked user, allowing the workflow to short-circuit safely. This avoids surfacing stale or invalid IDs to downstream systems.

Before processing a Navigatr-triggered webhook, call /user_detail/{id} and only continue when the response status is 200.

Agent-Driven Navigatr Profile Lookup via Jentic

Agent assistants that triage support tickets or onboard users need a one-shot Navigatr profile read without managing the X-Access-Token directly. Through Jentic the agent searches by intent, loads the schema for /user_detail/{id}, and executes it with the user ID, while Jentic injects the access token from the vault. The agent never holds the raw token.

Search Jentic for 'look up a Navigatr user by ID', load the schema for /user_detail/{id}, and execute it with the user ID extracted from the support ticket.

Key Endpoints

1 endpoints — the navigatr api provides programmatic read access to user records inside the navigatr platform.

METHOD

PATH

DESCRIPTION

GET

/user_detail/{id}

Retrieve a Navigatr user detail record by ID

GET

/user_detail/{id}

Retrieve a Navigatr user detail record by ID

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Navigatr X-Access-Token is stored encrypted in the Jentic vault and injected into each request header at execution time. Agents call /user_detail/{id} via Jentic without ever seeing the raw token.

Intent-based discovery

Agents search Jentic by intent (e.g. 'look up a Navigatr user by ID') and Jentic returns the single Navigatr operation with its input schema for direct execution.

Time to first call

Direct integration with Navigatr: a few hours including auth setup and error handling. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Okta API

Enterprise identity platform with full user CRUD and SSO for cases needing more than read-by-ID.

Pick Okta when the agent needs full user lifecycle management or SSO, not just a profile read.

Alternative

Auth0 Management API

Identity and user management API with broader profile management surface.

Choose Auth0 when the workflow needs user creation, role assignment, or login analytics in addition to profile reads.

Complementary

HubSpot Contacts API

CRM contact store commonly enriched with attributes pulled from Navigatr user records.

Combine with Navigatr when refreshing HubSpot contacts using Navigatr profile fields keyed by user ID.

FAQs

Specific to using Navigatr API API through Jentic.

What authentication does the Navigatr API use?

The Navigatr API authenticates each request with an X-Access-Token header carrying the API key. Jentic stores the token in its vault and injects it at execution time so the agent never sees the raw secret.

Can I list all Navigatr users with this API?

No. The current OpenAPI surface exposes only a single read operation, GET /user_detail/{id}, which returns one user at a time keyed by ID. Iterating over a known set of IDs is the supported way to read multiple users.

What are the rate limits for the Navigatr API?

The OpenAPI spec does not publish rate limits. Throttling is governed at the account level — confirm your plan limits with Navigatr support before running a high-volume enrichment loop against /user_detail/{id}.

How do I look up a Navigatr user through Jentic?

Run pip install jentic, search for 'look up a Navigatr user by ID', load the schema for /user_detail/{id}, and execute it with the user ID. Jentic adds the X-Access-Token header from your vault entry. Sign up at https://app.jentic.com/sign-up.

Does this API let me create or update Navigatr users?

No. The current surface is read-only. Creating, updating, or deleting Navigatr users must be performed through the Navigatr application, which is not covered by this OpenAPI spec.