Sandbox Withterminal Terminal API

Name: Terminal API
Brand: Terminal API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact Managementbearer29 EndpointsREST

For Agents

Programmatically public token exchange, create connection. Covers 29 operations with bearer authentication.

Install Jentic One Beta

Connect the Terminal API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Terminal 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Terminal API.

Public Token Exchange

Create Connection

List All Connections

Get Current Connection

GET STARTED

Start building with Terminal API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Terminal API for, with concrete tasks.

★ CRM Operations

Use the Terminal API to perform crm operations programmatically. The API provides 29 endpoints covering core functionality including public token exchange, create connection, list all connections.

Call POST /public-token/exchange to public token exchange

Automated Vehicles Management

Automate vehicles operations by combining multiple Terminal API endpoints. Agents can create connection and then list all connections in a single workflow.

Call POST /connections to create connection, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Terminal API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'public token exchange', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

29 endpoints — terminal is a unified api that makes it easy to integrate with the leading telematics service providers.

METHOD

PATH

DESCRIPTION

POST

/public-token/exchange

Public Token Exchange

POST

/connections

Create Connection

GET

/connections

List All Connections

GET

/connections/current

Get Current Connection

PATCH

/connections/current

Update Current Connection

POST

/syncs

Request Sync

GET

/syncs

List Sync History

GET

/syncs/{id}

Get Sync Job Status

POST

/public-token/exchange

Public Token Exchange

POST

/connections

Create Connection

GET

/connections

List All Connections

GET

/connections/current

Get Current Connection

PATCH

/connections/current

Update Current Connection

POST

Why Jentic?

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

Credential isolation

Terminal API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'public token exchange') and Jentic returns the matching Terminal API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Terminal API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Terminal API through Jentic.

What authentication does the Terminal API use?

The Terminal API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I public token exchange with the Terminal API?

Yes. Use the POST /public-token/exchange endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Terminal API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I public token exchange through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'public token exchange'. Jentic returns the matching Terminal API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Terminal API have?

The Terminal API exposes 29 endpoints covering vehicles, connections, data management operations.

Sandbox Withterminal Terminal API

Connect the Terminal API to your agent

Capabilities

Start building with Terminal API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs