For developers

Build SayIt into your own app

The same rehearsal engine behind the web app and Telegram bot, available over a simple REST API for developers who want it inside their own product. Keys are created in Settings and work today.

Create a key

Generate an API key from Settings. It's billed against your own SayIt credit balance — no separate billing to set up.

Create a conversation

POST a name and optional context to /v1/conversations. Get back a sessionId to run actions against.

Run an action

POST text or a recording URL to /v1/run with an actionId. Get back the diagnosis, script, scorecard, or audio — same as the web app.

Try it

Two calls to your first result

curl

curl https://say-it.online/api/v1/conversations \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"name": "Ask my landlord for the deposit"}'

curl https://say-it.online/api/v1/run \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "sessionId": "<sessionId from above>",
    "actionId": "review",
    "text": "I keep chickening out of asking for the deposit back."
  }'

Reference

Endpoints

Every request needs Authorization: Bearer <your key>.

POST/api/v1/conversations

Create a conversation to run actions against. The context answers (situation, who, ask, fear, tone, timing) are given to every action. Returns { id, sessionId }.

{ name, context? }

GET/api/v1/actions

List available actions for the active skin, with id, label, inputs, and credit cost.

POST/api/v1/run

Run one action. Debits credits on success, releases the hold on failure — same reserve→settle rule as the web app.

{ sessionId, actionId, text?, mediaUrl? }

GET/api/v1/balance

Current credit balance for the account behind the API key.

Same credits, no new billing

Every API call spends from the credit balance you already top up in the dashboard. One account, one balance, both surfaces.

Named, revocable keys

Name each key, see when it was last used, and revoke it instantly from Settings if it ever leaks. Every key has full access to its account, so keep keys secret.

The same engine

The API runs the exact pipeline the web app and Telegram bot use. Up to 300 requests per hour per account.

Same credits. Same engine. Your product.

Credit packs and pricing are identical to the web app — see the pricing page.

Questions about integrating? Contact us — read the API Terms before going live.