> For the complete documentation index, see [llms.txt](https://docs.samesystem.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samesystem.dev/getting-started/api-access.md). # API Access Access to the SameSystem APIs requires a dedicated API user and open up your client for API access. API access is not enabled automatically. To request an API user, please contact either: * Your **SameSystem Customer Success Manager (CSM)** * The **SameSystem Integration Team** at [**integrations@samesystem.com**](mailto:integrations@samesystem.com) ### Requesting an API User When requesting API access, SameSystem will provide an **API User Request Form**. The form must be completed with information about your integration and the required API access. This helps us understand the intended use case and ensure that the API user is configured with the appropriate access. Once the completed form has been reviewed, the Integration Team will create the API user and provide the necessary credentials. ### API Credentials Once API access has been set up, you will receive the credentials required to authenticate against the relevant SameSystem API. API credentials must be treated as sensitive information and stored securely. We recommend following these best practices: * Store credentials in a dedicated secrets manager or ID vault, such as Azure Key Vault, AWS Secrets Manager, or an equivalent solution. * Never store credentials directly in source code, configuration files committed to version control, scripts, or documentation. * Avoid exposing credentials in logs, monitoring tools, error messages, or support tickets. * Restrict access to credentials according to the principle of least privilege. * Use separate credentials for separate systems or environments where possible. * Do not share API credentials between individual users or unrelated integrations. * Only transmit credentials over secure, encrypted connections. --- # 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.samesystem.dev/getting-started/api-access.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.