Retrieve and analyze Gorgias CSAT (satisfaction survey) data via the Gorgias REST API
domain: developers.gorgias.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with HTTP Basic Auth against https://{your-domain}.gorgias.com/api/, using your account email as the username and a REST API key as the password.
Call GET /api/satisfaction-surveys to list CSAT surveys, paginated via a cursor query parameter (not page numbers), with limit (1-100, default 30) and order_by=created_datetime:asc|desc (default desc).
Filter to a specific ticket's survey by passing the ticket_id query parameter on the list call.
Retrieve a single survey's full detail (score, comment, timestamps) via the Get a survey endpoint using its numeric id.
Read the SatisfactionSurvey object fields — score (1-5 or null), body_text (customer comment), sent_datetime, scored_datetime, should_send_datetime, and the free-form meta object — to build CSAT reporting.
Join survey records back to tickets/customers using each survey's ticket_id and customer_id fields.
Known gotchas
Pagination is cursor-based, not offset/page-based — you must pass the cursor value returned by the previous response to page forward.
score, body_text, and scored_datetime remain null until the customer actually responds to a sent survey; a null score is not the same as a 0/negative score.
Gorgias currently allows only one satisfaction survey per ticket, so you cannot list or create multiple surveys for the same ticket.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?