Base URL
Authentication
Authenticated endpoints require a Bearer token in theAuthorization header. Obtain a token by creating an API key in the dashboard (Developers → API Keys).
/v2/r/) do not require authentication — they are open for embedding in your front-end.
Request format
Send JSON bodies withContent-Type: application/json:
Response format
Successful responses return JSON. List endpoints use a paginated envelope:Pagination
All list endpoints support cursor-based pagination via query parameters:| Parameter | Default | Description |
|---|---|---|
limit | 20 | Results per page (max 100) |
offset | 0 | Number of results to skip |
Filtering and sorting
| Parameter | Description |
|---|---|
ordering | Field to sort by — prefix with - for descending (e.g. -created) |
search | Full-text search on supported fields |
Error responses
All errors return a JSON body with adetail field:
errors array:
HTTP status codes
| Code | Meaning |
|---|---|
200 | OK |
201 | Created |
204 | No content (successful delete) |
400 | Bad request — validation error or missing field |
401 | Unauthorized — missing or invalid API key |
403 | Forbidden — you don’t own this resource |
404 | Not found |
409 | Conflict — e.g. slug collision |
500 | Server error |
API key management
See API keys for how to create, rotate, and revoke keys.Next steps
Forms
List, create, update, and publish forms.
Sessions & responses
Read respondent sessions and their answers.