> For the complete documentation index, see [llms.txt](https://konnadex-docs.gitbook.io/konnadex-technologies/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://konnadex-docs.gitbook.io/konnadex-technologies/authentication.md).

# Authentication

Authenticate your API calls by including your secret key or public key depending on the request you're making in the header of request you make. Generally, we provide both public and secret keys. Public keys are meant to be used from your front-end when integrating Konnadex gateway Inline Checkout and our Frontend libraries. By design, public keys cannot modify any part of your account besides initiating transactions. The secret keys, however, are to be kept secret. If for any reason you believe your secret key has been compromised or you wish to reset it, you can do so from the [dashboard](https://app.konnadex.com/settings) settings.

**`Secure your secret key`**

Do not commit your secret keys to git, or use them in client-side code.

The headers should be in the following format:

`X-api-key: SECRET_KEY​`

**Sample Authorization Headers**

`X-API-key:` pk\_test\_byvpV9uriHnrReNMCGLAZgYpJI1S

API requests made without authentication will fail with the status code `401: Unauthorized`. All API requests must be made over HTTPS.

**Secure your requests**

Do not set `VERIFY_PEER` to `FALSE`. Ensure your server verifies the SSL connection to Konnadex.