Introduction

Overview

The There There API lets you manage tickets, contacts, team members, workflows, and more from outside the app. Anything your team can do in the UI, you can automate from a script, a background job, or a third-party integration.

The base URL for all endpoints is https://there-there.app/api. All requests and responses are JSON, and every request must be authenticated with a bearer token. See Authentication for details on tokens, workspace headers, pagination, error responses, and rate limits.

Hello world

The fastest way to verify your setup is to fetch your own profile. This call requires nothing but a valid token, and it tells you which workspace the token resolves to.

curl https://there-there.app/api/me \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/json"

A successful response returns your user and the current workspace. If you get a 401, your token is missing or invalid. If you get a 400 complaining about a workspace, your token has access to multiple workspaces and you need to add an X-Workspace-Id header.

Interactive reference

Every endpoint is documented in an OpenAPI 3.1 spec. You can browse it interactively with example requests and response schemas, or download openapi.yaml to import it into Postman, Insomnia, or your own code generator.

What you can manage

The API is grouped by resource. Each section in the sidebar covers a single resource with the endpoints you need to list, create, update, and delete it.

• Tickets — the core object. Create inbound tickets, update status, change assignee, and attach tags.
• Messages — send public replies or internal notes on a ticket.
• Contacts — manage the people your tickets are from.
• Channels — the mailboxes and widgets tickets arrive on.
• Tags — categorize tickets across your workspace.
• Teams and Members — manage who can access what.
• Quick Replies — reusable reply templates.
• Saved Views — named ticket filters your team shares.
• Workflows — automation rules that run when tickets arrive.
• Brains — knowledge sources the AI assistant draws from.

Conventions you will see throughout

All endpoints share the same conventions, so you only need to learn them once.

• Authentication and workspace scoping — bearer token in Authorization, optional X-Workspace-Id header. See Authentication.
• Response shape — single resources are wrapped in { "data": {...} }. Collections add meta and links for pagination.
• Filtering and sorting — pass filters as filter[field]=value and sort with sort=field or sort=-field.
• Errors — validation errors return 422 with a per-field errors object. Other failures use the standard HTTP status codes listed under Authentication.
• Rate limits — 60 requests per minute per token. A 429 response includes a Retry-After header.

Next steps

Start with Authentication to generate a token and verify your setup, then jump into the resource you are working with. If you prefer exploring interactively, the API reference shows every endpoint and schema in one place.