Estimate Token Transfer Compute Units Solana
This endpoint estimates the number of compute units an SPL token transfer would consume on Solana. The transfer transaction is built and simulated against the node (without being broadcast) and the simulated compute units consumed are returned. If the recipient does not yet have an associated token account for the given token, the estimate includes the cost of creating it. Supports both the classic Token program and Token-2022 via the tokenStandard field. NFTs on Solana are SPL tokens under the regular Token program, so use "TOKEN" for NFT transfers.
Path Parameters
Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while a network like "devnet" is a test network.
Query Parameters
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
Request Body Schema application/json
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
The quantity of the SPL token to transfer, expressed in the token's raw base units (the on-chain integer value, before the mint's decimals are applied) — not a SOL/lamport amount. String-encoded non-negative integer. Example: for a token with 6 decimals, 1.5 tokens = "1500000".
Base58 string representation of the SPL token mint address (the token's on-chain identifier, equivalent to a token contract address on other chains).
Base58 string representation of the recipient owner pubkey (the wallet receiving the tokens; its associated token account is derived automatically).
Base58 string representation of the sender owner pubkey (the fee payer and source wallet of the tokens).
The SPL token standard the mint belongs to. Allowed values: "TOKEN" (classic Token program) or "TOKEN-2022". NFTs on Solana are regular Token-program SPL tokens, so use "TOKEN" for NFT transfers.
Response Schema
-
200Content-Type: application/json
The request has been successful.
-
400Content-Type: application/json
400
-
401Content-Type: application/json
401
-
402Content-Type: application/json
You have insufficient credits. Please upgrade your plan from your Dashboard or contact our team via email.
-
403Content-Type: application/json
403
-
409Content-Type: application/json
The data provided seems to be invalid.
-
415Content-Type: application/json
The selected Media Type is unavailable. The Content-Type header should be 'application/json'.
-
422Content-Type: application/json
Your request body for POST requests must have a structure of { data: { item: [...properties] } }
-
429Content-Type: application/json
The request limit has been reached. There can be maximum {requests} requests per {seconds} second(s) made. Please contact our team via email if you need more or upgrade your plan.
-
500Content-Type: application/json
An unexpected server error has occurred, we are working to fix this. Please try again later and in case it occurs again please report it to our team via email.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
Amount of the simulated compute units the SPL token transfer would consume. Includes associated-token-account creation cost when the recipient account does not yet exist.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
insufficient_credits
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
invalid_data
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
unsupported_media_type
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
invalid_request_body_structure
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
request_limit_reached
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.
unexpected_server_error
Specifies an error code, e.g. error 404.
Specifies the message of the error, i.e. why the error was returned, e.g. error 404 stands for “not found”.
Specifies an attribute of the error by name.
Specifies the details of an attribute as part from the error.
Credits Cost
| Blockchain protocol | Credits for 1 Results |
| Default Cost | 120 |
| Solana | 120 |
API Key
{
"context": "yourExampleString",
"data": {
"item": {
"amount": "1000000",
"contractAddress": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
"recipient": "9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM",
"sender": "5snoUseZG8s8CDFHrXY2ZHaCrJYsW457piktDmhyb5Jd",
"tokenStandard": "TOKEN"
}
}
}
-
200Content-Type: application/json
The request has been successful.
-
400Content-Type: application/json
400
-
401Content-Type: application/json
401
-
402Content-Type: application/json
You have insufficient credits. Please upgrade your plan from your Dashboard or contact our team via email.
-
403Content-Type: application/json
403
-
409Content-Type: application/json
The data provided seems to be invalid.
-
415Content-Type: application/json
The selected Media Type is unavailable. The Content-Type header should be 'application/json'.
-
422Content-Type: application/json
Your request body for POST requests must have a structure of { data: { item: [...properties] } }
-
429Content-Type: application/json
The request limit has been reached. There can be maximum {requests} requests per {seconds} second(s) made. Please contact our team via email if you need more or upgrade your plan.
-
500Content-Type: application/json
An unexpected server error has occurred, we are working to fix this. Please try again later and in case it occurs again please report it to our team via email.
{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"computeUnits": 4645
}
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "uri_not_found",
"message": "The specified URI has not been found. Check the URI and try again.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "limit_greater_than_allowed",
"message": "You have reached the allowed limit. The maximum number of items for this endpoint is {limit}, please use the specific pagination attributes to get the items in portions.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "invalid_pagination",
"message": "The pagination attributes that have been used are invalid. Please check the Documentation to see details on pagination.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "missing_api_key",
"message": "The specific authorization header (API Key) is missing, please check our Authorization section in our Documentation.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "invalid_api_key",
"message": "The provided API key is invalid. Please, generate a new one from your Dashboard.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "insufficient_credits",
"message": "You have insufficient credits. Please upgrade your plan from your Dashboard or contact our team via email.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "banned_ip_address",
"message": "This IP address has been banned. To check the reason for that, please contact our team via email.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "endpoint_not_allowed_for_plan",
"message": "This endpoint is not available for your current subscription plan, please upgrade your plan to be able to use it.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "endpoint_not_allowed_for_api_key",
"message": "This endpoint is not available for your API key.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "feature_mainnets_not_allowed_for_plan",
"message": "Mainnets access is not available for your current subscription plan, please upgrade your plan to be able to use it.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "invalid_data",
"message": "The data provided seems to be invalid.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "unsupported_media_type",
"message": "The selected Media Type is unavailable. The Content-Type header should be 'application/json'.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "invalid_request_body_structure",
"message": "Your request body for POST requests must have a structure of { data: { item: [...properties] } }",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "request_limit_reached",
"message": "The request limit has been reached. There can be maximum {requests} requests per {seconds} second(s) made. Please contact our team via email if you need more or upgrade your plan.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "unexpected_server_error",
"message": "An unexpected server error has occurred, we are working to fix this. Please try again later and in case it occurs again please report it to our team via email.",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}