How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Endgame Threads API

The public Threads API from Endgame — 5 operations (create, get, list, rename, delete) rooted at /api/v1 on https://app.endgame.io, authenticated with a Bearer eak_ API key or a WorkOS M2M access token. Threads are the conversational unit behind Endgame Chat: POST a natural-language prompt, then poll the thread until the assistant's asynchronous response reaches status.state idle or error.

Endgame Threads API is one of 3 APIs that Endgame publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Threads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 10 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://app.endgame.io.

10 operations 4 paths 11 schemas 2 DELETE4 GET2 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://app.endgame.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Endgame Threads API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — One of: an Endgame API key prefixed eak (created from Settings → API Keys with a Personal or Org-wide scope), or a WorkOS access token from an Endgame-provisio…

Paths & Operations 10

Across 4 paths, the API surfaces 10 operations — 2 DELETE, 4 GET, 2 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Threads 10
POST
/api/v1/threads
Create a thread
createThread body → 200400403
GET
/api/v1/threads
List threads
listThreads 3 params → 200400
GET
/api/v1/threads/{id}
Get a thread
getThread 1 param → 200
PATCH
/api/v1/threads/{id}
Update a thread
updateThread 1 param body → 200400403
DELETE
/api/v1/threads/{id}
Delete a thread
deleteThread 1 param → 200403
POST
/threads
Create a thread
threads.create body → 200
GET
/threads
List threads
threads.list 3 params → 200
GET
/threads/{id}
Get a thread
threads.get 1 param → 200
PATCH
/threads/{id}
Update thread
threads.update 1 param body → 200
DELETE
/threads/{id}
Delete thread
threads.delete 1 param → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are ThreadMessage (11 properties), Thread (9 properties), CreateThreadRequest (4 properties), ThreadStatus (4 properties). Each schema is shown below with its type and property counts.

UpdateThreadRequest
object
Only title is writable. Unknown fields are rejected with INVALIDPARAMS.
1 property 1 required
GetThreadResponse
object
3 properties 3 required
UpdateThreadResponse
object
1 property 1 required
ListThreadsResponse
object
3 properties 3 required
CreateThreadResponse
object
3 properties 1 required
ThreadStatus
object
Derived run status based on the latest assistant message.
4 properties 4 required
CreateThreadRequest
object
Parameters for creating a thread. prompt is required; title auto-generates from it if omitted.
4 properties 1 required
ThreadMessage
object
A single message on a thread.
11 properties 11 required
Thread
object
Public representation of a thread.
9 properties 9 required
DeleteThreadResponse
object
2 properties 2 required
Error
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

end-game-threads-api-openapi.yml Raw ↑

Other APIs Endgame publishes across the network.

Endgame Internal API
Endgame Protected Static API
Where this information came from

This is an independent, third-party profile of Endgame Threads API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.