Enterprise API v1

These APIs are exclusively for enterprise customers and are currently in public beta, subject to change.

To use these APIs or inquire about pricing, please contact us: support@podwise.ai.

Base URL: https://app.podwise.ai/api/ent/v1

The legacy https://podwise.ai/api/ent/v1 entry point remains available temporarily for backward compatibility. New integrations should use https://app.podwise.ai/api/ent/v1.

Open API access for Enterprise customers

The two API families use different endpoint paths and limits:

• Create and manage an API access token in the Enterprise Console or Settings > Developer.
• Use that token with both /api/open/v1 and /api/ent/v1 endpoints.

API access tokens identify the user but do not grant Enterprise access by themselves. Only users with an active Enterprise entitlement can call /api/ent/v1; Pro users can use the same token with Open API but not Enterprise Processing API.

Choose the API based on the resource you are working with: Open API operates on Podwise episodes identified by seq, while Enterprise Processing API operates on private processing jobs identified by your uuid. Access rules, billing, and rate limits are evaluated independently for each API family.

The Enterprise Processing API currently allows 10,000 requests per user per hour, independently of Open API usage. When this limit is reached, requests return HTTP 429 with a Retry-After header.

API sections

• Basics and authorization
• Processing jobs
• Translation
• Downloads
• Webhooks

Change Log

2026-07-28

• Enterprise customers can now use Podwise Open API in addition to Enterprise Processing API.
• API access tokens are shared by Open API and Enterprise Processing API. Enterprise entitlement is still required for /api/ent/v1 requests.
• Added OPEN_API_TRANSCRIBE_DONE and OPEN_API_TRANSCRIBE_ERROR webhook events for episode processing started through Open API.

2025-09-17

• Modified the input parameters of API: Process Episode.
  • Added options.forceRetry to the input parameters.

2025-09-14

• Deprecate episode.podcastDesc parameter in API: Process Episode, use episode.desc instead. If you want to provide more information about the podcast, concatenate it directly in episode.desc.

2025-08-23

• Added API: Translate. Supports translating AI processing results into Simplified Chinese, Traditional Chinese, English, Japanese, and Korean.
• Added API: Get Translation Status.
• Added API: Get Translation Result.
• New request parameter language for API: Download CSV File.
• New request parameter language and mixOriginalLanguage for API: Download SRT File.
• New request parameter language for API: Download Markdown File.
• API: Get Processing History now includes translation request history.
• Webhook Notification now provides callbacks when translation requests succeed or fail.

2025-04-07

• Added API: Download CSV File.
• Added API: Download SRT File.
• Added API: Download Markdown File.
• Modified the output parameters of API: Get Processing Result.
  • Modified the article field to structure the article as a list of chapters, each with a title, time, and list of conversations.

2025-01-03

• Modified the input parameters of API: Process Episode.
  • Added options.generateTitle and options.generateIntro to the input parameters.
  • episode.title is now optional.
• Modified the output parameters of API: Get Processing Result.
  • Added titles and intros to the output parameters. These fields are only returned if the corresponding options are set to true in the API: Process Episode request.

2024-12-28

• Modified the input and output parameters of API: Get Processing History.
  • Removed pageNo and pageSize from the input parameters.
  • Adjusted the fields in the response.
  • Separating the transcription processing records and article generation records into two independent records.
• Modified the input parameters of API: Process Episode.
  • Added keywords to the input parameters.