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

# Authentication

To ensure proper authentication of your API calls, make sure to include your secret key in the Authorization header of each request you send. You can manage your API keys directly from the [dashboard](https://dashboard.lahza.io).

In our integration, we provide both public and secret keys. Public keys are intended for use on the front-end when integrating with Lahza Inline and in our Mobile SDKs exclusively. Public keys have limitations and cannot modify any aspect of your account, except for initiating transactions towards your account. On the other hand, secret keys are intended to be kept confidential. If you suspect that your secret key has been compromised or if you wish to reset it for any reason, you can easily do so from the dashboard.<br>

{% hint style="danger" %}
**Secure your secret key**

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

Authorization headers should be in the following format:

&#x20;`Authorization: Bearer SECRET_KEY`

{% hint style="info" %}
**Sample Authorization Header**\
Authorization: Bearer sk\_test\_UkqerSTELjYhf6GNe6lB
{% endhint %}

API requests made without authentication will fail with the status code&#x20;

`401: Unauthorized`. All API requests must be made over HTTPS.<br>

{% hint style="danger" %}
**Secure your requests**\
Do not set `VERIFY_PEER` to `FALSE`. Ensure your server verifies the SSL connection to Lahza.
{% endhint %}

<br>