> ## Documentation Index
> Fetch the complete documentation index at: https://docs.validationcloud.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Retrieve a Ledger's Payments

> 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.

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.

This method will use `20` [Compute Units](/nodeapi/about/billing).

***

## Reference: [Here](https://developers.stellar.org/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments)


## OpenAPI

````yaml nodeapi/openapi/horizon-openapi-vc.json GET /ledgers/{sequence}/payments
openapi: 3.0.3
info:
  title: Horizon
  version: 0.0.1
servers:
  - url: https://mainnet.stellar.validationcloud.io/v1/<YOUR_API_KEY_HERE>
    description: The Pubnet Network
security: []
tags:
  - name: Accounts
    description: >-
      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.
  - name: Assets
    description: >-
      Assets are representations of value issued on the Stellar network. An
      asset consists of a type, code, and issuer.
  - name: Claimable Balances
    description: >-
      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.
  - name: Effects
    description: >-
      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.
  - name: Fee Stats
    description: >-
      Fee stats are used to predict what fee to set for a transaction before
      submitting it to the network.
  - name: Liquidity Pools
    description: >-
      Liquidity Pools provide a simple, non-interactive way to trade large
      amounts of capital and enable high volumes of trading.
  - name: Ledgers
    description: >-
      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.
  - name: Offers
    description: >-
      Offers are statements about how much of an asset an account wants to buy
      or sell.
  - name: Order Books
    description: An order book is a collections of offers for a specific pair of assets.
  - name: Trade Aggregations
    description: >-
      A trade aggregation represents aggregated statistics on an asset pair
      (base and counter) for a specific time period. Trade aggregations are
      useful to developers of trading clients and provide historical trade data.
  - name: Trades
    description: >-
      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.
  - name: Transactions
    description: >-
      Transactions are commands that modify the ledger state and consist of one
      or more operations.
paths:
  /ledgers/{sequence}/payments:
    get:
      tags:
        - Ledgers
      summary: Retrieve a Ledger's Payments
      description: >-
        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.
      operationId: RetrieveALedgersPayments
      parameters:
        - $ref: '#/components/parameters/SequenceParam'
        - $ref: '#/components/parameters/CursorParam'
        - $ref: '#/components/parameters/OrderParam'
        - $ref: '#/components/parameters/LimitParam'
        - $ref: '#/components/parameters/IncludeFailedParam'
        - $ref: '#/components/parameters/JoinParam'
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/Links'
                  - $ref: '#/components/schemas/Payment'
              examples:
                RetrieveALedgersPayments:
                  $ref: '#/components/examples/RetrieveALedgersPayments'
components:
  parameters:
    SequenceParam:
      name: sequence
      in: path
      required: true
      description: The sequence number of a specific ledger.
      schema:
        type: integer
        example: 0
    CursorParam:
      name: cursor
      in: query
      required: false
      description: >-
        A number that points to a specific location in a collection of responses
        and is pulled from the paging_token value of a record.
      schema:
        type: integer
        example: 6606617478959105
    OrderParam:
      name: order
      in: query
      required: false
      description: >-
        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.
      schema:
        type: string
        enum:
          - asc
          - desc
    LimitParam:
      name: limit
      in: query
      required: false
      description: >-
        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.
      schema:
        type: integer
        example: 10
    IncludeFailedParam:
      name: include_failed
      in: query
      required: false
      description: >-
        Set to true to include failed operations in results. Options include
        true and false.
      schema:
        type: boolean
        enum:
          - true
          - false
    JoinParam:
      name: join
      in: query
      required: false
      description: >-
        Set to transactions to include the transactions which created each of
        the operations in the response.
      schema:
        type: string
  schemas:
    Links:
      type: object
      properties:
        _links:
          type: object
          properties:
            self:
              $ref: '#/components/schemas/link'
            next:
              $ref: '#/components/schemas/link'
            prev:
              $ref: '#/components/schemas/link'
    Payment:
      type: object
      properties:
        _embedded:
          type: object
          properties:
            records:
              type: array
              items:
                type: object
                properties:
                  _links:
                    type: object
                    properties:
                      self:
                        $ref: '#/components/schemas/link'
                      transaction:
                        $ref: '#/components/schemas/link'
                      effects:
                        $ref: '#/components/schemas/link'
                      succeeds:
                        $ref: '#/components/schemas/link'
                      precedes:
                        $ref: '#/components/schemas/link'
                    required:
                      - self
                      - transaction
                      - effects
                      - succeeds
                      - precedes
                  id:
                    $ref: '#/components/schemas/id'
                  paging_token:
                    type: string
                  transaction_successful:
                    type: boolean
                  source_account:
                    $ref: '#/components/schemas/address'
                  type:
                    type: string
                    example: payment
                  type_i:
                    type: string
                  created_at:
                    type: string
                  transaction_hash:
                    type: string
                  asset_type:
                    type: string
                  asset_code:
                    enum:
                      - native
                      - credit_alphanum4
                      - credit_alphanum12
                  asset_issuer:
                    $ref: '#/components/schemas/address'
                  from:
                    $ref: '#/components/schemas/address'
                  to:
                    $ref: '#/components/schemas/address'
                  amount:
                    type: string
                required:
                  - id
                  - paging_token
                  - transaction_successful
                  - source_account
                  - type
                  - type_i
                  - created_at
                  - transaction_hash
                  - asset_type
                  - from
                  - to
                  - amount
    link:
      type: object
      properties:
        href:
          type: string
          format: link
        templated:
          type: boolean
      required:
        - href
    id:
      type: string
    address:
      type: string
      pattern: G[A-Z0-9]{55}
  examples:
    RetrieveALedgersPayments:
      value:
        _links:
          self:
            href: >-
              https://horizon-testnet.stellar.org/ledgers/27521176/payments?cursor=&limit=1&order=asc
          next:
            href: >-
              https://horizon-testnet.stellar.org/ledgers/27521176/payments?cursor=118202550867476481&limit=1&order=asc
          prev:
            href: >-
              https://horizon-testnet.stellar.org/ledgers/27521176/payments?cursor=118202550867476481&limit=1&order=desc
        _embedded:
          records:
            - _links:
                self:
                  href: >-
                    https://horizon-testnet.stellar.org/operations/118202550867476481
                transaction:
                  href: >-
                    https://horizon-testnet.stellar.org/transactions/971454b84a82baa38afa975e9eb4ff2632821b5a3e7f7993a7e20bbd9d7633ea
                effects:
                  href: >-
                    https://horizon-testnet.stellar.org/operations/118202550867476481/effects
                succeeds:
                  href: >-
                    https://horizon-testnet.stellar.org/effects?order=desc&cursor=118202550867476481
                precedes:
                  href: >-
                    https://horizon-testnet.stellar.org/effects?order=asc&cursor=118202550867476481
              id: '118202550867476481'
              paging_token: '118202550867476481'
              transaction_successful: true
              source_account: GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH
              type: payment
              type_i: 1
              created_at: '2019-12-30T22:35:49Z'
              transaction_hash: 971454b84a82baa38afa975e9eb4ff2632821b5a3e7f7993a7e20bbd9d7633ea
              asset_type: credit_alphanum4
              asset_code: NODL
              asset_issuer: GB2Y3AWXVROM2BHFQKQPTWKIOI3TZEBBD3LTKTVQTKEPXGOBE742NODL
              from: GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH
              to: GDGJS7AXAUFDZARIRDVZ5V7CFW6XY47WSBE2OVLCCGCDWOE7INKYN3PS
              amount: '0.0000017'

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.