XRPSCAN
HomeMetricsValidatorsAmendments
  • 📖Build with XRPSCAN
  • 📘API Documentation
    • Introduction
    • Pricing
      • Pay as you Go (PAYG)
    • API Concepts
      • Pagination
    • Account
      • Account info
      • Activations
      • Ancestry
      • Assets
      • Deposit Preauths
      • DEX Orders
      • Escrows
      • Issued tokens
      • Issued token balance
      • NFTs
      • Settings
      • Trustlines
      • Transactions
      • Xumm KYC status
    • Transaction
      • Transaction info
    • Ledger
      • Ledgers
      • Ledger info
      • Transactions
    • NFT
      • NFT info
    • AMM
      • AMM info
      • Pools
    • Object
      • Object info
    • Amendment
      • Amendments
      • Amendment info
    • Validator
      • Registry
      • Validator info
      • Report
    • Node
      • Nodes
      • Node info
    • Network
      • Fee
      • Server info
      • Server versions
    • Account Name
      • Well known accounts
    • Balance
      • Balances
    • Fact
      • Facts in namespace
      • Fact
    • Metrics
      • Metrics
    • Health
      • Ping
  • 📗Help
    • Integration guide
    • Validator
    • Contribute
    • Privacy policy
    • Contact us
  • 📙FAQs
    • How to report scams
Powered by GitBook
On this page
  1. API Documentation
  2. API Concepts

Pagination

Some APIs may contain a large number of documents. It is possible to paginate data in such APIs by passing limit and offset parameters in the GET query string.

Parameter
Type
Description

limit

Number

Maximum number of documents the API will return.

offset

Number

Number of documents to skip in the results set.

Example

To fetch 20 AMM pools from record 60 through 79, offset parameter would be set to 60 and limit parameter would be set to 20.

$ curl "https://api.xrpscan.com/api/v1/amm/pools?=60&=20"
PreviousAPI ConceptsNextAccount

Last updated 3 months ago

📘