> 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/get-your-api-key-or-token.md). # Get your API key or token Copy or reset your API key, or create a named legacy REST API token on the API tab of My account. Use this task to get a credential for the REST API v1. You can use the account API key or create a named personal access token for the REST API. A named token is the safer choice, because you can remove one token and keep the others. ## Before you start * Your plan includes API access: Scale and above, or an older plan that includes it. Without API access, the **API** tab shows an upgrade message instead of the key. * Members of an organization use the API access of the organization owner's plan. {% tabs %} {% tab title="Classic view" %} ### Copy the API key 1. Open the user menu and select **My account**, then open the **API** tab. 2. Read the value in the **API key** field. 3. Copy the key into your integration. ### Reset the API key 1. Open the user menu and select **My account**, then open the **API** tab. 2. Select **Reset API key**. 3. Confirm the prompt **Are you sure you want to reset your key?**. Podigee shows **API key has been reset successfully!** and replaces the key. Every integration that uses the old key no longer works. Update each integration with the new key. ### Create a legacy REST API token 1. Open the user menu and select **My account**, then open the **API** tab. 2. In the **Personal access tokens** section, select **Create legacy REST API token**. 3. Enter a name for the token. 4. Select the scope **Read** or **Read and write**. 5. Confirm. 6. Copy the token from the **Token created** message. Podigee shows the token once, with the note **Copy this token now. You will not be able to see it again.**. Podigee stores only a digest and shows the last four characters in the token list. ### Remove a token 1. Open the user menu and select **My account**, then open the **API** tab. 2. Find the token in the **Personal access tokens** list. 3. Select **Remove**. 4. Confirm the prompt. Podigee shows **Personal access token removed.**. Podigee refuses requests with that token from now on. ### Expected result You hold one credential for the REST API. A legacy REST API token starts with `pdg_pat_`. The token list shows it with the status **Does not expire** and a **Last used** time. The **Last used** time updates at most every 5 minutes. ### If you cannot complete the task * The **API** tab shows an upgrade message: your plan does not include API access. Upgrade to Scale or above, or ask the organization owner to upgrade. * You created a Model Context Protocol (MCP) token instead of a legacy REST API token: the REST API refuses MCP tokens. Create a token with **Create legacy REST API token**. * Your tokens disappeared: Podigee removes all personal access tokens when the subscription is canceled or suspended, or when the trial is expired. Create new tokens after the subscription is active again. ![API tab of My account in the classic view on the Launch plan with the upgrade message, the Upgrade plan button, and the Connector access section](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-f09e19a0dbc05230132c95e68b62cb2af992de05%2Fdoc-integrations-003-classic-upgrade-message.png?alt=media) On a plan without API access, the API tab shows the upgrade message instead of the API key. ### Notes on token lifetime * Legacy REST API tokens do not expire automatically. Remove a token that you no longer use. * A plan change that removes API access does not delete legacy tokens, but the REST API refuses them until the plan includes API access again. * The API key is not the auth token for the WordPress plugin. The settings tab states this with the note **Please note, this API key will not be used for WordPress.** {% endtab %} {% tab title="Podigee workspace" %} The Podigee workspace does not include API keys and tokens yet. Switch to the classic view to get your API key or token. {% endtab %} {% endtabs %} ## Next step [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/get-your-api-key-or-token.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.