Signature Examples

Now, let's build a couple signatures for your requests. For demonstrational purposes, we'll be using constant values for private-key and timeframe.

Parameter

Value

Basic Crypto Operations

POST /merchants/addresses

Whole body of the request should also be included in the MESSAGE as payload.

Request: POST/merchants/addresses

Body: {"blockchain":"BITCOIN", "meta":"your-info"}

Message: POST/merchants/addresses{"blockchain":"BITCOIN", "meta":"your-info"}1677486443

Signature: d1aeccfe32e4adf499be5777f38cd643a2a2c06a929f1f328d9809b9f8f8509e

POST /merchants/rotating-addresses

Whole body of the request should also be included in the MESSAGE as payload.

Request: POST/merchants/rotating-addresses

Body: POST/merchants/rotating-addresses{"blockchain":"BITCOIN", "meta":"your-info", "duration":"123145513"}

Message: POST/merchants/rotating-addresses{"blockchain":"BITCOIN", "meta":"your-info", "duration":"123145513"}1677486443

Signature: 2b3cb49ec7e03f7b53df43aea92977ef22d2ed5e8fff4ecd0696bf3906c070ea

POST /merchants/withdrawals/crypto

Whole body of the request should also be included in the MESSAGE as payload.

Request: POST/merchants/withdrawals/crypto

Body: {"ticker":"USDT", "blockchain":"TRON", "to":"THPvaUhoh2Qn2y9THCZML3H815hhFhn5YCw", "amount":"12.000", "meta":"your-info"}

Message: POST/merchants/withdrawals/crypto{"ticker":"USDT", "blockchain":"TRON", "to":"THPvaUhoh2Qn2y9THCZML3H815hhFhn5YCw", "amount":"12.000", "meta":"your-info"}1677486443

Signature: 47e1044d1116fae66dafa5af595170b7b2a63d5c169e8c030a0787b6b8095a23

GET /withdrawals/crypto/fee?ticker=USDT&amount=12.00&blockchain=TRON

Since this request sends parameters via query, they have to be included in the final MESSAGE.

Request: GET/withdrawals/crypto/fee

Query: ?ticker=USDT&amount=12.00&blockchain=TRON

Message: GET/merchants/withdrawals/crypto/fee?ticker=USDT&amount=12.00&blockchain=TRON1677486443

Signature: 80024504f409906c1bc9359bb943847eed0c9f8f5bfe83b9b5f5c8155e44e404

GET /merchants/assets/crypto

Since there're no parameters, MESSAGE will look like this:

Request: GET/merchants/assets/crypto

Message: GET/merchants/assets/crypto1677486443

Signature: a6351a236ac09284b9c31c1037a1b75541c2ca98b6ad2680f26bb4bb93c25751

Crypto Invoices

POST /merchants/invoices/crypto

Whole body of the request should also be included in the MESSAGE as payload.

Request: POST/merchants/invoices/crypto

Body: {"name":"Order #123123-412d-asdw", "amount":{"value":"125", "ticker":"USDT", "blockchain":"TRON"}, "meta":"your-info"}

Message: POST/merchants/invoices/crypto{"name":"Order #123123-412d-asdw", "amount":{"value":"125", "ticker":"USDT", "blockchain":"TRON"}, "meta":"your-info"}1677486443

Signature: f81f47f01e162a0fe0344e7b3f8ab874004984e440893728657e4e0ae1509ca4

GET /merchants/invoices/crypto/:id

Parameter id is included in URL path, and thus will be included into MESSAGE as payload. Let's pretend that id is "1234455-asdfafg-asdaweqw"

Request: GET/merchants/invoices/crypto/1234455-asdfafg-asdaweqw

Message: GET/merchants/invoices/crypto/1234455-asdfafg-asdaweqw1677486443

Signature: 6a27ef229d9be45a0a45914198ed042abd0fe9293db4b0de1ef322e50a7f5e8f