SimpleTexting API · unofficial, by Cotlet
Create your own SimpleTexting API
SimpleTexting's API is given by approval only, on a paid plan (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your SimpleTexting 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 SimpleTexting 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 SimpleTexting. SimpleTexting is a trademark of its owner. If SimpleTexting's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/unread-texts" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"hours": 24}' const url = "https://cotlet.dev/api/v1/custom/unread-texts";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ hours: 24 }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/unread-texts",
headers={"Authorization": f"Bearer {key}"},
json={"hours": 24},
)
data = res.json()["data"] {
"data": [
{
"contact": "Dana R.",
"phone": "+1 555 0142",
"received": "08:12",
"message": "Open on the 26th?"
},
{
"contact": "Tom H.",
"phone": "+1 555 0188",
"received": "09:40",
"message": "Holiday class times?"
}
]
} 01 Build
How do you build a SimpleTexting endpoint with Cotlet?
-
Sign in to SimpleTexting 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 unread texts from the last 24 hours with the contact, number and message."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a number of hours or a list, 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 SimpleTexting session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for SimpleTexting
Cotlet ships no fixed list of SimpleTexting endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/unread-texts Unread texts
Contact, number, time and message for each unread text
-
POST
/api/v1/custom/campaign-results Campaign results
Sent, replies and unsubscribes for each campaign
-
POST
/api/v1/custom/keyword-answers Keyword answers
Answers collected by a keyword, with the contact
-
POST
/api/v1/custom/list-contacts Contacts in a list
Name, number and date added for a list
-
POST
/api/v1/custom/writessend-reply Send a reply
A text sent to the contact you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/unread-texts" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"hours": 24}' The answer is JSON, with your fields under data:
{
"data": [
{
"contact": "Dana R.",
"phone": "+1 555 0142",
"received": "08:12",
"message": "Open on the 26th?"
},
{
"contact": "Tom H.",
"phone": "+1 555 0188",
"received": "09:40",
"message": "Holiday class times?"
}
]
} 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 SimpleTexting endpoints for?
- Schedule Cotlet endpoint Slack
Unread texts in your team chat.
New texts posted to Slack so the right person answers.
- Schedule endpoint Google Sheets
A campaign report.
Sends, replies and unsubscribes pulled into Google Sheets each week.
- Booking endpoint text sent
Your booking system.
A confirmation text sent when a class is booked.
- Chat agent endpoint texts
Your own AI assistant.
A chat agent that reads new texts and drafts answers from your FAQ.
04 Access
What can an endpoint see and change?
An endpoint works in your own SimpleTexting session, so it can read and change only what your SimpleTexting 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 sending a reply, 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 SimpleTexting have an official API?
SimpleTexting has an API on paid plans, given by approval: "We offer our API under approval only to ensure better security for everyone." The review usually takes 1 to 2 business days (checked 20 Nov 2026). The full picture with sources: Does SimpleTexting have an API or MCP server?
Want ChatGPT or Claude to work in SimpleTexting instead of code? See the SimpleTexting 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.
SimpleTexting API with Cotlet: questions
Is this an official SimpleTexting API?
No. Cotlet is independent and not affiliated with SimpleTexting. The endpoints you build run in your own signed-in SimpleTexting 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 SimpleTexting changes its screens?
An endpoint works while SimpleTexting works the way it did when you built it. If SimpleTexting 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 SimpleTexting 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.