Sendible API · unofficial, by Cotlet
Create your own Sendible API
Sendible: its API currently supports only SSO integration, with access through Sendible sales (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Sendible account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Sendible session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Sendible. Sendible is a trademark of its owner. If Sendible's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/scheduled-posts" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"workspace": "Bloom Bakery", "days": 7}' const url = "https://cotlet.dev/api/v1/custom/scheduled-posts";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ workspace: "Bloom Bakery", days: 7 }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/scheduled-posts",
headers={"Authorization": f"Bearer {key}"},
json={"workspace": "Bloom Bakery", "days": 7},
)
data = res.json()["data"] {
"data": [
{
"network": "Instagram",
"scheduled_at": "2026-11-21 08:00",
"text": "Fresh from the oven this morning.",
"status": "scheduled"
},
{
"network": "Facebook",
"scheduled_at": "2026-11-21 11:30",
"text": "Weekend orders close Friday at noon.",
"status": "scheduled"
}
]
} 01 Build
How do you build a Sendible endpoint with Cotlet?
-
Sign in to Sendible in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "List the posts scheduled for the next 7 days in a client workspace, with the network, time and text."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a client workspace or a number of days, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Sendible session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Sendible
Cotlet ships no fixed list of Sendible endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/scheduled-posts Scheduled posts
Network, time, text and status of each post in a client workspace
-
POST
/api/v1/custom/awaiting-approval Posts awaiting approval
Each post waiting for a client, with the workspace and the date it was sent
-
POST
/api/v1/custom/inbox-unanswered Inbox messages without a reply
Network, sender and text of each new comment or message
-
POST
/api/v1/custom/engagement-summary Engagement for a period
Engagement by profile for each client workspace
-
POST
/api/v1/custom/writesmove-post Move a post
The post moved to the time you send
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/scheduled-posts" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"workspace": "Bloom Bakery", "days": 7}' The answer is JSON, with your fields under data:
{
"data": [
{
"network": "Instagram",
"scheduled_at": "2026-11-21 08:00",
"text": "Fresh from the oven this morning.",
"status": "scheduled"
},
{
"network": "Facebook",
"scheduled_at": "2026-11-21 11:30",
"text": "Weekend orders close Friday at noon.",
"status": "scheduled"
}
]
} When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.
03 Uses
What can you use your Sendible endpoints for?
- Schedule Cotlet endpoint Slack or email
A Monday approvals report in n8n or Make.
Posts still waiting for client approval, sent to Slack for the account managers.
- Schedule endpoint Google Sheets
A client report sheet.
Engagement for each client workspace pulled monthly into Google Sheets or Looker Studio.
- Project tool endpoint calendar
A content plan from your project tool.
Posts approved in your own tool, moved into the Sendible calendar at the planned times.
- Schedule endpoint help desk
A support desk feed.
New inbox comments with a question, sent to your help desk as tickets.
04 Access
What can an endpoint see and change?
An endpoint works in your own Sendible session, so it can read and change only what your Sendible login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.
An endpoint that changes something, such as moving a post, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.
05 Official API
Does Sendible have an official API?
Sendible's help center says: "We currently only support SSO integration via our API." Access goes through a sales agent or customer success manager, and no public API docs were found (checked 20 Nov 2026). Sendible's Zapier app creates, approves and deletes posts. The full picture with sources: Does Sendible have an API or MCP server?
Want ChatGPT or Claude to work in Sendible instead of code? See the Sendible MCP server.
06 Pricing
What does it cost?
- per successful call
- 10 credits
- when a call fails
- 0
- in the smallest pack
- ≈ 500 calls
- free trial, no card
- 7 days
A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.
Sendible API with Cotlet: questions
Is this an official Sendible API?
No. Cotlet is independent and not affiliated with Sendible. The endpoints you build run in your own signed-in Sendible account.
Do I need to code?
Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.
What happens when Sendible changes its screens?
An endpoint works while Sendible works the way it did when you built it. If Sendible changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.
How long can a call take?
Up to 90 seconds, and the answer can be up to 1 MB of JSON.
Build your first Sendible endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.