The Blockdaemon Tokenization API provides access to various blockchain networks and their associated services. Follow the steps below to start using the API for free today.
Step 1. Sign Up for an API Key
To use the Blockdaemon Tokenization API, you must sign up for an API key. To do this, visit the Blockdaemon website and create an account. Once you have an account, you can access your API key from the dashboard.
Get Your Free API Key!
Enjoy Rapid and Scalable Multichain Access!
Step 2. Get Familiar with API Endpoints
Explore the Blockdaemon Tokenization API's endpoints to interact with tokenized assets. Check out the Tokenization API Overview and the list of Supported Protocols and Networks.
Step 3. Authenticate Your API Requests
Authenticate your requests using one of the following methods:
3.1. Query Parameter
Add your API key as a query parameter:
https://svc.blockdaemon.com/tokens/v1/{protocol}/{network}/{token_addr}/check_transfer_restriction?apiKey=YOUR_API_KEY
Authentication with a query parameter can be used with any tool - no additional actions are needed.
Info:
Note that if the query has additional parameters, replace
?
with&
.
3.2. Bearer Token
Include your API key as a bearer token in the authorization header:
curl --request POST 'https://svc.blockdaemon.com/tokens/v1/{protocol}/{network}/{token_addr}/check_transfer_restriction' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY'
Or, if you prefer to use short options, run the following:
curl -X POST 'https://svc.blockdaemon.com/tokens/v1/{protocol}/{network}/{token_addr}/check_transfer_restriction' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR_API_KEY'
3.3. Using Your API Key as an X-API-Key
For example, to check transfer restrictions using our Tokenization API, use the following code:
curl --request POST 'https://svc.blockdaemon.com/tokens/v1/{protocol}/{network}/{token_addr}/check_transfer_restriction' \
--header 'Content-Type: application/json' \
--header 'X-API-Key: YOUR_API_KEY'
Or, if you prefer to use short options, run the following:
curl -X POST 'https://svc.blockdaemon.com/tokens/v1/{protocol}/{network}/{token_addr}/check_transfer_restriction' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY'
Step 4. Test the API
Request Example
The example below shows a request example to check transfer restrictions. If your API key is correct, your request will be authorized.
curl --request POST \
--url https://svc.blockdaemon.com/tokens/v1/ethereum/mainnet/0xF6c5e53DD4dB0cAaC2B08596E96A98ffA7cA8faC/check_transfer_restriction \
--header 'X-API-Key: 2go1YqUcuAr4WZ2-3WgSD3c7qpatZqQuNWhTVBldKZnTSUtw' \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '
{
"from": "0x1f9090aaE28b8a3dCeaDf281B0F12828e676c326",
"to": "0x301407427168FB51bcc927b9FB76DCd88Fe45681"
}'
Response Example
It returns the transfer restriction result, which could be "No Restriction" or "Existing Restriction" for each token (ERC-1404/ERC-3643).
/** No Restriction for ERC-3643 **/
{
"standard": "ERC-3643",
"can_transfer": true,
"restriction_code": null,
"restriction_message": null
}
If the key is incorrect or missing, you will get this error:
{
"type": "https://httpproblems.com/http-status/401",
"title": "Unauthorized",
"status": 401,
"detail": "Authorization Failed",
"instance": "/tokens/v1/ethereum/sepolia/0xE1Aa8d091aF596D8EbC64b5beCd4114e7875E89c/check_transfer_restriction",
"trace": {
"timestamp": "2024-11-18T19:32:56.506Z",
"requestId": "394c9bf9-ab42-45c1-9298-81c2f66545d7",
"buildId": "b4b25a01-230b-4075-8709-2d128d33bc28",
"rayId": "8e4a63a93fc5aefc"
}
}
If the request is invalid, you will get this error:
{
"type": "bad-request",
"code": 16397,
"title": "Bad Request",
"status": 400,
"detail": "recipient address '0x30147427168FB51bcc927b9FB76DCd88Fe45681' is not valid"
}
👋 Need Help?
Contact us through email or our support page for any issues, bugs, or assistance you may need.