> 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.md).

# Integrations

Connect Podigee with your own software, partner applications, WordPress, and AI agents.

Use this section to connect Podigee with software outside the Podigee web app. It covers the credentials you need, the applications that can hold access to your account, the WordPress Quick Publish plugin, and it points to the REST API v1 reference.

## Start with the overview

* [Connect Podigee with other tools](https://docs.podigee.com/documentation/connect-and-administer/integrations/connect-podigee-with-other-tools.md) explains which connection paths exist and which one fits your job.

## Set up access

* [Get your API key or token](https://docs.podigee.com/documentation/connect-and-administer/integrations/get-your-api-key-or-token.md)
* [Manage authorized applications](https://docs.podigee.com/documentation/connect-and-administer/integrations/manage-authorized-applications.md)
* [Connect the WordPress Quick Publish plugin](https://docs.podigee.com/documentation/connect-and-administer/integrations/connect-the-wordpress-quick-publish-plugin.md)

## Use the REST API

The [REST API](https://docs.podigee.com/api-reference/rest-api) section of the API Reference starts with a first request and then lists every endpoint group. The groups are authentication and errors, podcasts and episodes, media uploads and encoding, episode content, listeners, analytics, and account.

## AI agents

Agent connections through Model Context Protocol (MCP) connectors have their own section: [AI Agents and MCP](https://docs.podigee.com/documentation/start-here/ai-agents.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.podigee.com/documentation/connect-and-administer/integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
