Libsyn API · unofficial, by Cotlet
Create your own Libsyn API
Libsyn lists API access only with its Professional and Enterprise plans, arranged by contacting Libsyn (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Libsyn 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 Libsyn 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 Libsyn. Libsyn is a trademark of its owner. If Libsyn's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/episode-downloads" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"days": 30}' const url = "https://cotlet.dev/api/v1/custom/episode-downloads";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ days: 30 }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/episode-downloads",
headers={"Authorization": f"Bearer {key}"},
json={"days": 30},
)
data = res.json()["data"] {
"data": [
{
"episode": 142,
"title": "Hiring your first editor",
"published": "2026-11-11",
"downloads": 1240
},
{
"episode": 141,
"title": "Pricing your first offer",
"published": "2026-11-04",
"downloads": 1810
}
]
} 01 Build
How do you build a Libsyn endpoint with Cotlet?
-
Sign in to Libsyn 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 episodes from the last 30 days with their downloads."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a number of days or an episode, 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 Libsyn session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Libsyn
Cotlet ships no fixed list of Libsyn endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/episode-downloads Downloads by episode
Title, publish date and downloads for each episode
-
POST
/api/v1/custom/scheduled-episodes Scheduled episodes
Episodes waiting to publish, with date and time
-
POST
/api/v1/custom/downloads-by-country Downloads by country
Downloads per country for a period
-
POST
/api/v1/custom/drafts-missing-details Drafts missing details
Drafts without audio, a title or show notes
-
POST
/api/v1/custom/writesupdate-show-notes Update show notes
New show notes on the episode you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/episode-downloads" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"days": 30}' The answer is JSON, with your fields under data:
{
"data": [
{
"episode": 142,
"title": "Hiring your first editor",
"published": "2026-11-11",
"downloads": 1240
},
{
"episode": 141,
"title": "Pricing your first offer",
"published": "2026-11-04",
"downloads": 1810
}
]
} 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 Libsyn endpoints for?
- Schedule Cotlet endpoint Slack or email
A weekly downloads report.
Last week's downloads by episode, posted to Slack or sent by email every Monday.
- Schedule endpoint Google Sheets
A sponsor report.
Downloads of the episodes a sponsor ran on, pulled into a sheet for the invoice.
- Website endpoint episodes
An episode list on your own site.
The latest episodes with titles and dates, read from Libsyn when a visitor opens the page.
- Chat agent endpoint drafts
Your own AI producer.
A chat agent that checks which drafts are missing show notes before a release day.
04 Access
What can an endpoint see and change?
An endpoint works in your own Libsyn session, so it can read and change only what your Libsyn 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 updating show notes, 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 Libsyn have an official API?
Libsyn: no public API docs or self-serve keys found on libsyn.com (checked 20 Nov 2026). Its plans page lists API access among the advanced tools of the Professional and Enterprise plans. The full picture with sources: Does Libsyn have an API or MCP server?
Want ChatGPT or Claude to work in Libsyn instead of code? See the Libsyn 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.
Libsyn API with Cotlet: questions
Is this an official Libsyn API?
No. Cotlet is independent and not affiliated with Libsyn. The endpoints you build run in your own signed-in Libsyn 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 Libsyn changes its screens?
An endpoint works while Libsyn works the way it did when you built it. If Libsyn 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 Libsyn 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.