Quickstart

This quickstart shows the typical Cyrafa integration flow from credentials to the first API call.

Integration flow

Get API credentials from the Cyrafa team.
Sign requests with your API secret.
Fetch wallets to identify the wallet you want to use.
Create a checkout link or submit a withdrawal.
Handle the API response and persist the identifiers you need.

First request

Cyrafa signs requests using a canonical payload built from:


<timestamp>.<body>

For GET requests or any request without a body, the body portion is an empty string. That means the payload for a wallet-list request is effectively:


<timestamp>.


curl -X GET "https://<HOST>/api/v1/cp/wallets/?page=1&limit=20" \
  -H "api-key: <YOUR_API_KEY>" \
  -H "timestamp: 1712668800" \
  -H "signature: <HMAC_SIGNATURE>"

What happens next

Use the wallet response to capture walletId, assetId, and available networks.
Use that wallet in a withdrawal request or alongside merchant settings for checkout.
Persist returned transaction and checkout identifiers in your system.

Troubleshooting

Confirm your server clock is accurate before signing requests.
Use compact JSON with no extra whitespace for any signed request body.
Sign the exact body you send on the wire.
If a GET request fails authentication, verify that you signed an empty string body instead of omitting the body segment entirely.