Encode XRP Address
This endpoint encodes XRP classic address into an X-Address when classic address and a tag are provided.
Path Parameters
The numeric tag used for the encoding.
The classic address that will be encoded.
The XRP network to use (mainnet, testnet).
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.
Response Schema
-
200Content-Type: application/json
The request has been successful.
-
400Content-Type: application/json
Invalid network! Network MUST be one of: {validNetworks}
-
401Content-Type: application/json
The provided API key is invalid. Please, generate a new one from your Dashboard.
-
403Content-Type: application/json
Mainnets access is not available for your current subscription plan, please upgrade your plan to be able to use it.
-
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 Vaultody 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.
The X-address format that encodes the classic address.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Vaultody 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 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 Vaultody 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 Vaultody 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 Vaultody 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 Vaultody 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 Vaultody 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 Vaultody 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 Vaultody 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 : 0 Credits for 1 Results
cb233681a8ee35665296c1824c1f67bc46691788
PSqeqRLap8rBc/wogNU1DeGGUPb2VyVtg6GiBOaBnYQ=
1681885776
zYgKeueoOq
-
200Content-Type: application/json
The request has been successful.
-
400Content-Type: application/json
Invalid network! Network MUST be one of: {validNetworks}
-
401Content-Type: application/json
The provided API key is invalid. Please, generate a new one from your Dashboard.
-
403Content-Type: application/json
Mainnets access is not available for your current subscription plan, please upgrade your plan to be able to use it.
-
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": "2026-03-20",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"xAddress": "T7zVRFzUcVxFfE3MUM6jV3SpobVdECBZ1K9UnX62Jacc6AV"
}
}
}{
"apiVersion": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "invalid_blockchain",
"message": "Invalid blockchain! Blockchain MUST be one of: {validBlockchains}",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2026-03-20",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"error": {
"code": "invalid_network",
"message": "Invalid network! Network MUST be one of: {validNetworks}",
"details": [
{
"attribute": "attribute which content caused the error",
"message": "message describing the error"
}
]
}
}{
"apiVersion": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"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": "2026-03-20",
"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"
}
]
}
}