Authentication
Authenticate your API calls by including your secret key in the Authorization header of every request you make. You can manage your API keys from the dashboard. Generally, we provide both public and secret keys. Public keys are meant to be used from your front-end when integrating using BudPay Inline and in our Mobile SDKs only. By design, public keys cannot modify any part of your account besides initiating transactions to you. 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
Authorization: Bearer sk_test_vhrg8erguv8fc990efe90df0e0fv
Sample Authorization Header
Authorization: Bearer sk_test_vhrg8erguv8fc990efe90df0e0fv
API requests made without authentication will fail with the status code 401: Unauthorized. All API requests must be made over HTTPS.
Do not set VERIFY_PEER to FALSE. Ensure your server verifies the SSL connection to BudPay.
Secure your requests
Do not set VERIFY_PEER to FALSE. Ensure your server verifies the SSL connection to BudPay.