Back to Details

podcast-api

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Podcast API

Podcast API

Use the Listen Notes Podcast API without guessing endpoints, exposing credentials, or treating mock data as real data.
无需猜测端点、暴露凭证或将模拟数据视为真实数据，即可使用Listen Notes Podcast API。

Sources Of Truth

权威来源

Do not copy a remembered schema into an implementation. Verify the relevant OpenAPI operation when network access is available. If it is unavailable, use the bundled endpoint map, state the limitation, and avoid inventing fields.
不要将记忆中的模式复制到实现中。当有网络访问时，请验证相关的OpenAPI操作。如果无法访问网络，请使用捆绑的端点映射，说明限制，切勿自行创建字段。

Workflow

工作流

  1. Inspect the target repository before changing it.
    • Identify the language, framework, server-side boundary, HTTP client, environment-variable convention, and test setup.
    • Reuse an installed official SDK or the project's existing HTTP client. Otherwise prefer the language's native HTTP facilities instead of adding a dependency.
  2. Select the operation.
    • Read endpoint-selection.md.
    • Load only the use-case reference relevant to the request.
    • Confirm the operation in the live OpenAPI document, including plan restrictions and pagination fields.
  3. Design the security boundary.
    • Read 
      LISTEN_API_KEY
      only in server-side code or a serverless function.
    • Send it as 
      X-ListenAPI-Key
      to the production API.
    • Never place it in browser or mobile bundles, public environment variables, source control, URLs, fixtures, logs, or error messages.
    • If the current architecture cannot protect the key, add a server-side proxy before integrating the API.
  4. Implement in the project's style.
    • Keep the production base URL configurable and default it to 
      https://listen-api.listennotes.com/api/v2
      .
    • Encode query parameters and request bodies with structured APIs.
    • Validate inputs at the application's boundary and handle non-2xx responses explicitly.
    • Follow integration-rules.md for pagination, usage headers, caching, attribution, and error handling.
  5. Test without spending quota.
    • Follow testing.md.
    • Use 
      https://listen-api-test.listennotes.com/api/v2
      without an API key only for HTTP transport and response-shape tests.
    • Use local mocks or fixtures for parameter behavior, error paths, and pagination logic.
  6. Verify the result.
    • Confirm no secret crosses a client boundary or appears in generated output.
    • Confirm the selected endpoint and every field used still exist in OpenAPI.
    • Confirm pagination terminates and does not issue unbounded requests.
    • Confirm UI using API data satisfies the applicable attribution rules.
Do not make a production request unless the user explicitly asks and has arranged a credential. Never print or inspect the credential value.
  1. 在修改目标仓库前先检查它。
    • 确定语言、框架、服务器端边界、HTTP客户端、环境变量约定和测试设置。
    • 复用已安装的官方SDK或项目现有的HTTP客户端。否则优先使用语言原生的HTTP工具，而非添加新依赖。
  2. 选择操作。
    • 阅读endpoint-selection.md。
    • 仅加载与请求相关的用例参考。
    • 在实时OpenAPI文档中确认操作，包括方案限制和分页字段。
  3. 设计安全边界。
    • 仅在服务器端代码或无服务器函数中读取
      LISTEN_API_KEY
      。
    • 将其作为
      X-ListenAPI-Key
      发送至生产API。
    • 切勿将其放置在浏览器或移动包、公共环境变量、版本控制、URL、测试数据、日志或错误消息中。
    • 如果当前架构无法保护密钥，请在集成API前添加服务器端代理。
  4. 按照项目风格实现。
    • 保持生产环境基础URL可配置，默认值设为
      https://listen-api.listennotes.com/api/v2
      。
    • 使用结构化API对查询参数和请求体进行编码。
    • 在应用边界验证输入，并显式处理非2xx响应。
    • 遵循integration-rules.md处理分页、使用头信息、缓存、归因和错误处理。
  5. 无需消耗配额进行测试。
    • 遵循testing.md。
    • 使用
      https://listen-api-test.listennotes.com/api/v2
      （无需API密钥）仅用于HTTP传输和响应格式测试。
    • 使用本地模拟或测试数据测试参数行为、错误路径和分页逻辑。
  6. 验证结果。
    • 确认没有密钥跨越客户端边界或出现在生成的输出中。
    • 确认所选端点和使用的每个字段仍存在于OpenAPI中。
    • 确认分页会终止，不会发出无限请求。
    • 确认使用API数据的UI符合适用的归因规则。
除非用户明确要求并已安排好凭证，否则不要发送生产请求。切勿打印或查看凭证值。

Reference Routing

参考路由

  • Endpoint choice and current API surface: endpoint-selection.md
  • Authentication, errors, pagination, caching, and attribution: integration-rules.md
  • Mock server and test strategy: testing.md
  • Search, typeahead, genres, charts, and discovery: search-and-discovery.md
  • Podcast lookup, episode sync, subscriptions, OPML, and webhooks: library-and-sync.md
  • Playlists, curation, audio, embeds, and transcripts: playlists-and-media.md
  • API keys, usage monitoring, and account operations: account-and-usage.md
  • Product, policy, support, rate-limit, and data questions: api-faq.md
  • Plans, quotas, charges, cancellation, and payments: billing-faq.md
  • 端点选择和当前API范围：endpoint-selection.md
  • 身份验证、错误、分页、缓存和归因：integration-rules.md
  • 模拟服务器和测试策略：testing.md
  • 搜索、预输入、分类、排行榜和发现：search-and-discovery.md
  • 播客查找、剧集同步、订阅、OPML和Webhooks：library-and-sync.md
  • 播放列表、策展、音频、嵌入和转录文本：playlists-and-media.md
  • API密钥、使用情况监控和账户操作：account-and-usage.md
  • 产品、政策、支持、速率限制和数据相关问题：api-faq.md
  • 方案、配额、费用、取消和支付：billing-faq.md

Answering Questions

问题解答

Answer stable technical behavior from the appropriate reference and link to the live source. Re-check the live page before quoting a price, quota, plan entitlement, rate limit, support commitment, or legal/policy requirement. Distinguish API behavior from business policy, and direct account-specific billing issues to 
hello@listennotes.com
.
从相应参考中回答稳定的技术行为，并链接到实时来源。在引用价格、配额、方案权益、速率限制、支持承诺或法律/政策要求前，请重新检查实时页面。区分API行为与业务政策，将账户特定的计费问题转至
hello@listennotes.com
。