> For the complete documentation index, see [llms.txt](https://docs.atomyx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atomyx.io/atomyx-submit/implementation/api-integration/authentication.md). # Authentication The Submit API uses bearer token authentication. Each request made to the Submit API must include an API key in the `Authorization` header. ```http Authorization: Bearer YOUR_API_KEY ``` API keys are issued and managed through Atomyx Vault. If you need access to the Submit API, your organisation must have the appropriate Vault access and an API key with permission to use Submit. ### Example request header ```http POST /jobs HTTP/1.1 Host: submit.atomyx.io Authorization: Bearer YOUR_API_KEY Content-Type: application/json ``` ### API key handling Treat API keys as sensitive credentials. Do not: * place API keys in public code repositories * expose API keys in frontend browser code * include API keys in screenshots or shared logs * hard-code production API keys in shared test tools * include API keys inside callback payloads Use secure environment variables, secret stores, or server-side configuration. ### Missing or invalid credentials If the API key is missing, invalid, expired, or not allowed for the selected environment, the API returns: ```http 401 Unauthorized ``` Check that: * the `Authorization` header is present * the value starts with `Bearer` * the API key is correct * the API key belongs to the environment being used * the API key has permission to create Submit jobs ### Callback authentication Outbound callbacks from Atomyx Submit are authenticated separately using HMAC signatures. Do not use Submit API keys as callback payload fields. See **Callbacks and Status Updates** for the callback authentication model. --- # 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: ``` GET https://docs.atomyx.io/atomyx-submit/implementation/api-integration/authentication.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.