> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/connect-and-administer/integrations/connect-podigee-with-other-tools.md). # Connect Podigee with other tools Understand the connection paths between Podigee and external software and pick the right one. Podigee offers several ways to exchange data with software outside the web app. Each path serves a different job. This page helps you pick the correct one before you set anything up. ## How it works | Path | Who uses it | What it does | | ----------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | REST API v1 | Your own scripts and systems | Reads and changes podcasts, episodes, media, listeners, and analytics with an API credential | | Authorized applications | Partner applications | Hold access to your account after you grant it with your Podigee sign-in | | WordPress Quick Publish | Your WordPress site | Connects the plugin to a podcast with an auth token | | Embed endpoints | Websites and social platforms | Return a player for an episode URL without any sign-in | | AI agents | Model Context Protocol (MCP) connectors and the `pdg` command-line interface (CLI) | Let an agent work with your account through a separate, scoped connection | ### REST API v1 The REST API v1 is available at `https://app.podigee.com/api/v1`. All requests and responses use JSON. You authenticate with your account API key or with a personal access token that you create for the REST API. The API is available on Scale and above, or on an older plan that includes it. The [REST API](/documentation/connect-and-administer/integrations/rest-api.md) collection documents the endpoints. ### Authorized applications Some partner applications, for example recording or editing tools, use OAuth 2.0 to work with your account. Podigee registers these applications. There is no self-service registration for developers. When you sign in to such an application, Podigee asks you to grant access. You can see and revoke every granted application: open the user menu and select **My account**, then open the **Applications** tab. ### WordPress Quick Publish The **Podigee Wordpress Quick Publish** plugin connects a WordPress site to one podcast with an auth token from your settings. The plugin authorizes itself with that token and with the subdomain of the podcast. ### Embed endpoints A website or a social platform can request a player for an episode URL from a public oEmbed endpoint (oEmbed is the open standard to embed content from a URL). This endpoint needs no sign-in and sets no cookies. The embed codes and the oEmbed details belong to the publishing pages of this documentation. ### AI agents MCP connectors, the `pdg` CLI, and the agent skill use a separate authorization model with scoped permissions. They do not use the REST API credentials on this page. Start with [Choose how to use Podigee for AI agents](/documentation/start-here/ai-agents/start-here/choose-how-to-use-podigee-for-ai-agents.md). ## Important decisions * Podigee sends no outbound webhooks. Your system must poll the REST API to detect changes. * A personal access token for the REST API can be read-only. Use a read-only token when your integration does not change data. * An MCP token or an MCP connector credential does not work on the REST API. Create a separate legacy REST API token for REST integrations. * The WordPress auth token is not the API key. Podigee shows the two credentials on different settings tabs, and they serve different integrations. ## Related tasks * [Get your API key or token](/documentation/connect-and-administer/integrations/get-your-api-key-or-token.md) * [Manage authorized applications](/documentation/connect-and-administer/integrations/manage-authorized-applications.md) * [Connect the WordPress Quick Publish plugin](/documentation/connect-and-administer/integrations/connect-the-wordpress-quick-publish-plugin.md) * [Make your first API request](/documentation/connect-and-administer/integrations/rest-api/make-your-first-api-request.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podigee.com/documentation/connect-and-administer/integrations/connect-podigee-with-other-tools.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.