> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/integrations/api-key.md). # API Key Learn how to get your API key which you can use to connect Zigpoll to any workflow ### 🔑 How to Create Your Zigpoll API Key 1. Log in to your Zigpoll dashboard. 2. Go to **Integrations** in the account sidebar and open the **API Keys** card (under **API Keys & Webhooks**). 3. Click **New API Key**, enter an **API Key Label** (for example "Zapier"), and click **Create API Key**. 4. Copy the key. Paste the key into the tool you're connecting, such as Zapier, Make, or n8n. {% hint style="info" %} **A key belongs to your login, not to one account.** It can reach every Zigpoll account your login has access to. If you manage several stores, sign in as the user who belongs to the account you want to connect before you create the key. To remove a key, click **Delete** next to it. {% endhint %} ### Using your key Send it in the `Authorization` header on requests to `https://v1.zigpoll.com`. See the [API reference](/web-api.md) for endpoints. ### Requirements and permissions * **Plan**: direct API access requires a **Premium** plan or higher. On other plans, requests return `403` with *"This account's plan does not include API access. Please upgrade to the Premium plan or higher."* Tools built on the API, such as Zapier, Make, n8n, and MCP, need the same plan. * **Role**: your key carries your team role. **Read only** keys can't make writes, and **Editor** keys can't manage webhooks or integrations. Those endpoints need a key from an **Owner**, **Admin**, or **Billing Admin**. See [Adding Team Members](/tutorials/adding-team-members.md) for role details. --- # 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.zigpoll.com/integrations/api-key.md?ask=&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.