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 Lazerpay 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 them, you can 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 X-api-key: PUBLIC_KEY

Sample Authorization Headers

Authorization: Bearer sk_test_mvfZP5sUQQz7WJ5iEe6Av 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 Lazerpay.

Last updated