EasyRoutes API

Name: EasyRoutes API API
Brand: EasyRoutes API
Availability: InStock

✓ Official Vendor SpecMaps GeolocationGeocodingbearer19 EndpointsREST

For Agents

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

Connect the EasyRoutes API to your agent

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

Authenticate client for access token

List routes

Get route by ID

Add stops to route

Delete stops from route

GET STARTED

Start building with EasyRoutes API API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ 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.

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.

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.

Search Jentic for 'authenticate client for access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

19 endpoints — route planning and delivery management api for shopify merchants.

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

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

Why though Jentic?

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

Credential isolation

EasyRoutes 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., 'authenticate client for access token') and Jentic returns the matching EasyRoutes API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

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

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Here

Alternative maps geolocation API

Choose Here when you need a different approach to maps geolocation operations

Alternative

Tomtom

Alternative maps geolocation API

Choose Tomtom when you need a different approach to maps geolocation operations

Complementary

Googleapis

Complementary maps geolocation API

Choose Googleapis when you need a complementary approach to maps geolocation operations

FAQs

Specific to using EasyRoutes API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.