Authentication
How to authenticate yourself with CKBull Signer API
To be able to generate sign in requests and transaction requests your dApp must use the API keys provided in CKBull Developer Console after registering it.
CKBull Signer API is meant to be called from a server. Don't make calls from your dApp frontend; always use your own dApp backend.
You will need:
API Key.
API Secret.
CKBull Signer API uses the HMAC-SHA512 algorithm to validate the dApp in every call to generate sign in and transaction requests. The following HTTP headers need to be passed to authenticate the dApp:
x-timestamp: A timestamp generated when making the call.
x-api-key: The dApp API key provided in CKBull Developer Console.
x-signature: The signature hash obtained using the timestamp and your dApp API secret.
Here you can find the code to generate the required headers.
Last updated