Okendo API · unofficial, by Cotlet
Create your own Okendo API
Okendo's Merchant API needs the Advanced plan or above, or a paid add-on (checked 19 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Okendo 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 Okendo 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 Okendo. Okendo is a trademark of its owner. If Okendo's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/pending-low-reviews" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"max_rating": 2}' const url = "https://cotlet.dev/api/v1/custom/pending-low-reviews";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ max_rating: 2 }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/pending-low-reviews",
headers={"Authorization": f"Bearer {key}"},
json={"max_rating": 2},
)
data = res.json()["data"] {
"data": [
{
"product": "Linen shirt",
"rating": 2,
"reviewer": "Ben T.",
"text": "Runs small, had to return it.",
"submitted": "2026-11-18"
},
{
"product": "Wool beanie",
"rating": 1,
"reviewer": "Omar S.",
"text": "Arrived a week late.",
"submitted": "2026-11-19"
}
]
} 01 Build
How do you build an Okendo endpoint with Cotlet?
-
Sign in to Okendo 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 reviews waiting in moderation with 2 stars or fewer, with product, rating and text."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a rating or a product, 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 Okendo session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Okendo
Cotlet ships no fixed list of Okendo endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/pending-low-reviews Low reviews in moderation
Product, rating, reviewer and text of each pending review under the rating you name
-
POST
/api/v1/custom/reviews-mentioning Reviews that mention a word
Reviews with the word you give, with product, rating and date
-
POST
/api/v1/custom/product-ratings Ratings by product
Average rating and review count for each product
-
POST
/api/v1/custom/open-questions Open product questions
Shopper questions still waiting for an answer, by product
-
POST
/api/v1/custom/writesreply-to-review Reply to a review
A public reply posted on the review you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/pending-low-reviews" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"max_rating": 2}' The answer is JSON, with your fields under data:
{
"data": [
{
"product": "Linen shirt",
"rating": 2,
"reviewer": "Ben T.",
"text": "Runs small, had to return it.",
"submitted": "2026-11-18"
},
{
"product": "Wool beanie",
"rating": 1,
"reviewer": "Omar S.",
"text": "Arrived a week late.",
"submitted": "2026-11-19"
}
]
} 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 Okendo endpoints for?
- Schedule Cotlet endpoint Slack or email
A Monday low-review digest in n8n or Make.
Last week's low reviews, sent to Slack or email with the product for each.
- Schedule endpoint Support desk
Low reviews in your support desk.
A new low review becomes a ticket, so your team follows up on the order.
- Schedule endpoint Google Sheets
A product dashboard.
Ratings by product pulled into Google Sheets each week for the merchandising team.
- Chat agent endpoint reviews
Your own AI assistant.
A chat agent that reads what shoppers say about a product before it answers a sizing question.
04 Access
What can an endpoint see and change?
An endpoint works in your own Okendo session, so it can read and change only what your Okendo 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 replying to a review, 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 Okendo have an official API?
Okendo has a Merchant API with credentials from its integration settings, on the Advanced plan or above, or as a paid add-on on lower plans (checked 19 Nov 2026). Its MCP server shows only published reviews and Q&A. The full picture with sources: Does Okendo have an API or MCP server?
Want ChatGPT or Claude to work in Okendo instead of code? See the Okendo 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.
Okendo API with Cotlet: questions
Is this an official Okendo API?
No. Cotlet is independent and not affiliated with Okendo. The endpoints you build run in your own signed-in Okendo 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 Okendo changes its screens?
An endpoint works while Okendo works the way it did when you built it. If Okendo 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 Okendo 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.