canonical: https://jentic.com/apis/roundtrip.ai/roundtrip

# Roundtrip EasyRoutes API

Route planning and delivery management API for Shopify merchants. The API exposes 19 endpoints secured with bearer authentication.

## For AI agents

Programmatically authenticate client for access token, list routes. Covers 19 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- Authenticate client for access token
- List routes
- Get route by ID
- Add stops to route
- Delete stops from route
- Update stop items

## Use cases

### Maps and Geolocation Operations

Use the EasyRoutes API to perform maps geolocation operations programmatically. The API provides 19 endpoints covering core functionality including authenticate client for access token, list routes, get route by id.

Example prompt: Call POST /authenticate to authenticate client for access token

### Automated Authenticate Management

Automate authenticate operations by combining multiple EasyRoutes API endpoints. Agents can list routes and then get route by id in a single workflow.

Example prompt: Call GET /routes to list routes, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call EasyRoutes 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 'authenticate client for access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/authenticate` | Authenticate client for access token |
| GET | `/routes` | List routes |
| GET | `/routes/{id}` | Get route by ID |
| GET | `/routes/{route_id}/stops/{stop_id}` | Get stop on route |
| POST | `/routes/{route_id}/stops` | Add stops to route |
| DELETE | `/routes/{route_id}/stops/{stop_ids}` | Delete stops from route |
| PUT | `/routes/{route_id}/stops/{stop_id}/items` | Update stop items |
| POST | `/routes/{id}/reoptimize` | Reoptimize route |

## Key resources

- **Authenticate** — Operations for authenticate
- **Drivers** — Operations for drivers
- **Routes** — Operations for routes
- **Stops** — Operations for stops
- **Webhooks** — Operations for webhooks

## Why Jentic

- **Setup:** Wiring the EasyRoutes API by hand means exchanging credentials for a bearer token, sending it on every request, and handling the request plumbing yourself. Through Jentic you install once, import the EasyRoutes API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** EasyRoutes puts the route and stop ids in the URL path (`/routes/{route_id}/stops/{stop_id}`), so a rule can pin your agent to one route: it can read and reoptimize that route and nothing else. You choose the operations it may call, so destructive ones like deleting stops are not included unless you add them.
- **Credential handling:** Your EasyRoutes 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 'list delivery routes' or 'reoptimize a route', and Jentic returns the matching EasyRoutes operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the EasyRoutes API use?

The EasyRoutes 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 authenticate client for access token with the EasyRoutes API?

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

### What are the rate limits for the EasyRoutes 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 authenticate client for access token through Jentic?

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

### How many endpoints does the EasyRoutes API have?

The EasyRoutes API exposes 19 endpoints covering authenticate, drivers, routes operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which EasyRoutes operations and credentials the agent may use. Because EasyRoutes puts the route and stop ids in the URL path, such as `/routes/{route_id}/stops/{stop_id}`, a rule can pin the agent to a single route so it only reads and reoptimizes that route. You pick the operations it may call, so destructive ones like deleting stops from a route stay out of reach unless you explicitly add them.