Skip to content
J·BJon BishopFractional growth marketer

Communications · llms.txt file breakdown

Sent llms.txt

A directly retrieved Markdown index for Sent's documentation, with 242 links across 31 detected headings.

The actual file

Source Markdown

The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.

Open saved text ↗

Showing the first 18000 characters. Load the complete file to read the remainder.

# Sent Documentation

> Sent API Documentation

- Documentation & Guides: Concepts, quickstart, guides, webhooks, and more — everything to build with Sent.
  - [One API for SMS, WhatsApp, and RCS](/start.md): Build multi-channel messaging with the Sent unified API: send SMS, WhatsApp, and RCS through one interface with automatic routing, fallback, and cost control.

  - **Introduction**
  - [What is Sent](/start/why-sent/what-is-sent.md): A quick introduction to Sent, what it is, what it does, and the problems it solves for teams building with messaging.
  - [Built for Scale](/start/why-sent.md): Why messaging became infrastructure: the forces that outgrow custom code and how shared platforms turn aggregate traffic into better delivery for everyone.
  - [What Sent Solves](/start/why-sent/use-cases.md): The messaging problems Sent is built to solve: guaranteed delivery, multichannel reach, and high-volume scale, and the teams that benefit most from each one.
  - [Compare Your Options](/start/why-sent/comparison.md): Compare Sent with direct provider integration and building in-house: setup time, maintenance, cost structure, migration paths, and a decision flowchart.

  - **Try Before You Commit**
  - [Try Sent: Send Your First Message in 2 Minutes, No Code](/start/try-sent.md): Explore Sent capabilities through the Dashboard Playground and send real messages in minutes with no code required.

  - **Quickstart**
  - [Quickstart Overview](/start/quickstart.md): Send your first message in minutes with light onboarding: a verified email and phone gets you API access, six pre-built templates, and 500 sends per day.
  - [Account Setup](/start/quickstart/account-setup.md): Create your Sent account and complete KYC verification: business details, destination countries, messaging use case, and billing to unlock the full platform.
  - [Channel Setup](/start/quickstart/channel-setup.md): Configure your own SMS, WhatsApp, and RCS sender for production: select a phone number, connect WhatsApp Business, enable RCS, and set up billing in Sent.
  - [Create Your First Template](/start/quickstart/first-template.md): Create your first message template in the Sent Dashboard: add dynamic variables, submit for WhatsApp and RCS approval, and get the template ID for API sends.
  - [Send Your First Message](/start/quickstart/first-message.md): Make your first Sent API call to send an SMS, WhatsApp, or RCS message: get your API key, send with a template, read the response, and track delivery status.
  - [The Sent Dashboard](/start/quickstart/dashboard-walkthrough.md): Tour the Sent Dashboard: send messages from the playground, manage contacts and templates, generate API keys, and monitor deliverability and account balance.

  - **Core Concepts**
  - [Core Concepts Overview](/start/concepts.md): The fundamental concepts behind the Sent messaging platform - unified messaging, channels, contacts, templates, Sender Profiles, and how they fit together
  - [Platform Overview](/start/concepts/platform-overview.md): Understanding Sent's intelligent messaging architecture and how it powers omnichannel communication
  - [Unified Messaging Intelligence](/start/concepts/unified-messaging.md): Why Sent exposes one intent-based messaging interface instead of channel APIs, and how the routing engine selects channels, falls back, and stays compliant
  - [Channels](/start/concepts/channels.md): Why Sent routes SMS, MMS, RCS, and WhatsApp behind one send call: the four-channel model, channel discovery, routing factors, and content adaptation.
  - [SMS Encoding & Message Length](/start/concepts/sms-encoding-and-length.md): How SMS character encoding (GSM-7 vs Unicode) and message concatenation determine character limits, segment counts, and cost
  - [Contacts](/start/concepts/contacts.md): What a contact is in Sent - a validated, channel-aware communication endpoint that carries availability, formatting, and routing state for a phone number
  - [Templates](/start/concepts/templates.md): Why Sent messages are defined as templates, and how one channel-agnostic definition adapts its content, variables, and buttons to SMS, WhatsApp, and RCS
  - [Sender Profiles](/start/concepts/sender-profiles.md): Why Sent models multi-tenancy as organizations and Sender Profiles, which resources a profile can inherit, and which are always dedicated to it.
  - [API Authentication](/start/concepts/api-authentication.md): Why the Sent API v3 authenticates every request with a single API key sent as a request header, covering the security model, trade-offs, and OAuth comparison.
  - [Trust & Safety](/start/concepts/trust-and-safety.md): How Sent protects your account, your recipients, and the platform from spam, fraud, and abuse.
  - [What is 10DLC?](/start/concepts/10dlc.md): Why carriers in the United States require 10DLC registration for A2P SMS, how The Campaign Registry reviews brands and campaigns, and where Sent fits in

  - **Implementation Guides**
  - [Implementation Guides](/start/guides.md): Step-by-step guides for common messaging patterns with Sent: sending messages, tracking delivery status, managing contacts, templates, errors, and testing.
  - [Connect a WhatsApp Business Account (WABA) to Sent](/start/guides/connect-whatsapp.md): Connect a WhatsApp Business Account to Sent: Meta authorization, choosing the sending number, confirming the channel is live, disconnecting, and the Sender Profile path.
  - [Managing channels](/start/guides/managing-channels.md): Read and change a sender's channels through the API: SMS markets per country and sender type, the WhatsApp account, the RCS agent, the numbers that take phone calls, and what each one still owes for compliance.
  - [Creating and Managing API Keys](/start/guides/api-keys.md): How to create a Sent API key in the dashboard, store it safely in environment variables, verify it authenticates, and rotate or revoke keys independently.
  - [Sending Messages](/start/guides/sending-messages.md): How to send SMS, WhatsApp, and RCS messages with the Sent API: template sends, free-form text without a template, channel selection, and error handling.
  - [Message Best Practices](/start/guides/message-best-practices.md): Harden your Sent send path for production: store per-recipient message IDs, make critical sends idempotent, apply RCS send rules, and estimate bulk costs.
  - [Message Response Handling](/start/guides/message-responses.md): Parse Sent API v3 message-send responses: the success/data/error envelope, per-recipient message IDs, validation and auth error shapes, and async failures.
  - [SMS Length, Segments & Cost](/start/guides/sms-length-and-cost.md): How Sent counts SMS segments, how segments map to billing, and practical tips to keep messages short and predictable
  - [Message Status Tracking](/start/guides/message-status-tracking.md): Track Sent message delivery status in real time using webhook status events, API polling, and the dashboard, and handle failed messages and inbound replies.
  - [Two-Way Conversations](/start/guides/two-way-conversations.md): How Sent handles two-way conversations, from inbound matching and storage to keyword detection, opt-out handling, auto-replies, and the conversation rules that gate free-form replies on SMS, RCS, and WhatsApp.
  - [Answering Calls](/start/guides/answering-calls.md): How your backend answers calls with the Sent API: the question Sent sends to your callback URL, the answer it expects, signature verification, deadlines and retries, cookies, and the test endpoint.
  - [Calls From Your App](/start/guides/in-app-calls.md): How a user of your web app places and receives phone calls with Sent: mint voice tokens on your backend, register the browser with the Sent voice SDK, and route calls by department.
  - [Calls, Recordings, and Participants](/start/guides/managing-calls.md): How to read a call record, hang up a live call, start and stop recordings and download them, and add, mute and remove conference participants with the Sent API.
  - [Voice Recipes](/start/guides/voice-recipes.md): Six worked answers for your voice callback, taken from the Sent voice example app: ring an app user with a phone fallback, a basic IVR menu, a hold, a recorded call, a room per call, and routing by department.
  - [Handling Opt-Outs and Consent](/start/guides/opt-out-and-consent.md): How to mirror Sent opt-outs into your own database, set contact opt-out state through the API, detect consent-blocked sends, and apply a stricter send window.
  - [Managing Contacts](/start/guides/managing-contacts.md): Import your user base into Sent, honor opt-outs, and control channel routing per contact. Covers automatic contact creation, phone validation, and search.
  - [Working with Templates](/start/guides/working-with-templates.md): Start here for Sent message templates: build one in the dashboard, look up the definition JSON in the reference, and learn how templates and approval work.
  - [Create a Template in the Dashboard](/start/guides/create-a-template.md): Step-by-step directions for building a message template in the Sent dashboard: header, body, dynamic variables, buttons, category, and review submission.
  - [Creating a Sender Profile](/start/guides/creating-a-sender-profile.md): Create a Sender Profile in the Sent dashboard: identity, brand, campaign, billing and notification choices, channels, WhatsApp, number type, and 10DLC or alphasender registration.
  - [Integrating Sender Profiles into Your Application](/start/guides/integrating-sender-profiles.md): Route messages through Sender Profiles in a multi-tenant app: profile API keys, per-customer sends, and per-profile webhook tracking across eight languages.
  - [Batch Operations](/start/guides/batch-operations.md): How to send messages in bulk with the Sent API: batches of up to 1000 recipients, rate limit management, idempotent retries, and bulk contact imports.
  - [Error Handling](/start/guides/error-handling.md): Handle errors gracefully with retries, circuit breakers, and fallback strategies
  - [How to handle Sent API errors](/start/guides/handling-api-errors.md): Handle Sent API v3 error responses in client code: check the success flag, branch on error codes, capture request IDs, and test failures with sandbox mode.
  - [How to retry Sent API requests safely](/start/guides/retrying-requests-safely.md): Retry Sent API v3 requests without duplicating messages or contacts: derive stable idempotency keys, reuse them across retries, and resolve conflicts.
  - [How to handle Sent API rate limits](/start/guides/handling-rate-limits.md): Keep your integration under Sent API v3 rate limits: back off on 429 responses, honor Retry-After, throttle requests client-side, and pace batch workloads.
  - [Testing & Debugging](/start/guides/testing-debugging.md): Test and debug your Sent integration by validating sends with sandbox mode, unit-testing webhook handlers, verifying signatures, and tracing failures.
  - [Testing with Sandbox Mode](/start/guides/testing-with-sandbox-mode.md): How to test a Sent integration with sandbox mode: assert against real API responses, run CI suites without sending messages, and reproduce failures safely.

  - **Webhooks & Events**
  - [Webhooks & Events Overview](/start/webhooks.md): Receive real-time message delivery notifications, inbound messages, and template approval events via webhooks, with guides for setup, security, and retries
  - [Webhook Setup](/start/webhooks/getting-started.md): Register a webhook endpoint in the Sent Dashboard, choose the message and template events to subscribe to, and verify your configuration with a test delivery
  - [Webhooks Lifecycle](/start/webhooks/lifecycle.md): How a webhook delivery moves from event generation through signing, retries, and the threshold that turns a failing webhook off, plus the events Sent emits
  - [Events Reference](/start/webhooks/event-types.md): Complete catalog of webhook event types and JSON payloads for all Sent webhook events
  - [Receiving Inbound Messages via the message.received Webhook](/start/webhooks/receiving-inbound-messages.md): How to receive contact replies in real time with the message.received webhook, acknowledge and deduplicate deliveries, and skip compliance keywords.
  - [Security](/start/webhooks/signature-verification.md): Verify webhook authenticity and implement security best practices for Sent webhooks
  - [Handling Retries](/start/webhooks/handling-retries.md): Make your Sent webhook handler idempotent: key on the event ID header, handle duplicate and out-of-order events, and understand why retries happen.
  - [Local Development & Debugging](/start/webhooks/local-development.md): Expose your local server to receive Sent webhooks through a tunnel, send test events, debug failed deliveries, and process events reliably with queues
  - [Production Checklist](/start/webhooks/production-checklist.md): Pre-launch checklist for Sent webhook handlers: HTTPS and signature verification, idempotency, monitoring, error handling, scaling, and a runbook template.

  - **Advanced Topics**
  - [Advanced Guides Overview](/start/advanced.md): Advanced guides for platforms and enterprises building on Sent: performance optimization, 10DLC registration, compliance, v2 to v3 migration, and multi-tenancy.
  - [Performance optimization: high throughput on the Sent API](/start/advanced/performance-optimization.md): Optimize Sent API throughput: stay under the 10,000 requests per minute rate limit, batch up to 1,000 recipients per request, cache reads, and queue sends.
  - [10DLC Registration Guide](/start/advanced/10dlc-registration.md): How to register your brand and messaging campaigns with TCR through the Sent dashboard, including the form inputs, opt-in rules, and autoresponses required
  - [Register 10DLC Campaigns via the API](/start/advanced/10dlc-campaigns-api.md): Create, track, update, and delete 10DLC campaigns with the Sent API, from SENT_CREATED to ACTIVE, plus bulk registration patterns for agencies and resellers.
  - [Compliance & Regulations](/start/advanced/compliance-regulations.md): The compliance controls Sent enforces automatically at send time, what remains your responsibility, and per-region regulations with authoritative sources.
  - [API v2 to v3 Migration](/start/advanced/migration-v2-v3.md): Migrate your integration from the legacy Sent v2 API to v3 and update auth headers, request and response envelopes, error codes, webhooks, and idempotency.
  - [Multi-tenant architectures on Sent: profiles vs. accounts](/start/advanced/multi-tenant-architectures.md): Choose a tenant model for your messaging platform: Sender Profiles with per-tenant provisioning, one shared Sent account, or separate accounts per tenant.
  - [Create and activate Sender Profiles via the API](/start/advanced/sender-profiles-api.md): Create Sender Profiles with the Sent API: the minimum request, which resources are dedicated versus inherited, giving a profile a sender, and reading what its compliance still owes.

  - **Help & Reference**
  - [Help & Reference Overview](/start/reference-guides.md): Quick answers when you need help with Sent: frequently asked questions, problem-solution troubleshooting guides, error code references, and support channels.
  - [Frequently Asked Questions](/start/reference-guides/faq.md): Answers to common questions about Sent: getting started without KYC, pricing and billing, messaging and templates, webhooks, security, and technical limits.
  - [Troubleshooting Common Issues](/start/reference-guides/troubleshooting.md): Quick problem-to-solution fixes for common Sent issues: authentication errors, message sending failures, template rejections, webhooks, and channel setup.
  - [Support & Developer Resources](/start/reference-guides/support.md): Get help with Sent: support channels and response times, plus changelog, glossary, error catalog, troubleshooting guides, and FAQ resources for developers.

  - **LLM & AI Access**
  - [Docs for LLMs & AI Agents](/start/llm-docs.md): Machine-readable versions of the Sent documentation, plain-text files optimized for LLMs, AI coding assistants, and autonomous agents.
  - [Sent MCP Server](/start/llm-docs/mcp-server.md): Use Sent directly from Claude, Claude Code, Cursor, VS Code, and other AI agents via the Model Context Protocol
