Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This endpoint actually submits a transaction to the Stellar network. It only takes a single, required parameter: the signed transaction. Refer to the Transactions page for details on how to craft a proper one. If you submit a transaction that has already been included in a ledger, this endpoint will return the same response as would’ve been returned for the original transaction submission. This allows for safe resubmission of transactions in error scenarios, as highlighted in the error-handling guide.
This method will use 20
Compute Units.
Users interact with the Stellar network through accounts. Everything else in the ledger—assets, offers, trustlines, etc.—are owned by accounts, and accounts must authorize all changes to the ledger through signed transactions.
Learn more about accounts.
Assets are representations of value issued on the Stellar network. An asset consists of a type, code, and issuer.
Learn more about assets.
The single account endpoint provides information on a specific account. The balances section in the response will also list all the trustlines this account has established, including trustlines that haven’t been authorized yet.
This method will use 20
Compute Units.
This endpoint represents successful transactions for a given account and can be used in streaming mode. Streaming mode allows you to listen for new transactions for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
This method will use 20
Compute Units.
This endpoint lists accounts by one of four filters : signer, asset, liquidity pool or sponsor.
This method will use 20
Compute Units.
This endpoint represents successful operations for a given account and can be used in streaming mode. Streaming mode allows you to listen for new operations for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
This method will use 20
Compute Units.
This endpoint represents successful payments for a given account and can be used in streaming mode. Streaming mode allows you to listen for new payments for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time.
This method will use 20
Compute Units.
This endpoint represents all offers a given account has currently open and can be used in streaming mode. Streaming mode allows you to listen for new offers for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time.
This method will use 20
Compute Units.
This endpoint returns the effects of a specific account and can be used in streaming mode. Streaming mode allows you to listen for new effects for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
This method will use 20
Compute Units.
This endpoint represents a single data for a given account.
This method will use 20
Compute Units.
This endpoint represents all trades for a given account and can be used in streaming mode. Streaming mode allows you to listen for trades for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time.
This method will use 20
Compute Units.
This endpoint lists all ledgers and can be used in streaming mode. Streaming mode allows you to listen for new ledgers as they close. If called in streaming mode, Horizon will start at the earliest known ledger unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream ledgers since your request time.
This method will use 20
Compute Units.
This endpoint lists all available liquidity pools.
This method will use 20
Compute Units.
This endpoint represents successful trades fulfilled by the given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new trades referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trade created since your request time.
This method will use 20
.
The single offer endpoint provides information on a specific offer.
This method will use 20
Compute Units.
The single operation endpoint provides information about a specific operation.
This method will use 20
Compute Units.
This endpoint represents a single data for a given account.
This account’s public key encoded in a base32 string representation.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
The key name for this data.
"config.memo_required"
Success
This endpoint lists all available liquidity pools.
Comma-separated list of assets in canonical form (Code:IssuerAccountID), to only include liquidity pools which have reserves matching all listed assets.
A Stellar account ID, to only include liquidity pools in which this account is participating in (i.e. holds pool shares to).
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
The single operation endpoint provides information about a specific operation.
The ID number for this operation.
121692259040116740
Set to transactions to include the transactions which created each of the operations in the response.
Success
0
"create_account"
The single offer endpoint provides information on a specific offer.
A unique identifier for this offer.
Success
G[A-Z0-9]{55}
This endpoint represents successful payments for a given account and can be used in streaming mode. Streaming mode allows you to listen for new payments for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time.
This account’s public key encoded in a base32 string representation.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Set to transactions to include the transactions which created each of the operations in the response.
Success
G[A-Z0-9]{55}
"payment"
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint represents all offers a given account has currently open and can be used in streaming mode. Streaming mode allows you to listen for new offers for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time.
This account’s public key encoded in a base32 string representation.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
This endpoint lists all assets.
The code of the asset you would like to filter by.
The Stellar address of the issuer for the asset you would like to filter by.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
This endpoint represents all trades for a given account and can be used in streaming mode. Streaming mode allows you to listen for trades for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time.
This account’s public key encoded in a base32 string representation.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint represents successful trades fulfilled by the given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new trades referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trade created since your request time.
A unique identifier for this liquidity pool.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint returns the effects of a specific account and can be used in streaming mode. Streaming mode allows you to listen for new effects for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
This account’s public key encoded in a base32 string representation.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
"create_account"
0
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint represents successful operations for a given account and can be used in streaming mode. Streaming mode allows you to listen for new operations for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
This account’s public key encoded in a base32 string representation.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Set to transactions to include the transactions which created each of the operations in the response.
Success
G[A-Z0-9]{55}
"create_account"
0
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint lists all ledgers and can be used in streaming mode. Streaming mode allows you to listen for new ledgers as they close. If called in streaming mode, Horizon will start at the earliest known ledger unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream ledgers since your request time.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
This endpoint lists accounts by one of four filters : signer, asset, liquidity pool or sponsor.
Account ID of the sponsor. Every account in the response will either be sponsored by the given account ID or have a subentry (trustline, offer, or data entry) which is sponsored by the given account ID.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
An issued asset represented as “Code:IssuerAccountID”. Every account in the response will have a trustline for the given asset.
Account ID of the signer. Every account in the response will have the given account ID as a signer.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
With this parameter, the results will include only accounts which have trustlines to the specified liquidity pool.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Returns accounts based on provided filter: signer , asset, sponser or liquidity pool
G[A-Z0-9]{55}
[0-9]+
G[A-Z0-9]{55}
[0-9]+\.[0-9]{7}
[0-9]+\.[0-9]{7}
[0-9]+\.[0-9]{7}
[0-9]+\.[0-9]{7}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
The single account endpoint provides information on a specific account. The balances section in the response will also list all the trustlines this account has established, including trustlines that haven’t been authorized yet.
This account’s public key encoded in a base32 string representation.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
Returns details like balances, sponserships etc. about an account.
G[A-Z0-9]{55}
[0-9]+
G[A-Z0-9]{55}
[0-9]+\.[0-9]{7}
[0-9]+\.[0-9]{7}
[0-9]+\.[0-9]{7}
[0-9]+\.[0-9]{7}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint actually submits a transaction to the Stellar network. It only takes a single, required parameter: the signed transaction. Refer to the Transactions page for details on how to craft a proper one. If you submit a transaction that has already been included in a ledger, this endpoint will return the same response as would’ve been returned for the original transaction submission. This allows for safe resubmission of transactions in error scenarios, as highlighted in the error-handling guide.
The base64-encoded XDR of the transaction.
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint represents successful transactions for a given account and can be used in streaming mode. Streaming mode allows you to listen for new transactions for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
This account’s public key encoded in a base32 string representation.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
Effects represent specific changes that occur in the ledger as a result of successful operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are.
A Claimable Balance represents the transfer of ownership of some amount of an asset. Claimable balances provide a mechanism for setting up a payment which can be claimed in the future. This allows you to make payments to accounts which are currently not able to accept them.
Each ledger stores the state of the network at a point in time and contains all the changes - transactions, operations, effects, etc. - to that state.
Learn more about ledgers.
This endpoint lists all available claimable balances.
This method will use 20
Compute Units.
This endpoint represents successful transactions referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
This method will use 20
Compute Units.
The single ledger endpoint provides information on a specific ledger.
This method will use 20
Compute Units.
This endpoint represents successful transactions in a given ledger.
This method will use 20
Compute Units.
This endpoint lists all effects and can be used in streaming mode. Streaming mode allows you to listen for new effects as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
This method will use 20
Compute Units.
There are eight groups of effect types. Each effect type has its own set of attributes.
Account Created
create_account
Account Removed
merge_account
Account Credited
create_account, payment, path_payment, merge_account
Account Debited
create_account, payment, path_payment, merge_account
Account Thresholds Updated
set_options
Account Home Domain Updated
set_options
Account Flags Updated
set_options
Account Inflation Destination Updated
set_options
Signer Created
set_options
Signer Removed
set_options
Signer Updated
set_options
Trustline Created
change_trust
Trustline Removed
change_trust
Trustline Updated
change_trust, allow_trust
Trustline Authorized
allow_trust
Trustline Deauthorized
allow_trust
Offer Created
manage_buy_offer, manage_sell_offer, create_passive_sell_offer
Offer Removed
manage_buy_offer, manage_sell_offer, create_passive_sell_offer, path_payment
Offer Updated
manage_buy_offer, manage_sell_offer, create_passive_sell_offer, path_payment
Trade
manage_buy_offer, manage_sell_offer, create_passive_sell_offer, path_payment
Data Created
manage_data
Data Removed
manage_data
Data Updated
manage_data
Claimable Balance Created
create_claimable_balance
Claimable Balance Claimant Created
create_claimable_balance
Claimable Balance Claimed
claim_claimable_balance
Account Sponsorship Created
create_account
Account Sponsorship Updated
revoke_sponsorship
Account Sponsorship Removed
revoke_sponsorship
Trustline Sponsorship Created
change_trust
Trustline Sponsorship Updated
revoke_sponsorship
Trustline Sponsorship Removed
revoke_sponsorship
Account Data Sponsorship Created
manage_data
Account Data Sponsorship Updated
revoke_sponsorship
Account Data Sponsorship Removed
revoke_sponsorship
Claimable Balance Sponsorship Created
create_claimable_balance
Claimable Balance Sponsorship Updated
revoke_sponsorship
Claimable Balance Sponsorship Removed
revoke_sponsorship
Account Signer Sponsorship Created
set_options
Account Signer Sponsorship Updated
revoke_sponsorship
Account Signer Sponsorship Removed
revoke_sponsorship
Liquidity Pool Created
change_trust
Liquidity Pool Removed
change_trust
Liquidity Pool Revoked
change_trust, allow_trust
Liquidity Pool Deposited
liquidity_pool_deposit
Liquidity Pool Withdraw
liquidity_pool_withdraw
Liquidity Pool Trade
path_payment
Sequence Bumped
bump_sequence
This endpoint represents successful operations referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
This method will use 20
.
This endpoint represents effects referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new effects referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
This method will use 20
.
This endpoint represents successful operations referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
This method will use 20
.
This endpoint lists all currently open offers and can be used in streaming mode. Streaming mode allows you to listen for new offers as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time. When filtering by buying or selling arguments, you must use a combination of selling_asset_type, selling_asset_issuer, and selling_asset_code for the selling asset, or a combination of buying_asset_type, buying_asset_issuer, and buying_asset_code for the buying asset.
This method will use 20
.
Offers are statements about how much of an asset an account wants to buy or sell.
Learn more about offers.
Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading.
Transactions are commands that modify the ledger state and consist of one or more operations.
Learn more about transactions.
Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction.
Each of Stellar’s operations have a unique operation object.
This endpoint returns successful operations in a specific ledger.
This method will use 20
Compute Units.
The single liquidity pool endpoint provides information on a liquidity pool.
This method will use 20
Compute Units.
This endpoint represents successful transactions referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
This method will use 20
Compute Units.
This endpoint represents all trades for a given offer and can be used in streaming mode. Streaming mode allows you to listen for trades for this offer as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time.
This method will use 20
Compute Units.
This endpoint lists all trades and can be used in streaming mode. Streaming mode allows you to listen for new trades as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time. When filtering for a specific orderbook, you must use use all six of these arguments: base_asset_type, base_asset_issuer, base_asset_code, counter_asset_type, counter_asset_issuer, and counter_asset_code. If the base or counter asset is XLM, you only need to indicate the asset type as native and do not need to designate the code or the issuer.
This method will use 20
Compute Units.
This endpoint lists all Successful transactions and can be used in streaming mode. Streaming mode allows you to listen for new transactions as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
This method will use 20
.
This endpoint lists all effects and can be used in streaming mode. Streaming mode allows you to listen for new effects as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
1
This endpoint lists all available claimable balances.
Account ID of the sponsor. Every account in the response will either be sponsored by the given account ID or have a subentry (trustline, offer, or data entry) which is sponsored by the given account ID.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
An issued asset represented as “Code:IssuerAccountID”. Every account in the response will have a trustline for the given asset.
Account ID of the destination address. Only include claimable balances which can be claimed by the given account ID.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
The single ledger endpoint provides information on a specific ledger.
The sequence number of a specific ledger.
0
Success
This endpoint represents successful transactions referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
A unique identifier for this claimable balance.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint represents successful transactions in a given ledger.
The sequence number of a specific ledger.
0
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint returns the effects of a specific ledger.
The sequence number of a specific ledger.
0
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
1
This endpoint represents successful operations referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
A unique identifier for this claimable balance.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Set to transactions to include the transactions which created each of the operations in the response.
Success
G[A-Z0-9]{55}
"create_account"
0
G[A-Z0-9]{55}
G[A-Z0-9]{55}
The single claimable balance endpoint provides information on a claimable balance.
A unique identifier for this claimable balance.
Success
G[A-Z0-9]{55}
This endpoint represents effects referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new effects referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
A unique identifier for this liquidity pool.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
1
This endpoint represents successful operations referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
A unique identifier for this liquidity pool.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Set to transactions to include the transactions which created each of the operations in the response.
Success
0
"create_account"
This endpoint lists all currently open offers and can be used in streaming mode. Streaming mode allows you to listen for new offers as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time. When filtering by buying or selling arguments, you must use a combination of selling_asset_type, selling_asset_issuer, and selling_asset_code for the selling asset, or a combination of buying_asset_type, buying_asset_issuer, and buying_asset_code for the buying asset.
Account ID of the sponsor. Every account in the response will either be sponsored by the given account ID or have a subentry (trustline, offer, or data entry) which is sponsored by the given account ID.
"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"
The account ID of the offer creator.
The type for the selling asset. Either native, credit_alphanum4, or credit_alphanum12.
The Stellar address of the selling asset’s issuer.
The code for the selling asset.
The type for the buying asset. Either native, credit_alphanum4, or credit_alphanum12.
The Stellar address of the buying asset’s issuer.
The code for the buying asset.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
When an offer is fully or partially fulfilled, a trade happens. Trades can also be caused by successful path payments, because path payments involve fulfilling offers.
A trade occurs between two parties—base
and counter
. Which is which is either arbitrary or determined by the calling query.
Learn more about trades.
This endpoint returns the effects of a specific transaction.
This method will use 20
Compute Units.
This endpoint returns the effects of a specific operation.
This method will use 20
Compute Units.
This endpoint returns successful operations in a specific ledger.
The sequence number of a specific ledger.
0
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Set to transactions to include the transactions which created each of the operations in the response.
Success
0
"create_account"
The single liquidity pool endpoint provides information on a liquidity pool.
A unique identifier for this liquidity pool.
Success
This endpoint represents all trades for a given offer and can be used in streaming mode. Streaming mode allows you to listen for trades for this offer as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time.
A unique identifier for this offer.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint lists all trades and can be used in streaming mode. Streaming mode allows you to listen for new trades as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time. When filtering for a specific orderbook, you must use use all six of these arguments: base_asset_type, base_asset_issuer, base_asset_code, counter_asset_type, counter_asset_issuer, and counter_asset_code. If the base or counter asset is XLM, you only need to indicate the asset type as native and do not need to designate the code or the issuer.
The offer ID. Used to filter for trades originating from a specific offer.
The type for the base asset. Either native, credit_alphanum4, or credit_alphanum12.
The Stellar address of the base asset’s issuer.
"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
The code for the base asset.
"USD"
The type for the counter asset. Either native, credit_alphanum4, or credit_alphanum12.
The Stellar address of the counter asset’s issuer.
"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
The code for the counter asset.
Can be set to all, orderbook, or liquidity_pools to filter only trades executed across a given mechanism.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint represents successful transactions referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
A unique identifier for this liquidity pool.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint returns Successful operations for a specific transaction.
Transactions are commands that modify the ledger state and consist of one or more operations.
"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Set to transactions to include the transactions which created each of the operations in the response.
Success
0
"create_account"
The single transaction endpoint provides information on a specific transaction.
Transactions are commands that modify the ledger state and consist of one or more operations.
"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint lists all Successful transactions and can be used in streaming mode. Streaming mode allows you to listen for new transactions as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Success
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint returns the effects of a specific operation.
The ID number for this operation.
121692259040116740
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
1
This endpoint returns the effects of a specific transaction.
Transactions are commands that modify the ledger state and consist of one or more operations.
"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Success
G[A-Z0-9]{55}
1
This endpoint lists all Successful operations and can be used in streaming mode. Streaming mode allows you to listen for new operations as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
This method will use 20
Compute Units.
This endpoint lists all Successful payment-related operations and can be used in streaming mode. Streaming mode allows you to listen for new payments as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time. Operations that can be returned by this endpoint include: create_account, payment, path_payment_strict_recieve, path_payment_strict_send, and account_merge .
This method will use 20
Compute Units.
This endpoint returns all payment-related operations in a specific ledger. Operation types that can be returned by this endpoint include: create_account, payment, path_payment, and account_merge.
The sequence number of a specific ledger.
0
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Set to transactions to include the transactions which created each of the operations in the response.
Success
G[A-Z0-9]{55}
"payment"
G[A-Z0-9]{55}
G[A-Z0-9]{55}
G[A-Z0-9]{55}
This endpoint lists all Successful operations and can be used in streaming mode. Streaming mode allows you to listen for new operations as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Set to transactions to include the transactions which created each of the operations in the response.
Success
0
"create_account"
This endpoint lists all Successful payment-related operations and can be used in streaming mode. Streaming mode allows you to listen for new payments as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time. Operations that can be returned by this endpoint include: create_account, payment, path_payment_strict_recieve, path_payment_strict_send, and account_merge .
A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.
6606617478959105
A designation of the order in which records should appear. Options include asc (ascending) or desc (descending). If this argument isn’t set, it defaults to asc.
The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
10
Set to true to include failed operations in results. Options include true and false.
Set to transactions to include the transactions which created each of the operations in the response.
Success
G[A-Z0-9]{55}
"create_account"
0
G[A-Z0-9]{55}
G[A-Z0-9]{55}