Feature guide
Gorgias API in 2026
Prices checked November 15, 2026
This guide is for buyers and technical evaluators who need the official Gorgias REST API — what it is, how it authenticates, what rate limits are published, and where official pages disagree. It is based on the developer portal and the public pricing page, fetched on November 15, 2026. It is not an SDK, and we have not built an app against the API. Desk for Stores is not affiliated with Gorgias. Confirm live docs before you ship anything.
What official developer docs say the API is
The official Introduction describes a REST API with “predictable resource-oriented URLs,” JSON request and response bodies, and standard HTTP codes, authentication, and verbs. The reference lives at your account host: official examples use https://your-customer-account.gorgias.com/api/....
Official docs also draw a hard line: “Resources, resources' attributes, and resources' operations not documented in this documentation should not be used and should be considered as non-existing. They are reserved for internal use and can be changed or removed at any time without prior notice.” We are not documenting unofficial endpoints.
Authentication supports two methods:
- Private app → API key. Official Access Tokens (API Keys) say this method is only for private apps. Public apps must use OAuth2. Each key is tied to a specific user and “has the same permissions as the user that holds them.” A key for an Observer can only do what an Observer can do. Admins generate or revoke a key under Settings → REST API. Requests use HTTP Basic Authentication: a base64-encoded
USERNAME:API_KEYpair. - Public app → OAuth2. Official docs say OAuth2 is mandatory for public apps to be approved. OAuth2 Bearer Token docs say access tokens expire; apps that need ongoing access should request the
offlinescope and use a refresh token.
Official create integrations and widgets docs describe custom HTTP integrations (API calls from Gorgias to another service, often triggered by ticket events) and widgets that can show that data on the ticket. They distinguish those custom HTTP integrations from native integrations maintained by Gorgias. There are also official guides for receiving and responding to tickets from a third-party channel, and for syncing Gorgias data with a database. Those are implementation guides, not a second API product.
We looked for a dedicated public “merge tickets” endpoint, including developers.gorgias.com/reference/merge-tickets, which returned 404 in this fetch. What official docs do publish is a changelog note dated from August 8, 2023: requests to /api/tickets/{id}/* return HTTP 301 and redirect to the remaining ticket if the ticket has been merged (previously those requests 404’d). There is a separate documented merge two customers operation; that is not a ticket-merge endpoint. Official billing docs describe how merged tickets are billed in the helpdesk, which is a different topic.
Rate limits, and official figures that do not fully agree
Official Rate Limits use a leaky-bucket model. Published request limits:
- OAuth2 apps: 80 requests in a 20-second window
- API key integrations: 40 requests in a 20-second window
- Enterprise accounts: “folow the same request limits, but have a smaller 10-second window” (official wording, including the typo)
Exceeding the limit returns HTTP 429. Responses include Retry-after and X-Gorgias-Account-Api-Call-Limit.
On the official pricing page in this fetch, the compare table had a row titled “API rate limit” at 2 req/s for Starter, Basic, Pro, and Advanced. A separate “custom plan” / Enterprise-style block on the same page said “Unlimited Help Centers, API at 4 requests per second.”
Those public figures can be read in more than one way, and we do not average them:
- 40 API-key requests / 20 seconds is 2 requests per second, which matches the compare-table row for the four listed helpdesk plans.
- 80 OAuth2 requests / 20 seconds is 4 requests per second, which matches the custom-plan blurb — but that blurb is not the compare-table row for Advanced.
- Enterprise’s official 10-second window, if the same 40 or 80 count applies, would be 4 or 8 requests per second, which is not spelled out as a single “4 req/s” line in the developer article.
If API throughput is a buying criterion, confirm the limit that will apply to your plan and your auth method in writing. Do not assume the compare table, the custom-plan blurb, and the developer article are interchangeable.
Price: no separate API list price
We did not find a public add-on price for “Gorgias API.” The REST API is documented as part of the product (Settings → REST API). Helpdesk list prices on this fetch remain Starter $10 / month, Basic $60 / $50 annually, Pro $360 / $300, Advanced $900 / $750, with the usual seat and AI-Agent conflicts on that page — see Gorgias pricing. We are not inventing an API SKU.
The Gorgias MCP is a different official surface: an MCP server for AI assistants, not a replacement for the REST API.
Related guides: Gorgias MCP, Gorgias integrations, Gorgias automation (macro HTTP hooks cannot be used in rules, per official macro docs), and Gorgias pricing. Official docs also describe a partner Zapier path that uses HTTP integrations and the REST API; that is summarized in Gorgias Zapier integration.
If you want to look at Gorgias after this guide, you can use our affiliate link. We may earn a commission. You pay the same published price. See Gorgias (affiliate link).
Sources and method
Checked November 15, 2026:
- API introduction
- Authentication, Access tokens, and OAuth2 bearer tokens
- Rate limits
- Create integrations and widgets
- 301 redirect when fetching a merged ticket
- Gorgias pricing
No invented API list price. Undocumented endpoints were not used as sources.
Frequently asked questions
Is there a Gorgias API price?
Not on the official pages we fetched. The REST API is documented in the developer portal and in helpdesk settings. Confirm any plan-specific API limits or Enterprise terms with Gorgias.
What is the official rate limit?
Developer docs publish 80 requests / 20 seconds for OAuth2 apps and 40 / 20 seconds for API keys, with a shorter 10-second window for Enterprise. The public pricing compare table listed 2 req/s on Starter through Advanced, and a custom-plan blurb listed 4 req/s. Those official figures are not identical; we report them all.
Is there a merge-tickets API endpoint?
The specific reference URLs we tried for a merge-tickets operation returned 404. Official developer docs do describe a 301 redirect when you fetch a ticket that has already been merged, and official billing docs describe how merges are billed. Do not assume an undocumented merge endpoint exists.
Considering Gorgias for a Shopify or ecommerce store? You can start a trial on Gorgias through our affiliate link. We may earn a commission. You pay the same published price.
See Gorgias (affiliate link)Affiliate link: we may earn a commission if you buy through this link. You pay the same published price.