- Build with Sent: The production blueprint — architect and ship a robust Sent integration, layer by layer, in any language.
  - [Build with Sent](/build.md): The production blueprint for integrating Sent: architecture, the outbound and inbound paths, and everything you need to ship a resilient, secure integration.

  - **Foundations**
  - [Reference Architecture](/build/architecture.md): The anatomy of a production Sent integration: the layers, the outbound and inbound request flows, the HTTP surface your app exposes, and where state lives.
  - [Setting Up the Project: SDK, Config, and Folder Layout](/build/project-setup.md): Prerequisites, SDK installation, the SDK-vs-raw-REST decision, config validation that fails fast, and a folder layout that realizes the reference architecture.
  - [Authenticating Requests with Per-Request Clients](/build/authentication.md): Build a Sent SDK client from the request's bearer key. Per-request client factories in seven frameworks, 401 guards, key verification, and easy rotation.
  - [About Per-Request Credentials](/build/per-request-credentials.md): Why the Sent API key is a per-request credential, never a boot-time singleton. Who sends the bearer key in each setup, and why isolation is structural.

  - **Sending Messages**
  - [Sending Messages with the Sent SDK: The Outbound Path](/build/sending-messages.md): A thin, testable service layer over messages.send: the request shape, multi-recipient response mapping, channels, sandbox sends, and where status comes from.
  - [Managing Contacts & Templates](/build/contacts-and-templates.md): Service wrappers for con

