Developer documentation

Textycally is an SMS API for small businesses: one REST surface for sending messages, receiving replies, and tracking delivery — plus a dashboard for numbers, inbox, and billing. Everything the dashboard does, the API does too.

How the platform fits together

Your account is approved by a human (usually within hours), after which you mint a show-once API key in onboarding. Every API request authenticates with that key as a bearer token against https://relay.blackleafdigital.com:

Notifications — POST /v1/notifications dispatches messages; each recipient becomes a delivery record with per-attempt status you can poll.
Conversations — attach a conversation to a notification and inbound replies are threaded into a transcript you can fetch by ID (they also land in the dashboard inbox).
Idempotency — every send carries an idempotencyKey; retrying the same key returns the original record instead of double-sending.

Sections

Quickstart — Sign up, get approved, and send your first SMS in five steps — then receive replies and check delivery status.
API reference — Interactive reference for every tenant-facing endpoint: notifications, conversations, web push, and the embed tier.
TypeScript SDK — Typed client over the same REST API — install from our registry, construct a client, send with full type safety.
Errors — The one error envelope every endpoint returns, the stable error codes, and which failures are safe to retry.

Base URL and authentication

Base URL	`https://relay.blackleafdigital.com`
Authentication	`Authorization: Bearer <your API key>` on every request
Content type	`application/json` request and response bodies
Errors	One envelope everywhere: `{ code, message, retryable, requestId }` — see Errors

 Getting help
 
Stuck? Email support@textycally.com
with the requestId from any error response and we can trace
    the exact request.