Developers
Company API
Give your product a Send key and post shorts to the accounts you already connected — Instagram, Facebook, TikTok, YouTube, X, LinkedIn, Threads, Pinterest.
Same idea as Buffer
A key for your backend. Not a login code.
API access is free with a paid plan. You buy The Send on Whop, log in, then mint a key. Cancel the plan and the keys die. Guessing a key does not get anyone a free send. Posting endpoints reject missing, fake, revoked, and unpaid keys. Connect accounts in the app first. The API does not log you into Instagram or YouTube by itself.
Whop send_… codes unlock the app in a browser. API keys (tsk_…) are for servers, Zapier-style tools, and other company products. Each key posts as that Send account, to that brand’s connected channels.
SuperGrok
Connect The Send in Grok like GitHub
If you have SuperGrok, Grok Bot, or X Premium+, add The Send as a custom MCP connector. Grok can then see this account’s brands, queue, and connected channels. It connects for an active free trial or a paid membership. In Grok Bot, ask it to add https://getthesend.com/mcp.
- Start a free trial or buy The Send, log in at /app, then connect Instagram/YouTube as usual.
- Open grok.com/connectors → New Connector → Custom.
- Paste
https://getthesend.com/mcpand approve SuperGrok when The Send asks.
https://getthesend.com/mcp # Grok Build / SuperGrok Heavy grok mcp add --transport http the-send https://getthesend.com/mcp
- Subscribe on Whop, then log in at /app.
- Connect the social accounts for the brand.
- Open Company API, name a key, copy it once.
- Send
Authorization: Bearer tsk_…to/api/v1.
Auth
Every request carries the key
Authorization: Bearer tsk_your_key # or X-Api-Key: tsk_your_key
Active paid plan required on every call. 60 requests per minute per key. Failed guesses from the same IP are throttled. HTTPS only in production. The Send never stores the plaintext key after you leave the create screen.
Endpoints
REST at /api/v1
| Method | Path | What it does |
|---|---|---|
| GET | /api/v1 | Discovery (no auth) |
| GET | /api/v1/account | Plan, brand, connected channels |
| GET | /api/v1/channels | Which networks are connected |
| POST | /api/v1/media | Upload MP4/JPG, or pass a public https URL |
| GET | /api/v1/posts | List queue / calendar items |
| POST | /api/v1/posts | Create a short (file, mediaId, or mediaUrl) |
| GET | /api/v1/posts/:id | One post |
| PATCH | /api/v1/posts/:id | Edit title, text, channels, schedule |
| DELETE | /api/v1/posts/:id | Remove it |
| POST | /api/v1/posts/:id/send | Publish now to connected channels |
Create + queue a short
curl https://getthesend.com/api/v1/posts \ -H "Authorization: Bearer tsk_YOUR_KEY" \ -F "[email protected]" \ -F "title=Spring AC tune-up" \ -F "text=Book your tune-up this week. Call the shop." \ -F "channels=instagram,tiktok,facebook,youtube" \ -F "scheduledAt=2026-08-25T14:00:00Z"
Or JSON with a public media URL
curl https://getthesend.com/api/v1/posts \
-H "Authorization: Bearer tsk_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"mediaUrl": "https://cdn.example.com/short.mp4",
"text": "Same clip, every network.",
"channels": ["instagram", "tiktok"],
"send": true
}'
See what’s connected
curl https://getthesend.com/api/v1/channels \ -H "Authorization: Bearer tsk_YOUR_KEY"
Pass "send": true to publish immediately. Otherwise the post sits in the queue until you send or until the scheduler hits scheduledAt. Unique titles, captions, and hashtags still run per network when copy is enabled.
When an in-memory Send now job is already running for that post, POST /api/v1/posts/:id/send returns HTTP 200 with ok true, the current post (status sending), and skipped as an empty list. That JSON does not include alreadyRunning, jobId, results, or error. The MCP send_post tool returns ok true and that post. alreadyRunning is not in the tool result. A second v1 send while a direct send holds the file lock, and that post is not in the in-memory job set, returns HTTP 400 with ok false and error send already in progress. alreadyRunning is not in that body. The MCP send_post tool then returns ok false and error send already in progress. alreadyRunning is not in the tool result.
Limits
What this key can and cannot do
It posts as your Send account. It does not log into other people’s Send accounts. Third-party OAuth apps (customers connecting their Send to your product) come later — same split Buffer uses between a personal key and an app client.
- Up to 5 keys per account. Revoke from /app.
- A key is pinned to the brand you created it on, unless you are the operator.
- Connect accounts in the app first. The API will not complete Meta/TikTok/YouTube OAuth for you.
- Video max 200MB. Public media URLs must be https on a public host.
