Ezus API

Name: Ezus API API
Brand: Ezus API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey, bearer37 EndpointsREST

For Agents

Manage travel-agency projects, clients, suppliers, products, packages, destinations, invoices and webhooks for Ezus across 37 endpoints under api.ezus.app.

Connect the Ezus API to your agent

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

Authenticate via /login and obtain a bearer token alongside the x-api-key header

Create, list and upsert travel projects through /projects, /project and /projects-upsert

Manage trip-day structure with /project-steps and /project-steps-upsert

List and upsert clients via /clients and /clients-upsert and individual records through /client

GET STARTED

Start building with Ezus API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Ezus API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Ezus API, keeping it validated and agent-ready. Ezus is a travel-agency management platform, and the API exposes the operations that travel professionals use to manage projects (trips), clients, suppliers, products, packages, destinations, invoices and webhook subscriptions. Authentication uses an x-api-key header alongside a bearer token issued by /login, supporting both delegated and machine-to-machine flows for agency back-office automation.

Use Cases

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

★ Project and Itinerary Management

Coordinate travel-agency operations by creating and updating projects, project steps, and traveller assignments through /projects, /project-steps and /project-travellers. Use the upsert variants to push changes from an upstream system without first checking for existence, and attach quoting or itinerary documents through /project-documents-create.

POST /projects-upsert with the trip metadata, then call /project-steps-upsert for each itinerary day and /project-travellers to add the traveller list.

Client and Supplier Sync

Keep Ezus aligned with the agency's CRM and supplier database by upserting through /clients-upsert and /suppliers-upsert. Useful for travel agencies whose source-of-truth for contacts lives in a separate CRM and who need Ezus projects to reference the latest client and supplier records without manual re-entry.

POST the CRM client record to /clients-upsert and the supplier record to /suppliers-upsert in a nightly synchronisation job.

Quote and Document Attachment

Generate and attach quoting documents to a project using /project-documents-create after a project has been upserted. The pattern keeps the document trail co-located with the project record and makes it easy for the agency team to retrieve the latest quote without leaving Ezus. Combine with the project-steps endpoints to ensure the quote reflects the agreed itinerary.

Call /project-documents-create with the rendered quote PDF and the project id to attach it to the matching Ezus project.

Agent-Driven Travel Operations via Jentic

An AI agent supporting a travel agency can use Jentic to discover and call the right Ezus operations rather than embedding the bespoke client. The x-api-key and bearer credentials live in the Jentic vault, so the agent can upsert clients, create projects, and attach documents while the secrets stay out of the prompt context.

Through Jentic, search 'create an Ezus travel project', load /projects-upsert, and execute it with the trip details supplied by the operations team.

Key Endpoints

37 endpoints — jentic publishes the only available openapi specification for ezus api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/login

Authenticate and receive a bearer token

POST

/projects-upsert

Upsert a travel project

GET

/projects

List travel projects

POST

/project-steps-upsert

Upsert itinerary steps for a project

POST

/clients-upsert

Upsert a client record

POST

/suppliers-upsert

Upsert a supplier record

POST

/project-documents-create

Attach a document to a project

POST

/project-travellers

Add travellers to a project

POST

/login

Authenticate and receive a bearer token

POST

/projects-upsert

Upsert a travel project

GET

/projects

List travel projects

POST

/project-steps-upsert

Upsert itinerary steps for a project

POST

/clients-upsert

Upsert a client record

Why though Jentic?

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

Credential isolation

The x-api-key value and the bearer token issued by /login are stored encrypted in the Jentic vault; the agent receives scoped credentials at execution time and never holds the raw API key.

Intent-based discovery

Agents search Jentic for intents like 'create an Ezus travel project' or 'upsert an Ezus client' and Jentic returns the matching /projects-upsert or /clients-upsert operation alongside its input schema.

Time to first call

Direct integration: 2-4 days to wire login, dual-credential handling, and the upsert patterns across projects, clients and suppliers. Through Jentic: under an hour to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

ezBookkeeping API

Self-hosted personal bookkeeping — useful for recording the agency's own expenses outside of Ezus invoices.

Use Ezus for client-facing projects and invoices, and ezBookkeeping for the agency's internal expense ledger.

Complementary

EZ Texting API

SMS messaging — pair with Ezus when project updates should trigger SMS notifications to travellers.

Trigger an EZ Texting send whenever a Ezus project step changes so travellers receive an itinerary update by SMS.

FAQs

Specific to using Ezus API API through Jentic.

Why is there no official OpenAPI spec for Ezus API?

Ezus does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Ezus API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Ezus API use?

The spec declares two security schemes: an apiKey scheme that requires the x-api-key header, and an HTTP bearer scheme used after authenticating via POST /login. Both credentials sit in the Jentic vault, so the agent never holds the long-lived API key directly.

Can I create a travel project with the Ezus API?

Yes. POST /projects-upsert with the project payload to create or update the project in one call, and follow up with /project-steps-upsert for itinerary days and /project-travellers for the traveller list.

How do I add a supplier to the Ezus directory?

Call POST /suppliers-upsert with the supplier record to create or update it, or use POST /supplier when you want to address a single supplier explicitly; GET /suppliers lists every supplier in the account.

How do I create a project through Jentic?

Run pip install jentic, search 'create an Ezus travel project', load POST /projects-upsert, then execute it with the trip metadata; Jentic supplies both the x-api-key and the bearer token from the vault.

What are the rate limits for the Ezus API?

The spec does not declare explicit rate limits, so honour any 429 responses with backoff, batch upsert calls where possible, and avoid running unbounded /projects pulls during peak booking hours.