canonical: https://jentic.com/apis/rtafleet.com/rtafleet

# RTA Fleet API

API for managing fleet vehicles, work orders, and parts programmatically in RTA Fleet Management. The API exposes 5 endpoints secured with bearer authentication.

## For AI agents

Programmatically get API token, search vehicles (enhanced). Covers 5 operations with bearer authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Get API Token
- Search Vehicles (Enhanced)
- Update Vehicle
- Extract Table Data
- Monitor RTA Fleet API operational status and events

## Use cases

### Communications Operations

Use the RTA Fleet API to perform communications operations programmatically. The API provides 5 endpoints covering core functionality including get API token, search vehicles (enhanced), get vehicle by id.

Example prompt: Call GET /information-management/{tenantId}/integrations/get-api-token to get API token

### Automated Authentication Management

Automate authentication operations by combining multiple RTA Fleet API endpoints. Agents can search vehicles (enhanced) and then get vehicle by id in a single workflow.

Example prompt: Call POST /asset-management/{tenantId}/vehicles/search-vehicles-enhanced to search vehicles (enhanced), then verify the result

### AI Agent Integration via Jentic

AI agents discover and call RTA Fleet 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.

Example prompt: Search Jentic for 'get API token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /information-management/{tenantId}/integrations/get-api-token | Get API Token |
| POST | /asset-management/{tenantId}/vehicles/search-vehicles-enhanced | Search Vehicles (Enhanced) |
| GET | /asset-management/{tenantId}/vehicles/{id} | Get Vehicle by ID |
| PUT | /asset-management/{tenantId}/vehicles/{id} | Update Vehicle |
| GET | /v0/extract/{tablename} | Extract Table Data |

## Key resources

- **Authentication** — Obtain API tokens for authenticating requests
- **Vehicles** — Manage fleet vehicles
- **DataExtract** — Extract data from RTA database tables

## Why Jentic

- **Setup:** Wiring the RTA Fleet API by hand means handling its bearer token, choosing between the api.momentum-prd.rtafleet.com and api.rtafleet.com hosts, and threading the tenant id through each vehicle call. Through Jentic you install once, import the RTA Fleet API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** RTA Fleet puts the tenant id and vehicle id in the URL path (/asset-management/{tenantId}/vehicles/{id}), so a rule can pin your agent to one tenant: it can search and read vehicles there and nothing else. You choose the operations it may call, so updating a vehicle is not included unless you add it.
- **Credential handling:** Your RTA Fleet bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search fleet vehicles' or 'get vehicle details by id', and Jentic returns the matching RTA Fleet operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the RTA Fleet API use?

The RTA Fleet API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get API token with the RTA Fleet API?

Yes. Use the GET /information-management/{tenantId}/integrations/get-api-token endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the RTA Fleet 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 get API token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get API token'. Jentic returns the matching RTA Fleet API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the RTA Fleet API have?

The RTA Fleet API exposes 5 endpoints covering authentication, vehicles, dataextract operations.

### Can I limit what my agent is allowed to do with the RTA Fleet API?

Yes. Because you run Jentic One yourself, your own rules decide which RTA Fleet operations and credentials the agent may use. Since the API carries the tenant id and vehicle id in the URL path, such as /asset-management/{tenantId}/vehicles/{id}, you can pin the agent to a single tenant and grant only read operations like Search Vehicles (Enhanced) and Get Vehicle by ID. Write operations such as Update Vehicle stay off unless you explicitly add them.