oto.photo API · unofficial, by Cotlet
Create your own oto.photo API
oto.photo: no public API, webhooks or Zapier app found on oto.photo (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your oto.photo 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 oto.photo 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 oto.photo. oto.photo is a trademark of its owner. If oto.photo's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/sessions-for-week" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"from": "2026-11-23", "to": "2026-11-29"}' const url = "https://cotlet.dev/api/v1/custom/sessions-for-week";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ from: "2026-11-23", to: "2026-11-29" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/sessions-for-week",
headers={"Authorization": f"Bearer {key}"},
json={"from": "2026-11-23", "to": "2026-11-29"},
)
data = res.json()["data"] {
"data": [
{
"date": "2026-11-28",
"time": "09:00",
"client": "The Parks",
"session": "Family session"
},
{
"date": "2026-11-28",
"time": "14:00",
"client": "Mia K.",
"session": "Headshots"
}
]
} 01 Build
How do you build an oto.photo endpoint with Cotlet?
-
Sign in to oto.photo 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 my sessions for next week with the client, session type and time."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date range or a client, 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 oto.photo session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for oto.photo
Cotlet ships no fixed list of oto.photo endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/sessions-for-week Sessions for a period
Date, time, client and session type for each booking
-
POST
/api/v1/custom/gallery-favorites Gallery favorites
Which clients picked favorites, and how many
-
POST
/api/v1/custom/open-dates Open dates
Days with no session booked in the period you pick
-
POST
/api/v1/custom/find-client Find a client
Matching clients with phone, email and past sessions
-
POST
/api/v1/custom/writesadd-client Add a client
A new client with phone, email and a note
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/sessions-for-week" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"from": "2026-11-23", "to": "2026-11-29"}' The answer is JSON, with your fields under data:
{
"data": [
{
"date": "2026-11-28",
"time": "09:00",
"client": "The Parks",
"session": "Family session"
},
{
"date": "2026-11-28",
"time": "14:00",
"client": "Mia K.",
"session": "Headshots"
}
]
} 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 oto.photo endpoints for?
- Sunday Cotlet endpoint Email
A weekly plan.
Next week's sessions, sent to your email on Sunday.
- Website form endpoint new client
Inquiries from your website.
A contact form that adds each inquiry as a client in oto.photo.
- Daily endpoint Google Sheets
An editing queue.
Galleries with new favorites listed in a sheet, so you know what to edit first.
- Chat agent endpoint open dates
Your own booking assistant.
A chat agent that checks open dates before it offers one.
04 Access
What can an endpoint see and change?
An endpoint works in your own oto.photo session, so it can read and change only what your oto.photo login can. You choose what each endpoint does when you build it.
An endpoint that changes something, such as adding a client, 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 oto.photo have an official API?
oto.photo: no developer docs, API keys or webhooks found on oto.photo, and its llms.txt summary for AI readers names none (checked 20 Nov 2026). The full picture with sources: Does oto.photo have an API or MCP server?
Want ChatGPT or Claude to work in oto.photo instead of code? See the oto.photo 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.
oto.photo API with Cotlet: questions
Is this an official oto.photo API?
No. Cotlet is independent and not affiliated with oto.photo. The endpoints you build run in your own signed-in oto.photo 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 oto.photo changes its screens?
An endpoint works while oto.photo works the way it did when you built it. If oto.photo 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 oto.photo 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.