REST API - Usertick

The REST API gives your own code access to your Usertick data. With it, your code can list and filter responses, change their status, type, urgency and assignees, add notes, read surveys and metrics, pause and resume surveys, erase a respondent’s data, and subscribe a URL to new responses, status changes, urgent feedback, theme spikes or a workflow’s Zapier step. API keys, which your own code uses to call the API, are available on the Pro plan and above. Apps such as Zapier call the API on the Starter plan and above.

Base URL: https://app.usertick.com/api/public/v1

Make a first request

After you create an API key under Settings → Developers → API keys, call GET /me to check that the key works:

curl "https://app.usertick.com/api/public/v1/me" \
  -H "Authorization: Bearer utk_live_your_key_here"

{
  "organization": { "id": "3c9e4e1a-5b7d-4f20-9a61-0c2d8e4f6a10", "name": "Usertick" },
  "user": null,
  "credential": {
    "kind": "api_key",
    "id": "0d6f1c2a-3b4c-4d5e-8f60-718293a4b5c6",
    "name": "Ops script",
    "scopes": ["responses:read", "responses:write"]
  },
  "rateLimits": { "perMinute": 120, "organizationPerMinute": 600 }
}

The same key then lists the newest responses:

curl "https://app.usertick.com/api/public/v1/responses?limit=10" \
  -H "Authorization: Bearer utk_live_your_key_here"

How the API behaves

Plain JSON. A successful call returns the resource itself, or a list as { "data": [...], "nextCursor": "..." }, without a { success, data } wrapper. See Pagination.
Times are RFC 3339 in UTC with milliseconds, such as 2026-09-30T10:00:00.000Z. A time in a query without an offset is read as UTC. A to given as a date alone, such as to=2026-10-14, includes that whole UTC day.
Every key is present. An empty value is null instead of a missing key. New fields can appear over time, so your code should ignore the ones it doesn’t know.
Errors carry a stable code, plus an errors list for invalid fields. See Errors.
Every HTTP response has an X-Request-Id header. Include it when you contact support.
Rate limits are 120 requests per minute per credential and 600 per organization. See Rate limits.
POST requests take an Idempotency-Key header, so a retried request doesn’t run twice. See Idempotency.
Retention. The API reads responses only as far back as your plan keeps them, the same as the dashboard.

Guides

Authentication

API keys, scopes, expiry, rotation and usage.

The Response resource

One shape for every response the API returns and every webhook delivers.

Pagination

Cursors, page sizes and syncing with updatedSince.

Errors

The error envelope and every code.

Erase personal data

Delete one response or everything one person sent.

Metrics

Counts, NPS, CSAT, CES, series and breakdowns.

The API reference

Every endpoint has its own page under API reference. Each page lists the scopes the endpoint needs, its parameters, its HTTP responses and its error codes. Try it on a page sends a real request with the key you paste in.

Area	Endpoints
Account	Get the current credential
Surveys	List, get, pause and resume surveys, list sites
Responses	List, list recent, get and update responses, the analysis tree, members, files
Notes	List, add, edit and delete notes
Erasure	Erase a response, erase a respondent, follow the job
Metrics	Summary, time series, breakdown
Webhooks	List, subscribe and unsubscribe, deliveries, resend, workflow Zapier steps

Other ways to reach your data

Webhooks send each new or analyzed response, and the AI events, to your URL as they happen. See Webhooks.
The MCP server lets AI assistants such as Claude, ChatGPT, Cursor and Claude Code work with your surveys, responses, metrics and webhooks. Each person signs in and chooses what the assistant may do. See MCP server.
Zapier connects Usertick to other apps without code. See Zapier.

​Make a first request

​How the API behaves

​Guides