Bamboo Card
GET

Orders

Retrieve historical order records for a selected reporting window, including product, quantity, pricing, account currency, and status.

GET/api/Integration/v1/orders

Use Orders to retrieve historical order data for a reporting window defined by startDate and endDate.

Each row in the response represents a purchased product line with pricing, denomination, account currency, and Bamboo order status details.

This endpoint requires Basic Auth using your API credentials.

Query parameters

Provide the date range you want Bamboo to return.

ParameterTypeRequiredDescriptionExample
startDatestringYesStart date for the orders report.2022-10-01
endDatestringYesEnd date for the orders report.2022-11-20

Response specifications

Orders returns a flat array of report rows for the selected date range.

FieldTypeDescription
clientNamestringClient name returned in the order report.
orderNumberstringBamboo order number.
orderDatestringOrder date timestamp.
clientReferenceNumberstringClient reference number / RequestId.
channelstringOrder channel such as Sandbox or Production.
productNamestringPurchased product name.
denominationstringHuman-readable product denomination.
quantitynumberNumber of cards purchased.
unitPricenumberPer-card client price.
subTotalnumberSubtotal charged before any report-specific aggregation.
totalnumberTotal amount charged for the report row.
accountCurrencystringSettlement currency of the account that paid for the order.
statusstringFinal Bamboo order status.

Examples

Full request and response examples for this endpoint.

Example request

Use this full request as the primary reference for client-side implementation.

cURL - cURL
# Generate token: echo -n 'YOUR_CLIENT_ID:YOUR_CLIENT_SECRET' | base64

curl --location 'https://api.bamboocardportal.com/api/Integration/v1/orders?startDate=2026-04-01&endDate=2026-05-19' \
  --header 'Authorization: Basic YOUR_BASE64_TOKEN' \
  --header 'Accept: application/json'

Example response

Use this sample payload to validate parsing, field mapping, and downstream handling.

200 OK
JSON
[
  {
    "clientName": "Bamboo Tech - Testing",
    "orderNumber": "O-06761537",
    "orderDate": "2024-05-15T00:00:00",
    "clientReferenceNumber": "97018cf7-98f5-40fc-a142-711d43a72e17",
    "channel": "Sandbox",
    "productName": "Steam 10 USD BH",
    "denomination": "USD 10",
    "quantity": 1,
    "unitPrice": 9.47,
    "subTotal": 9.47,
    "total": 9.47,
    "accountCurrency": "USD",
    "status": "Succeeded"
  },
  {
    "clientName": "Bamboo Tech - Testing",
    "orderNumber": "O-06779294",
    "orderDate": "2024-05-16T00:00:00",
    "clientReferenceNumber": "71ac2817-e51a-438a-bb7b-5ffdda23603c",
    "channel": "Sandbox",
    "productName": "Steam 10 USD BH",
    "denomination": "USD 10",
    "quantity": 2,
    "unitPrice": 9.47,
    "subTotal": 18.94,
    "total": 18.9401,
    "accountCurrency": "USD",
    "status": "Succeeded"
  }
]

Typical report uses

Order history is commonly used for reconciliation, exports, and operational review.

Reconciliation

Compare order totals against account balances and downstream settlement reports.

Reference lookup

Use clientReferenceNumber to map Bamboo orders back to your internal RequestId.

Status review

Use the status field to identify fulfilled, failed, and partial order outcomes in the reporting window.

Historical exports

Export the order list for audit, finance, or customer-service workflows.

Settlement currency

accountCurrency shows the currency of the account that paid for the order.

Product granularity

Each record reflects a product line, not a grouped summary for every order in the date range.

On this page

Try it out

Open the interactive API panel to test this endpoint with your own credentials.