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.

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.

Secure your secret key

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

Authorization headers should be in the following format:

Authorization: Bearer SECRET_KEY

Sample Authorization Header Authorization: Bearer sk_test_UkqerSTELjYhf6GNe6lB

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 Lahza.