Gorgias APIs for AI Agents
CRMCustomer SupportJentic-Generated DocumentsBasic authAgent Ready
For Agents
APIs2 in catalogue
Endpoints128 indexed
AuthBasic auth — 1 credential for all 2 APIs
ProvenanceJentic-generated documents
An agent can read, create, and reply to Gorgias support tickets, look up and enrich customer records, apply macros, manage tags and automation rules, populate custom fields, and pull satisfaction and statistics data across the helpdesk. It can choose between the lighter core API for everyday ticket and customer work and the full REST surface for reporting, rules, surveys, and custom data.
Gorgias is a helpdesk purpose-built for e-commerce merchants, tying support conversations to customer and order context rather than serving as a general-purpose ticketing tool. Both of its published specs share one Basic auth model and helpdesk data model, differing only in how much of the surface they expose.
Gorgias API Catalog
2 APIs across 1 product group. All share one credential.
CRM2
Gorgias REST APIDrive deep Gorgias helpdesk automation across tickets, custom fields, rules, satisfaction surveys, voice, statistics, and integrations.~111 endpointsGorgias APIManage Gorgias helpdesk tickets, customers, messages, macros, and tags so agents can read and reply to e-commerce support conversations.~17 endpoints
Which Gorgias API should I use?
| I want to... | Use |
|---|---|
| Read, create, and reply to support tickets and look up customers | Gorgias API |
| Reach automation rules, custom fields, satisfaction surveys, voice, and statistics | Gorgias REST API |
| Define and populate custom fields on tickets or customers | Gorgias REST API |
Install Jentic One Beta
Connect the Gorgias APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gorgias APIs, 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%2Fgorgias.com" | sh2
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%2Fgorgias.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
Once connected, ask your agent something like: “automate the gorgias helpdesk: reply to tickets and pull satisfaction data”.
What AI Agents Can Do with Gorgias
Each workflow spans multiple Gorgias APIs. Jentic routes each operation to the right API automatically.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring either Gorgias API by hand means setting up Basic auth with the merchant email and API key, resolving the {domain}.gorgias.com host per account, and matching calls across the resource surface. Through Jentic you install Jentic One once, add the Gorgias APIs from the Jentic directory, store the email and key once, and your agent calls both.
Permission scoping
Gorgias puts resource ids in the URL path, so your own rules can pin an agent to one ticket or one customer and to a chosen set of operations. Reporting, rule changes, or custom field writes are not available to the agent unless you add those operations.
Credential isolation
Your Gorgias merchant email and API key are stored once, encrypted, by your own Jentic One instance and injected at execution time as the Basic auth header. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search the Jentic directory by intent such as 'reply to a support ticket' or 'list satisfaction surveys', and Jentic returns the matching Gorgias operation from the right API with its input schema, so the agent calls the correct endpoint without browsing the reference docs.
FAQs
Specific to using Gorgias APIs through Jentic.
What is the difference between the two Gorgias APIs?
The Gorgias API is a lighter 17-endpoint surface covering the most-used helpdesk objects: tickets, messages, customers, macros, tags, teams, and integrations. The Gorgias REST API is the comprehensive 111-endpoint surface that also reaches automation rules, custom fields, satisfaction surveys, voice, statistics, and account settings. Use the smaller one for everyday ticket and customer work and the larger one when you need reporting, rules, or custom data.
Do both APIs use the same authentication?
Yes. Both use HTTP Basic with the merchant email as username and a Gorgias account API key as password, scoped to the merchant subdomain. A single credential pair works across both APIs, so you store it once and reuse it.
Which API should an agent use to reply to a ticket?
Either exposes ticket messaging, but the core Gorgias API is the simpler choice for posting a public or internal reply to a ticket thread. Reach for the comprehensive REST API when the same workflow also needs custom fields, automation rules, or satisfaction data.
Why does Jentic publish these Gorgias specs?
Gorgias does not publish an OpenAPI specification. Jentic generates and maintains both specs, validated against the live API and kept up to date, so AI agents and developers can call Gorgias through structured tooling instead of hand-writing requests.
What can an agent not do with these APIs?
These are helpdesk APIs. They do not manage orders, inventory, fulfillment, payments, or marketing email. Pair Gorgias with an e-commerce platform or CRM when a workflow needs order context or customer data beyond what the helpdesk stores.
Can I run e-commerce support reporting across both APIs?
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.