Authentication
Pod Engine uses API tokens to authenticate requests. You need to include your API token in the header of all requests to access protected endpoints.
API Token
All API requests must include your token in the Authorization header:
You can find your unique API token URL in your Developer SettingsOne key per integration
You can create more than one key, so each integration, script or environment has its own. If one key leaks, revoke just that key and everything else keeps working.
- Create a key in Developer Settings with Create key. Give it a name that says what uses it. The full key is shown only once, so copy it straight away.
- Every key works the same way. Calls run as your team, count toward its plan and usage, and use the same Authorization header.
-
Revoke a key and it stops working on the next request, with a
401response. Your other keys aren't affected. - Each key shows when it was last used, so you can spot keys nothing uses any more.
Authentication Examples
Error Responses
If authentication fails, the API will respond with a 401 status code and the following error message:
{
"status": "UNAUTHORIZED",
"data": {
"message": "Invalid authorization token"
}
}Get started with the API and MCP server
One plan, everything included
- Full Pod Engine web app access
- Full API access — same data, programmatic
- MCP server
- 10,000 searches / mo
- 10,000 podcast and episode lookups / mo
- 1,000 transcripts / mo
- Historical podcast charts
- Contacts, emails, social & YouTube data
- 30 alerts
Available Discounts
We believe great tools should be accessible to everyone building amazing things.
Eligible for a discount? Contact us to learn more.
Bootstrapped Startups
50% off first year
Students & Educators
50% off first year
Nonprofits
50% off first year
Pay Annually
2 months free
Need Guest Booking, an Agency plan, or higher limits?
See the full pricing page for addons and Agency options, or schedule a call.
Need more than 10,000 searches / mo? Get in touch and we'll tailor a plan.