Simpro API · unofficial, by Cotlet
Create your own Simpro API
Simpro's API starts with an access request from your administrator, and the credentials come in a key file (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Simpro 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 Simpro 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 Simpro. Simpro is a trademark of its owner. If Simpro's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/schedule-for-day" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-21"}' const url = "https://cotlet.dev/api/v1/custom/schedule-for-day";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ date: "2026-11-21" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/schedule-for-day",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-21"},
)
data = res.json()["data"] {
"data": [
{
"time": "07:30",
"employee": "Sam",
"job": "20871",
"customer": "Harbor Dental",
"site": "12 Pier Rd"
},
{
"time": "10:00",
"employee": "Sam",
"job": "20884",
"customer": "Oak Cafe",
"site": "3 Elm St"
}
]
} 01 Build
How do you build a Simpro endpoint with Cotlet?
-
Sign in to Simpro 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 tomorrow's scheduled jobs with the employee, customer, site and start time."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date or an employee, 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 Simpro session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Simpro
Cotlet ships no fixed list of Simpro endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/schedule-for-day Schedule for a day
Time, employee, job, customer and site of each scheduled job
-
POST
/api/v1/custom/accepted-quotes Accepted quotes
Quotes the customer accepted that are not jobs yet, with their totals
-
POST
/api/v1/custom/job-costs Job costs
Time and materials on a job so far, by cost center
-
POST
/api/v1/custom/find-catalog-item Find a catalog item
Matching catalog items with their IDs and prices
-
POST
/api/v1/custom/writesadd-job-note Add a job note
A note on the job you name, seen by your team
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/schedule-for-day" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-21"}' The answer is JSON, with your fields under data:
{
"data": [
{
"time": "07:30",
"employee": "Sam",
"job": "20871",
"customer": "Harbor Dental",
"site": "12 Pier Rd"
},
{
"time": "10:00",
"employee": "Sam",
"job": "20884",
"customer": "Oak Cafe",
"site": "3 Elm St"
}
]
} 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 Simpro endpoints for?
- Schedule Cotlet endpoint Slack or email
An evening crew sheet in n8n or Make.
Tomorrow's jobs per employee, sent to Slack or email.
- Schedule endpoint Team chat
A quote follow-up list.
Accepted quotes that are not jobs yet, posted for the office each morning.
- Schedule endpoint Google Sheets
Job costing in a sheet.
Time and materials per job pulled into Google Sheets each week.
- Chat agent endpoint schedule
Your own AI assistant.
A chat agent that checks the schedule before it offers a customer a visit date.
04 Access
What can an endpoint see and change?
An endpoint works in your own Simpro session, so it can read and change only what your Simpro 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 adding a job note, 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 Simpro have an official API?
Simpro publishes an API that views, creates and edits resources on a Simpro build (checked 20 Nov 2026). An administrator submits an API access request in System, Setup, API, Applications, and the credentials come in a key file; whether Simpro reviews requests or charges for them is not stated. The full picture with sources: Does Simpro have an API or MCP server?
Want ChatGPT or Claude to work in Simpro instead of code? See the Simpro 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.
Simpro API with Cotlet: questions
Is this an official Simpro API?
No. Cotlet is independent and not affiliated with Simpro. The endpoints you build run in your own signed-in Simpro 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 Simpro changes its screens?
An endpoint works while Simpro works the way it did when you built it. If Simpro 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 Simpro 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.