> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/developer/api.md). # API Programmatic access to read and write data in Pylon Pylon’s API can be used to programmatically access and take action on data within Pylon. Only Admin users can create API tokens. To learn more about Admins, see [Roles & User Management](/pylon-docs/platform/roles-and-user-management.md). Some common use cases for our API include: * Fetching information about customers * Fetching information about issues * Creating issues programmatically Check out our [API Reference](/pylon-docs/developer/api/api-reference.md) for specifications on all endpoints. To call the API from TypeScript, Python, or Go, use our [SDKs](/pylon-docs/developer/api/sdks.md). Before you build an integration, read: * [Authentication](/pylon-docs/developer/api/authentication.md) for creating tokens, roles, and regions * [API conventions](/pylon-docs/developer/api/conventions.md) for IDs, timestamps, pagination, search filters, update behavior, files, and slugs * [Rate limits](/pylon-docs/developer/api/rate-limits.md) for request limits and how to handle `429` responses * [Errors](/pylon-docs/developer/api/errors.md) for error codes and response format --- # 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.usepylon.com/pylon-docs/developer/api.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.