Platform · API and webhooks

Run Tore from your code.Hear about every event.

A read and write API, keys scoped to exactly what they need, and signed webhooks with a log of every delivery. Your inbox and investigations also work inside Claude and Cursor.

Join the waitlist See what you can build

Tore opens soon. Join the waitlist and we'll email you the day you can start.

app.tore.ai/beacon-data/developers

Illustration

Illustration: a developer creates a conversation through the Tore API with a test-mode key. Tore answers 201 Created, then fires webhooks to Beacon Data's endpoint. One delivery gets a 503, Tore retries it and the second attempt succeeds. Every delivery is signed and the signature verifies.

Requestlivetest

$ curl -X POST https://api.tore.ai/v1/conversations \    -H "Authorization: Bearer tore_test_••••4f2a" \    -d '{      "product": "beacon-app",      "from": "maya@northwind.io",      "subject": "Export stops at 1,000 rows",      "tags": ["export"]    }'

Response142 ms

201 Createdscope: support:write

{
  "id": "cnv_8KQ2",
  "status": "open",
  "product": "beacon-app",
  "mode": "test"
}

2 events fired

Webhook deliverieshooks.beacondata.io

conversation.createdattempt 1 · 88 ms200

conversation.taggedattempt 1 · retrying503

conversation.taggedattempt 2 · 104 ms200

Tore-Signature: sha256=7c1e…verified

Tore fits into your systems,not the other way round.

Anything you can do in Tore you can do from code, and anything that happens in Tore can tell your systems straight away.

Automate it from your code

Create, update and read conversations, tickets and feedback from your own scripts and services.

copying data between tools by hand

Keys that can't do too much

Each key gets only the scopes it needs, in live or test mode, and rotates without an outage.

one admin key shared in a chat message

Events you can trust arrive

Webhooks are signed, retried when your endpoint is down, and logged attempt by attempt.

polling every minute to see what changed

Tore inside your AI tools

Ask Claude or Cursor about a ticket or an investigation, and it reads it straight from Tore.

pasting a ticket into a chat window

Built for the engineerwho has to maintain it.

API keys

Scoped keys, with a test mode.

Give each integration only what it needs. Build against test mode, then switch to a live key when you are ready. Rotating a key keeps the old one working for a while, so nothing breaks in between.

Read and write scopes for support, knowledge and feedback
Live and test modes, and keys pinned to one product
Rotation with an overlap window, so you never need an outage
A rotated key can never gain a wider scope than it had

settings · API keys

Example data

Help center synclivetore_live_••••a91c · beacon-app

knowledge:readknowledge:writesupport:write

Staging smoke teststesttore_test_••••4f2a · beacon-app

support:readsupport:write

Rotating Help center sync. Both keys work until the overlap ends.

new key issuedold key retires in 18 h

Stored as a hash. Only the last four characters are shown.

Webhooks

Signed, retried and logged.

Tore pushes events to your endpoint the moment they happen. Each one is signed so you know it came from Tore, retried if your server is down, and recorded attempt by attempt so you can see exactly what was sent.

Every delivery signed with HMAC-SHA256
Retried three times when your endpoint fails
A delivery log with each attempt, status and timing
Redirects are not followed and private addresses are refused

webhooks · delivery log

Example data

TimeEventTryStatus

10:02:11investigation.completed1200

10:04:37ticket.created1timeout

10:05:07ticket.created2502

10:07:07ticket.created3200

10:09:52conversation.handed_over1200

Tore-Signature: t=1761735712,sha256=7c1e9a…f02b
Tore-Event: ticket.created · Tore-Delivery: dlv_3HV9

Endpoint http://10.0.0.4/hook refused: private address

MCP server

Your inbox, inside Claude and Cursor.

Connect Tore's MCP server and the AI tools your team already uses can read conversations, tickets and investigations. Ask about a bug in your editor and get the root cause Tore already found.

Works with Claude, Cursor and other tools that speak MCP
Uses the same scoped keys as the API
Investigations, tickets and conversations, one question away

Cursor · chat

Illustration

Connected: tore (MCP) · support:read

What did Tore find on the export bug Priya reported?

tore.get_investigation · TCK-482

Root cause found by Tore:

paginate.ts:57stops when it has 1,000 rows instead of when a page comes back short
sincestarted with PR #471, two days ago
statusfix proposed, waiting for your approval

API docs

Docs generated from the API itself.

The reference is built from the API, not written next to it, so it can't drift out of date. Every endpoint, parameter and scope is listed, with a test-mode request you can try.

Generated from the API, so it always matches
Shows the scope each endpoint needs
Versioned, so an upgrade never surprises you

API reference

Illustration

SupportConversationsTicketsTagsKnowledgeArticlesFeedbackRequestsEventsWebhooks

PATCH/v1/tickets/{id}

Update a ticket's status, owner or tags. Needs support:write.

statusopen, pending or closedoptional

assignee_ida teammate in this productoptional

tagsreplaces the ticket's tagsoptional

Generated from API v1 · matches the running service

6key scopes: read or write for support, knowledge and feedback

2modes per key, live and test

3retries for a webhook your endpoint missed

1signature on every delivery, so you know it came from Tore

Keep exploring.

Make a test key.Send your first request.

Start a trial, switch to test mode and send your first request. Nothing reaches a real customer until you go live.