Get started with the CryptoSwift API

Every call to the CryptoSwift API must include an API secret key. After your CryptoSwift account is created, we generate two API keys for your CryptoSwift organisation – one for test, and one for production environment.

If you haven't joined CryptoSwift, reach out to our team to get your API keys.

CryptoSwift authenticates all your API requests using your account's API keys. CryptoSwift raises a 401 Unauthorized error if you don’t include a key or if the key is incorrect or outdated.

As mentioned above, all API requests that require authentiation need to include the API secret key. The key has to be put in a custom header called x-api-key.

All CryptoSwift API requests occur in either test or live environments, objects and API keys in one environment aren't accessible to the other.

curl --location --request GET 'https://api.cryptoswift.eu/transactions/' \
--header 'x-api-key: a70fcedf-416b-4f83-845c-a05aba0d7da4' 

The example below returns the latest 100 transactions for the organisation associated with the given API key.

Use this checklist to decide what to implement next once your first request succeeds.

• Explore full payloads in Send and receive data examples.
• Keep the Travel Rule recipes open as a companion playbook.

• Register webhooks and secure them with webhook signatures for real-time updates.
• Align business stakeholders with the Workflows & concepts track so everyone understands the operational picture.

• Embed or redirect to the wallet verification widget.
• Orchestrate ownership checks in your own app through the wallet verification API.

• Keep the Travel Rule data model handy for field definitions.
• Consult the API reference whenever you need endpoint details.

• Travel Rule recipes
• Send and receive data examples
• Webhooks