> 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/rest-api/make-your-first-api-request.md). # Make your first API request List your podcasts with one authenticated request and open the interactive API docs. Use this tutorial to make a successful request to the REST API v1. It uses the podcast list endpoint, which needs only a credential and returns the podcasts that your account can see. ## What you will complete At the end of this tutorial, you have a JSON list of your podcasts on your screen. You also know where to find the other endpoints. ## Before you start * Your plan includes API access: Scale and above, or an older plan that includes it. * You have an API key or a legacy REST API token from the **API** tab of **My account**. See [Get your API key or token](/documentation/connect-and-administer/integrations/get-your-api-key-or-token.md). * You have `curl` or another HTTP client on your computer. ## Follow the tutorial ### 1. Send the request 1. Replace `mytoken` with your API key or your legacy REST API token. 2. Run this command: ```bash curl -H "Token: mytoken" https://app.podigee.com/api/v1/podcasts ``` Expected result: the response is a JSON list. Each entry is one podcast with its `id`, `title`, and the other podcast fields. ### 2. Limit the returned fields 1. Add the `fields_filter[]` parameter with one field name for each field that you need. 2. Run this command: ```bash curl -H "Token: mytoken" "https://app.podigee.com/api/v1/podcasts?fields_filter[]=subdomain" ``` Expected result: each entry contains `id`, `title`, and `subdomain`. The API always includes `id` and `title`, even when the filter does not name them. ### 3. Open the interactive API docs 1. Open `https://app.podigee.com/api-docs` in your browser. 2. Find the `podcasts` tag and expand `GET /podcasts`. 3. Compare the response schema with the JSON from step 1. Expected result: the page lists every published endpoint with its parameters and response schema. When you are signed in to Podigee, the page pre-fills your API key, so you can try requests in the browser. The machine-readable specification is at `https://app.podigee.com/api/v1/docs`. ## Check your result The response from step 1 contains at least one podcast with the same `title` that you see in the Podigee web app. The list includes the podcasts that you own, the podcasts that you edit as a collaborator, and the visible podcasts of your organization. ## If the result is different * The response is `{"code": 401, "message": "You are not authorized to access this area.", ...}`: the credential is wrong, your plan does not include API access, or the subscription is suspended. Check the `reason` field and see [REST API authentication and errors](/documentation/connect-and-administer/integrations/rest-api/rest-api-authentication-and-errors.md). * The response is `401` although the credential is correct: the credential is possibly a Model Context Protocol (MCP) token or an MCP connector credential. An MCP connector credential answers with the message `This MCP credential is not valid for the legacy API.`. The API refuses an MCP token as unknown. Create a legacy REST API token instead. * The response is `429`: you sent too many requests in one minute. Wait for the number of seconds in the `Retry-After` header and send the request again. ## Next step [REST API podcasts and episodes](/documentation/connect-and-administer/integrations/rest-api/rest-api-podcasts-and-episodes.md) lists the parameters of the podcast and episode endpoints. --- # 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/rest-api/make-your-first-api-request.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.