Measured from the saved file

Links and embedded code

UTF-8 text size
102.0 KB104436 bytes
Token count
22820o200k_base encoding
Markdown links
240239 distinct URLs
Fenced code blocks
3797 lines in the file

Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.

Project H1
Sent Documentation

Opening blockquote

Sent API Documentation

Context architecture

How the content is divided

30 H2 sections organize 240 parsed Markdown links. 237 links point to .md or .markdown paths; 3 link occurrences use another hostname. Linked destinations have not been recursively validated.

H2 sectionLinksUTF-8 bytesTokens
The minimumLine 2670477110
Saying what a profile ownsLine 27302111481
Use cases and volumeLine 2950889198
ComplianceLine 30301049223
Uploading documentsLine 31101573357
WhatsApp and RCSLine 33912373478
ResponsesLine 35522009442
What it releasesLine 37132383521
What `compliance` carriesLine 3920577119
Writing it backLine 4001772191
What to have in place firstLine 41501471310
Sending itLine 42711808420
Partial, at every levelLine 442038189
What a US `TEN_DLC` market holdsLine 4520846201
Every other marketLine 467024256
What it will refuseLine 47122749581
Show 14 more sections
H2 sectionLinksUTF-8 bytesTokens
What it asks forLine 49301812411
What comes back, and what does notLine 51353797884
What it changesLine 5420899214
What it will refuseLine 5541484281888
ChannelLine 59001145247
`setup[]` — what to doLine 60001152261
`requirements[]` — what each value meansLine 6100519111
When nothing is requiredLine 61632210451
WhatsApp Business AccountLine 6310503100
BrandLine 637014334
Payment DetailsLine 6411967203
Brand ManagementLine 648035576
Payment DetailsLine 652037482
Deprecated fieldsLine 65654196294068

Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.

