Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Productivity / Ezus API
Ezus API logo

Ezus API

69
AI ReadinessAI-Aware (B+)69/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticProductivityTask ManagementapiKey, bearer37 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to log in to Ezus and obtain a bearer token, Create a new travel project for a client, List the active projects in my Ezus account, Upsert a client record from my CRM into Ezus

Not supported: Does not handle flight inventory, GDS bookings, or payment processing - use for travel-agency project, client, supplier and document management only.

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

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.

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

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fezus.io%2Fezus" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fezus.io%2Fezus" | 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.

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

Maintain a supplier directory through /suppliers, /supplier and /suppliers-upsert

Attach project documents and travellers through /project-documents and /project-travellers

Use Cases

Patterns agents use Ezus 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 your Jentic One instance, 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

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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

E

Ezus API

- AI-Aware (B+)
69/100
99
Foundational Compliance
63
Developer Experience & Jentic Compatibility
52
AI-Readiness & Agent Experience
94
Agent Usability
55
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

52

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4
61%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

97%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

55

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1
55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Ezus API by hand means presenting its x-api-key, exchanging it for a bearer token at /login, targeting the api.ezus.app host, and following its upsert-style routes yourself. Through Jentic you install once, import the Ezus API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Ezus carries project and client details in the request body of its upsert operations rather than a resource id in the path, so you limit the agent to the operations it needs, such as listing projects or upserting a client. You choose those operations, so supplier or document-creation calls are not included unless you add them.

Credential isolation

Your Ezus x-api-key and the bearer token issued by /login are stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw API key never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an Ezus travel project' or 'upsert an Ezus client', and Jentic returns the matching /projects-upsert or /clients-upsert operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance, 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.

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

Yes. Because you self-host Jentic One, your own rules decide which Ezus operations and credentials the agent may use, so you can grant only what a task needs, such as GET /projects to list trips or POST /clients-upsert to sync a client. Ezus carries project and client details in the request body of its upsert routes rather than a resource id in the path, so scoping happens at the operation level: supplier calls like POST /suppliers-upsert and document routes like POST /project-documents-create stay off limits unless you add them. The x-api-key and the bearer token from /login are injected at execution time under those same rules.

GET STARTED

Start building with Ezus API

Explore with Jentic One
View OpenAPI Document