Back to Help Center
Developers

Developer API

An overview of Thicket’s REST API and where to find the reference.

Thicket API Overview

Thicket exposes a versioned REST API at /api/v1. It's the same surface the web app is built on, so anything you can do in the product has a corresponding API route — projects, to-dos, messages, documents, calendar events, cards, chats, people, search, and more.

The Basics

  • Base path — /api/v1. Routes that belong to an organization include its slug: /api/v1/{org-slug}/...
  • Format — JSON with snake_case keys
  • Errors — returned as { "error": { "code": "...", "message": "..." } } with conventional HTTP status codes
  • Tenancy — every request is scoped to your organization; you can never read another organization's data

Authentication

The API currently authenticates with the same session used by the web app — sign in through the auth endpoints and the session cookie carries your identity. Personal access tokens are a planned addition, and the API is designed so they'll slot in without any route changes.

Full Reference

The endpoint-by-endpoint reference lives at thickethq.com/developers/api, covering authentication, projects, content, people, calendar, search, and billing routes.

Was this article helpful?