ThreadPage

ThreadPage Events API

The Events API from ThreadPage — 8 operation(s) for events.

GitHub OpenAPI

Operations 10

GET /api/integrations/v1/events/sample Up to three recent events in the exact live form #
GET /api/integrations/v1/subscriptions List this connection's event subscriptions #
POST /api/integrations/v1/subscriptions Subscribe a webhook or a pull feed to events #
GET /api/integrations/v1/subscriptions/{subscription_id} Get one subscription #
DELETE /api/integrations/v1/subscriptions/{subscription_id} Delete a subscription #
GET /api/integrations/v1/subscriptions/{subscription_id}/deliveries The latest delivery attempts of a webhook subscription #
POST /api/integrations/v1/subscriptions/{subscription_id}/deliveries/{delivery_id}/retry Send the event of a failed delivery again #
GET /api/integrations/v1/subscriptions/{subscription_id}/events Read a pull feed #
POST /api/integrations/v1/subscriptions/{subscription_id}/pause Pause deliveries #
POST /api/integrations/v1/subscriptions/{subscription_id}/resume Resume deliveries #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/thread-page/openapi/thread-page-events-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/thread-page/json-schema/thread-page-subscription-schema.json
📊
JSONSchema
https://artifacts.apis.io/thread-page/json-schema/thread-page-delivery-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/thread-page:thread-page-events-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

thread-page-events-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: ThreadPage Integration Events API
  version: 1.1.0
  description: 'Read, add, edit and organize notes in ThreadPage from your own scripts, servers and workflows.

    Every page of the developer reference has a Markdown twin; all of them in one file:

    https://thread.page/llms-full.txt. Start at https://thread.page/help/connections/custom.md.


    - **Authentication.** A custom connection''s token as `Authorization: Bearer tp_…`, from a server

    or a script: the API sends no CORS headers. Its level (Edit and organize, Read and add, Read

    only, Add only or Add to Inbox) offers the same here as through MCP; `x-threadpage-levels` and

    `x-threadpage-mcp-tool` on each operation say who may call it. A 401 is `invalid_token` (ask

    the owner for a new token) or `token_expired` (the owner renews the same token). The same

    token connects an MCP client to `/mcp` on every level but Edit and organize, which MCP takes

    only through OAuth (403 `oauth_required`). https://thread.page/help/connections/api.md

    - **Writes.** Every write takes an `Operation-Id` header: one UUID per logical write, the same

    on every retry. After a lost response, read `GET /operations/{operation_id}`. A content edit

    sends the `content_revision` and `context_receipt` of the read it is based on; 409

    `stale_block` or `reread_required` means read again. A shared thread or folder

    (`shared: true`) takes writes only where the owner allowed this connection (409

    `shared_place_write`). Nothing is ever deleted permanently.

    - **Errors** share one shape: `code`, `message`, `retryable`, `diagnostic_id` (also the

    `X-Request-ID` header) and `details`. A 429 or 503 carries `Retry-After`. MCP tools answer

    `{"status": "rejected", "code", "message", "details"}` in the tool result.

    `x-threadpage-errors` on each operation lists the codes it answers, and at the top level every

    code. https://thread.page/help/connections/errors.md

    - **Lists** return `next_cursor`; pass it back as `cursor` within an hour.

    - **Times** are UTC in RFC 3339 and end in `Z`.

    - **Events** (`webhooks` below) reach a signed webhook or a pull feed; a connection never hears

    its own writes. https://thread.page/help/connections/events.md

    - **Endpoint URLs** (`POST /in/{capability}`) turn a service''s JSON into notes in one thread.

    https://thread.page/help/connections/endpoints.md

    - **Requests**: claim the notes the owner addresses to this connection (its `@name`) and answer

    with a note; a request keeps the name it was sent to, so tell them apart by id.

    https://thread.page/help/connections/requests.md'
servers:
- url: https://thread.page
tags:


# --- truncated at 32 KB (101 KB total) ---
# Full source: https://artifacts.apis.io/thread-page/openapi/thread-page-events-api-openapi.yml