Skip to main content
Open Beta: The Endgame REST API is expected to continue evolving, and its endpoints may change.
The Endgame REST API lets you create and manage threads — the same conversational units that power Endgame Chat — from any HTTP client. Start a thread with a prompt, poll it for the assistant’s response, rename it, list an organization’s threads, or delete one. Use it to embed Endgame directly into your own applications, agents, or back-office automations.

Base URL

All endpoints in this reference are rooted at /api/v1.

The 30-second tour

Authenticate with a user-scoped API key and POST a prompt to /threads. The prompt is required — it’s persisted as the first user message and triggers an assistant response that generates asynchronously. You get back the thread plus the IDs of both messages:
Fetch the thread to watch the assistant’s response fill in:
The response includes the thread, every message on it, and a derived status object (idle, in_progress, or error) you can poll until the assistant finishes.

What’s next

Authentication

How to create and use API keys and M2M credentials.

Endpoints

Reference for the five thread endpoints, with examples, errors, rate limits, and pagination.