Get desktop application:
View/edit binary Protocol Buffers messages
RPCs available to interact with the XRP Ledger. The gRPC API mimics the JSON API. Refer to xrpl.org for documentation
Get account info for an account on the XRP Ledger.
A request to get info about an account. Next field: 6
The address to get info about.
Which ledger to use to retrieve data. If this field is not set, the server will use the open ledger. The open ledger includes data that is not validated or final. To retrieve the most up to date and validated data, use SHORTCUT_VALIDATED
Response to GetAccountInfo RPC Next field: 6
Get all validated transactions associated with a given account
Next field: 8
What ledger to include results from. Specifying a not yet validated ledger results in an error. Not specifying a ledger uses the entire range of validated ledgers available to the server. Note, this parameter acts as a filter, and can only reduce the number of results. Specifying a single ledger will return only transactions from that ledger. This includes specifying a ledger with a Shortcut. For example, specifying SHORTCUT_VALIDATED will result in only transactions that were part of the most recently validated ledger being returned. Specifying a range of ledgers results in only transactions that were included in a ledger within the specified range being returned.
Return results as binary blobs. Defaults to false.
If set to true, returns values indexed by older ledger first. Default to false.
Limit the number of results. Server may choose a lower limit. If this value is 0, the limit is ignored and the number of results returned is determined by the server
Marker to resume where previous request left off Used for pagination
Next field: 8
Get the fee for a transaction on the XRP Ledger.
A request for the current transaction fee on the ledger. Next field: 1
Response to a GetFee RPC Next field: 8
Get a specific ledger, optionally including transactions and any modified, added or deleted ledger objects
If true, include transactions contained in this ledger
If true and transactions, include full transactions and metadata If false and transactions, include only transaction hashes
If true, include state map difference between this ledger and the previous ledger. This includes all added, modified or deleted ledger objects
If the request needs to be forwarded from a reporting node to a p2p node, the reporting node will set this field. Clients should not set this field.
Identifying string. If user is set, client_ip is not set, and request is coming from a secure_gateway host, then the client is not subject to resource controls
For every object in the diff, get the object's predecessor and successor in the state map. Only used if get_objects is also true.
Just the hashes
Full transactions and metadata
True if the ledger has been validated
State map difference between this ledger and the previous ledger
True if the skiplist object is included in ledger_objects
True if request was exempt from resource controls
True if the response contains the state map diff
True if the response contains key of objects adjacent to objects in state map diff
Successor information for book directories modified as part of this ledger
Iterate through all ledger objects in a specific ledger
Get ledger objects for a specific ledger. You can iterate through several calls to retrieve the entire contents of a single ledger version.
If set, only objects with a key greater than marker are returned. This can be used to pick up where a previous call left off. Set marker to the value of marker in the previous response.
If set, only objects with a key less than end_marker are returned
If the request needs to be forwarded from a reporting node to a p2p node, the reporting node will set this field. Clients should not set this field.
Identifying string. If user is set, client_ip is not set, and request is coming from a secure_gateway host, then the client is not subject to resource controls
Sequence of the ledger containing the returned ledger objects
Hash of the ledger containing the returned ledger objects
Ledger objects
Key to be passed into a subsequent call to continue iteration. If not set, there are no more objects left in the ledger, or no more objects with key less than end_marker (if end_marker was set in the request)
True if request was exempt from resource controls
Get all ledger objects that are different between the two specified ledgers. Note, this method has no JSON equivalent.
Get the state map difference between the two specified ledgers
If true, include the full ledger object. If false, only keys are included.
If the request needs to be forwarded from a reporting node to a p2p node, the reporting node will set this field. Clients should not set this field.
All ledger objects that were added, modified or deleted between base_ledger and desired_ledger
Get a specific ledger object from a specific ledger
Get a single ledger object
Key of the desired object
Ledger containing the object
If the request needs to be forwarded from a reporting node to a p2p node, the reporting node will set this field. Clients should not set this field.
Ledger containing the object. Will match the value specified in the request.
Get the status of a transaction
Next field: 4
hash of the transaction. 32 bytes ATTN: this is in binary, not hex. The JSON API accepts a hex string for a transaction hash, but here we need that hex string converted into its binary form. Each pair of hex characters should be converted into its corresponding byte. For example, the 4 character hex string "00FF" should be converted to a 2 byte array: [0, 255]
if true, return data in binary format. defaults to false
If the transaction was not found, server will report whether the entire specified range was searched. The value is contained in the error message. The error message is of the form: "txn not found. searched_all = [true,false]" If the transaction was found, this parameter is ignored.
Submit a signed transaction to the XRP Ledger.
A request to submit the signed transaction to the ledger. Next field: 3
The signed transaction to submit.
A response when a signed transaction is submitted to the ledger. Next field: 5
Code indicating the preliminary result of the transaction.
Numeric code indicating the preliminary result of the transaction, directly correlated to engine_result.
Human-readable explanation of the transaction's preliminary result.
32 bytes
Used in: , , , , , , , , ,
A representation of an account address Next field: 2
Used in: , , , , , , , , , , , ,
base58 encoding of an account
Next field: 3
Used in:
Next field: 19
Used in: ,
Next field: 9
Used in:
Used in: ,
32 bytes
Next field: 6
Used in: ,
32 bytes
Next field: 4
Used in:
Next field: 2
Used in: ,
32 bytes
Next field: 3
Used in:
Used in: , , , , , , , , ,
Note, CurrencyAmount is a oneof, that can represent an XRP drops amount or an Issued Currency amount. However, in some transaction types/ledger objects, this value can only be in drops. For instance, the Amount field of a Payment transaction can be specified in XRP drops or an Issued Currency amount, but the Amount field of a PaymentChannelClaim transaction can only be an XRP drops amount.
Used in: ,
Used in: , , ,
Used in:
in drops
Used in:
32 btes
Used in:
Successor information for book directories. The book base is (usually) not an actual object, yet we need to be able to ask for the successor to the book base.
Used in:
Base of the book in question
First book directory in the book. An empty value here means the entire book is deleted
Used in:
Used in: , , ,
time in seconds since Ripple epoch
Used in: ,
32 bytes
Next field: 14
Used in:
Next field: 2
Used in:
Next field: 4
Used in:
Next field: 6
Used in:
Used in: ,
32 bytes
Used in:
Used in:
time in seconds since Ripple epoch
Used in: , ,
Next field: 2
Used in:
Next field: 3
Used in: , , ,
3 character ASCII code
160 bit currency code. 20 bytes
Next field: 3
Used in: , , , , , , , , , ,
Used in:
time in seconds since Ripple epoch
Next field: 2
Used in:
Used in: ,
Used in:
Next field: 3
Used in:
Next field: 7
Used in:
Used in: , , , , , , , , ,
Used in: , ,
Used in: , , , , , , ,
Next field: 12
Used in:
Next field: 3
Used in:
Used in: ,
Used in: ,
Next field: 14
Used in:
Next field: 3
Used in:
Next field: 7
Used in:
Next field: 5
Used in:
Used in: , , , , , , ,
time in seconds since Ripple epoch
Next field: 5
Used in:
Next field: 5
Used in:
Next field: 6
Used in:
Used in: ,
time in seconds since Ripple epoch
Used in:
Used in: , , , , , , , , , , , , , , , ,
Used in:
Next field: 9
Used as response type in: XRPLedgerAPIService.GetTransaction
Used as field type in:
Variable length
Sequence number of ledger that contains this transaction
32 bytes
whether the ledger has been validated
metadata about the transaction
Variable length
Used in:
32 bytes
Used in:
Used in:
Used in:
Used in:
Used in: ,
32 bytes
Used in:
Used in:
Used in: , ,
32 bytes
A representation of an amount of issued currency. Next field: 4
Used in:
The currency used to value the amount.
The value of the amount. 8 bytes
Unique account address of the entity issuing the currency.
Used in:
Used in: , ,
Next field: 15
Used in:
Next field: 4
Used in:
Next field: 17
Used in: , ,
Next field: 3
Used in: ,
Note, if ledger_index_min is non-zero and ledger_index_max is 0, the software will use the max validated ledger in place of ledger_index_max
Next field: 4
Used in: , , , , , ,
32 bytes
Next field: 4
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Next field: 3
Used in: ,
Next field: 4
Used in:
Used in:
Used in:
Used in:
Used in: ,
Next field: 5
Used in:
index in ledger
result code indicating whether the transaction succeeded or failed
Used in:
Next field: 5
Used in:
Next field: 3
Used in:
Next field: 4
Used in:
Used in:
Next field: 3
Used in:
Used in:
32 bytes
Next field: 2
Used in:
Next field: 6
Used in:
Used in: , , , ,
Next field: 5
Used in:
Used in: ,
Next field: 11
Used in:
Used in:
Next field: 7
Used in:
Used in:
32 bytes
Used in:
Next field: 5
Used in:
Used in:
32 bytes
Next field: 12
Used in:
Next field: 2
Used in:
Next field: 5
Used in:
Used in: , , ,
Used in: , , , , ,
Used in:
Used in: , , , , , , ,
Next field: 13
Used in:
Next field: 8
Used in:
Next field: 2
Used in:
Next field: 4
Used in:
Next field: 6
Used in:
Next field: 7
Used in:
Next field: 4
Used in:
Used in:
Used in:
32 bytes
Used in: , , , , , , , , , , ,
32 bytes
Used in: , , , , , , , , , , ,
Used in: , , ,
Used in:
Used in:
Aggregate data about queued transactions Next field: 11
Used in:
Data about a single queued transaction Next field: 8
Used in:
Next field: 3
Used in: ,
Raw data of the ledger object. In GetLedgerResponse and GetLedgerDiffResponse, data will be empty if the object was deleted.
Key of the ledger object
Whether the object was created, modified or deleted
Key of the object preceding this object in the desired ledger
Key of the object succeeding this object in the desired ledger
Used in:
Used in: , ,
Used in:
Used in: ,
Used in:
in drops
Used in:
in drops
Next field: 13
Used in:
Used in:
32 bytes
Used in: , ,
Used in: , , , ,
Used in:
Next field: 2
Used in:
Used in: ,
Next field: 4
Used in:
Next field: 3
Used in: ,
Next field: 8
Used in: ,
Used in:
Next field: 3
Used in:
Used in: ,
Used in:
is actually uint16
Used in: ,
Used in: , , ,
Used in: ,
*** Messages wrapping a Currency value *** TODO: if there's a V2 of the API, fix this misspelling.
Used in:
Used in:
20 bytes
Used in: ,
Used in:
Used in:
20 bytes
Used in: ,
is actually uint8
Used in:
Used in: ,
Next field: 2
Used in:
Next field: 7
Used in:
Used in: ,
A message encompassing all transaction types Next field: 37
Used in:
Data specific to the type of transaction
Used in:
Used in:
Used in:
Next field: 3
Used in: ,
category of the transaction result
full result string, i.e. tesSUCCESS
Next field: 7
Used in:
Claimed cost only
Failure
Local error
Malformed transaction
Retry
Success
Used in: ,
Used in:
is actually uint16
Used in: ,
Next field: 4
Used in:
Used in: ,
Used in:
Used in:
Used in:
Used in:
32 bytes
A representation of an amount of XRP. Next field: 2
Used in: , , , ,