Decode XRP Address

This endpoint is used to decode an X-Address into classic address and tag.

Path parameters

network string required

The XRP network to use (mainnet, testnet).

xAddress string required

The X-Address that has to be decoded

Query parameters

context string

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

Returns 200 the request has been successful.

apiVersion string required

Specifies the version of the API that incorporates this endpoint.

E.G. 2026-03-20

requestId string required

Defines the ID of the request. The `requestId` is generated by Vaultody and it's unique for every request.

E.G. 601c1710034ed6d407996b30

context string

E.G. yourExampleString

data object required

item object required

classicAddress string required

The classic XRP Ledger address.

E.G. rB1QL2KsiwrwaErZ8Pa8dVh3ZEQ2oKGp9J

tag string required

A numeric identifier associated with an XRP Ledger address.

E.G. 123

Errors

400 Invalid network! Network MUST be one of: {validNetworks} application/json

401 The provided API key is invalid. Please, generate a new one from your Dashboard. application/json

403 Mainnets access is not available for your current subscription plan, please upgrade your plan to be able to use it. application/json

409 The data provided seems to be invalid. application/json

415 The selected Media Type is unavailable. The Content-Type header should be 'application/json'. application/json

422 Your request body for POST requests must have a structure of { data: { item: [...properties] } } application/json

429 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. application/json

500 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. application/json