DINGG API · unofficial, by Cotlet
Create your own DINGG API
DINGG: no public API docs found on dingg.app or docs.dingg.app (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your DINGG 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 DINGG 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 DINGG. DINGG is a trademark of its owner. If DINGG's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/appointments-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/appointments-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/appointments-for-day",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-21"},
)
data = res.json()["data"] {
"data": [
{
"time": "10:00",
"client": "Neha S.",
"service": "Haircut",
"staff": "Riya"
},
{
"time": "11:30",
"client": "Mia K.",
"service": "Facial",
"staff": "Riya"
}
]
} 01 Build
How do you build a DINGG endpoint with Cotlet?
-
Sign in to DINGG 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 appointments with the client's name, service and staff member."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date or a staff member, 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 DINGG session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for DINGG
Cotlet ships no fixed list of DINGG endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/appointments-for-day Appointments for a day
Time, client, service and staff member of each appointment
-
POST
/api/v1/custom/sales-by-staff Sales by staff for a period
Sales per staff member and service
-
POST
/api/v1/custom/find-client Find a client
Matching clients with phone and last visit
-
POST
/api/v1/custom/low-stock Products to reorder
Products below their reorder level
-
POST
/api/v1/custom/writesblock-time Block time for a staff member
A blocked slot in that person's calendar
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/appointments-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": "10:00",
"client": "Neha S.",
"service": "Haircut",
"staff": "Riya"
},
{
"time": "11:30",
"client": "Mia K.",
"service": "Facial",
"staff": "Riya"
}
]
} 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 DINGG endpoints for?
- Schedule Cotlet endpoint WhatsApp or email
A morning report in n8n or Make.
Today's appointments and yesterday's sales, sent to WhatsApp or email before opening.
- Monday endpoint Google Sheets
A reorder list.
Products below their reorder level, pulled into Google Sheets every Monday.
- Website form endpoint free slots
A booking form on your own website.
Free slots for a service, read from DINGG when a visitor picks a day.
- Voice or chat agent endpoint free slots
Your own AI receptionist.
A voice or chat agent that checks free slots before it offers a time.
04 Access
What can an endpoint see and change?
An endpoint works in your own DINGG session, so it can read and change only what your DINGG 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 blocking time, 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 DINGG have an official API?
DINGG: no public API docs or webhooks found on dingg.app or docs.dingg.app (checked 20 Nov 2026). DINGG says client, appointment and sales data can be exported at any time. The full picture with sources: Does DINGG have an API or MCP server?
Want ChatGPT or Claude to work in DINGG instead of code? See the DINGG 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.
DINGG API with Cotlet: questions
Is this an official DINGG API?
No. Cotlet is independent and not affiliated with DINGG. The endpoints you build run in your own signed-in DINGG 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 DINGG changes its screens?
An endpoint works while DINGG works the way it did when you built it. If DINGG 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 DINGG 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.