Embedded material

Code, installation and API examples

Fenced blocks
3 closed
Declared languages
json (2), bash (1)
Package-install commands
0 detected in fenced or inline code
Authentication examples
1 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
1 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels

Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.

Inspect detected API and authentication lines

Source line 319 · bash

  -H 'x-api-key: YOUR_SECRET_TOKEN' \

Source line 318 · bash

curl -X POST https://api.sent.dm/v3/sender-profiles \

Publisher prioritization

The Optional section

No H2 section named “Optional” was detected in this file.

The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.

Machine-readable routes

MCP references and configuration text

MCP-related text was detected in the captured file. 1 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.

These are text and link observations. No MCP server connection, authentication or tool call was tested.

Index and bundle

llms-full.txt companion

Verified text companion

Text companion verified

https://docs.sent.dm/llms-full.txt ↗
Discovery
Conventional sibling path checked
HTTP response
200 · text/plain;charset=UTF-8
Text size
Whole-file size not established by the bounded response
Token count
Not measured for the whole file
Retrieval scope
Bounded prefix inspected; the whole body was not downloaded

A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.

Change evidence

What can be said about freshness

This capture establishes a baseline. Update frequency cannot be determined from one observation.

Linked release and migration material

2 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.

File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.

Capture identity and measurement method
Requested endpoint
https://docs.sent.dm/llms.txt
Final endpoint
https://docs.sent.dm/llms.txt
HTTP status
200
Content type
text/plain;charset=UTF-8
Text retrieval
Firecrawl literal text capture
Tokenizer
tiktoken 0.14.0 · o200k_base
SHA-256 of saved UTF-8 text
8bd3a37766e149e1a235a1a1d61ac9192ee1df7ae2e73ec4b97185a04d1e102f

Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.

Related tools and resources

Contact Jon