RedeemSG Integration Guide
  • Overview
  • PHASE 1: GETTING STARTED
    • Submit interest to NEA
    • Information provided
  • PHASE 2: INTEGRATION
    • Overview
    • API documentation
      • Introduction
      • Environment
      • Authentication
        • In event of leaked API key
      • Redeeming a QR code Voucher
        • POST /v1/vouchers/redeem
          • Attributes
          • Returns
        • Making Idempotent Redemption Requests
          • Introduction
          • Implementation and Details
      • Retrieving transactions
        • GET /v1/transactions
        • Request
        • Response
      • Errors
        • Overview
        • Error codes
      • Changelog
    • Tech requirement
      • Overall flow
      • Sales System Requirements
      • Reconciliation requirements
      • Changelog
    • Generate API keys
      • Login
      • Create API key
  • PHASE 3: UAT
    • Overview
    • Complete test cases
      • Create vouchers
      • Download test cases
    • UAT self-review
      • Review UAT results
    • Inform NEA
    • UAT with RedeemSG
      • UAT submission
    • What should I do if I have questions?
      • FAQs
      • Weekly office hours
  • PHASE 4: PRODUCTION TESTING
    • Production testing
      • Arrange date for prod testing
      • Test cases conducted
      • Items to prepare
      • FAQs
    • Ops readiness check
Powered by GitBook
On this page
  1. PHASE 2: INTEGRATION
  2. API documentation
  3. Retrieving transactions

GET /v1/transactions

PreviousRetrieving transactionsNextRequest

Last updated 7 months ago

5.1 GET /v1/transactions

Date range filtering

You can specify a start and end date window to retrieve transaction data made within the timeframe, inclusive of the dates. For example, specifying start and end as 2022-10-01 and 2022-10-31 returns all transactions made in Oct 2022. For retrieving transactions on a specific day, set start and end to the same date.

If start and end are not specified, the response will return all transactions since inception.

Transactions are returned in ascending order by time of creation.

Pagination

Additionally, the end point uses for retrieval of data. Results are sorted in ascending order of transaction creation date.

cursor pagination