OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Ticket collections return structured support records.
Gorgias list tickets ↗
List tickets · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Cursor pagination traverses tickets with up to 100 per page.
Gorgias list tickets ↗
cursor; limit · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
customer_id, view_id, trashed and ticket IDs filter ticket results.
Gorgias list tickets ↗
Query Params · Checked 2026-10-16
Access cost barrier -
-
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges.
Gorgias list tickets ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Public applications require OAuth and the partner app review process.
Gorgias public OAuth app process ↗
App creation and approval · Checked 2026-10-16
Downstream permission -
-
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
Gorgias list tickets ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
POST creates tickets and the reviewed PUT route updates them.
Gorgias create ticket ↗
Create a ticket; Update a ticket separately reviewed · Checked 2026-10-16
Gorgias update ticket ↗
Update a ticket · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Public custom apps use provider-approved OAuth integrations; private keys are separate.
Gorgias public OAuth app process ↗
Public apps · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism -
-
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
The reviewed Gorgias scope does not establish refresh mechanism.
Gorgias list tickets ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Auth-dependent numeric budgets, quota headers and Retry-after are published.
Gorgias rate limits ↗
Request Limits; Rate-Limiting Headers · Checked 2026-10-16
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Repeat ticket collections permit scoped reconciliation; durable hard-delete identities unverified.
Gorgias list tickets ↗
List tickets; trashed · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Rerun the authorized ticket collection to rebuild its current scope; no retained historical replay established.
Gorgias list tickets ↗
List tickets · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Authorized ticket JSON can be received outside Gorgias.
Gorgias list tickets ↗
200 ticket list response · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
No retrieval window or export charge at cancellation is established by these technical sources.
Gorgias list tickets ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Portable ticket records; complete message history and attachments unresolved.
Gorgias list tickets ↗
List tickets response · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
The provider documents third-party app ticket creation.
Gorgias ticket creation behavior ↗
Introduction · Checked 2026-10-16
Rights to custom logic -
-
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Rights to native workflow artifacts and independent execution are not established.
Gorgias list tickets ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Private API requests use email and API key. Public OAuth apps follow partner registration and review; a private account key does not establish broad distribution rights.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
List tickets uses a cursor, a limit of 1-100 and filters such as customer_id, view_id and trashed. Internal undocumented resources are explicitly outside the supported API.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Private account email/API key | HTTP Basic | Customer | No | private integration email plus account api key; public distribution requires oauth | 2026-10-16 |
| Reviewed public OAuth app | OAuth 2.0 | Integration provider | Yes | partner portal registration, oauth and public app approval | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Fixed API fees and lowest-plan entitlement remain unknown. Limits differ by auth: OAuth has 80 calls per 20 seconds and keys 40; Enterprise uses a 10-second window.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
POST creates and PUT updates tickets. Ticket creation requires a message, and channel selection affects behavior; the API channel does not trigger auto-replies.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Current ticket enumeration can rebuild its declared selection, including the requested trashed state. Ordering by update time is not a durable delta checkpoint; retained replay remains unverified.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Repeat ticket collections permit scoped reconciliation; durable hard-delete identities unverified. | Gorgias list tickets ↗List tickets; trashedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Rerun the authorized ticket collection to rebuild its current scope; no retained historical replay established. | Gorgias list tickets ↗List ticketsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
The documented ticket JSON supports a record copy. Complete attachment payloads, message retention and historical configurations require separate verification.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Applications can implement external support workflows. Customer rights to native rule definitions and post-cancellation retrieval remain unknown (ticket APIs do not settle them).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Ticket collections return structured support records. | Gorgias list tickets ↗List ticketsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Cursor pagination traverses tickets with up to 100 per page. | Gorgias list tickets ↗cursor; limitChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. customer_id, view_id, trashed and ticket IDs filter ticket results. | Gorgias list tickets ↗Query ParamsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Public applications require OAuth and the partner app review process. | Gorgias public OAuth app process ↗App creation and approvalChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges. | Gorgias list tickets ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | Gorgias list tickets ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. POST creates tickets and the reviewed PUT route updates them. | Gorgias create ticket ↗Create a ticket; Update a ticket separately reviewedChecked 2026-10-16 Gorgias update ticket ↗Update a ticketChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Public custom apps use provider-approved OAuth integrations; private keys are separate. | Gorgias public OAuth app process ↗Public appsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | -Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. The reviewed Gorgias scope does not establish refresh mechanism. | Gorgias list tickets ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Auth-dependent numeric budgets, quota headers and Retry-after are published. | Gorgias rate limits ↗Request Limits; Rate-Limiting HeadersChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Authorized ticket JSON can be received outside Gorgias. | Gorgias list tickets ↗200 ticket list responseChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. No retrieval window or export charge at cancellation is established by these technical sources. | Gorgias list tickets ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. The provider documents third-party app ticket creation. | Gorgias ticket creation behavior ↗IntroductionChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Rights to native workflow artifacts and independent execution are not established. | Gorgias list tickets ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedGorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. Portable ticket records; complete message history and attachments unresolved. | Gorgias list tickets ↗List tickets responseChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest-plan API entitlement and fixed access fees
- Complete attachments/history and deletion recovery
- Native workflow rights and cancellation retrieval
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.