Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Endgame Threads API

The Threads API from Endgame — 2 operation(s) for threads.

Endgame Threads API is published by Endgame 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, and authentication docs.

This API exposes 5 operations across 2 paths, and defines 11 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

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

5 operations 2 paths 11 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.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 5

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

Threads 5
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

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), ThreadStatus (4 properties), CreateThreadRequest (4 properties). Each schema is shown below with its type and property counts.

DeleteThreadResponse
object
2 properties 2 required
ThreadStatus
object
Derived run status based on the latest assistant message.
4 properties 4 required
UpdateThreadResponse
object
1 property 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
GetThreadResponse
object
3 properties 3 required
UpdateThreadRequest
object
Only title is writable. Unknown fields are rejected with INVALIDPARAMS.
1 property 1 required
CreateThreadRequest
object
Parameters for creating a thread. prompt is required; title auto-generates from it if omitted.
4 properties 1 required
CreateThreadResponse
object
3 properties 1 required
ListThreadsResponse
object
3 properties 3 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 ↑