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

# How Do I Fetch Order Details with Gameball POS (v4)?

> Retrieve order transaction history and customer activities

Retrieve detailed information about orders and customer activities to display purchase history, verify transactions, support customers, or feed analytics. Two endpoints cover this: one scoped to a single order, the other to a customer's full activity log.

## Order Transactions

Get all transactions associated with a specific order:

```bash cURL theme={null}
curl -X GET 'https://api.gameball.co/api/v4.0/integrations/orders/{orderId}/transactions' \
  -H 'APIKey: YOUR_API_KEY' \
  -H 'SecretKey: YOUR_SECRET_KEY'
```

```json Success theme={null}
{
  "orderId": "ORD000123",
  "transactions": [
    {
      "transactionId": "TXN001",
      "type": "points_earned",
      "points": 9.5,
      "timestamp": "2025-10-19T12:10:00Z"
    },
    {
      "transactionId": "TXN002",
      "type": "points_redeemed",
      "points": 100,
      "timestamp": "2025-10-19T12:10:00Z"
    }
  ]
}
```

## Customer Activities

Get the complete purchase history and activities for a customer:

```bash cURL theme={null}
curl -X GET 'https://api.gameball.co/api/v4.0/integrations/customers/{customerId}/activities' \
  -H 'APIKey: YOUR_API_KEY' \
  -H 'SecretKey: YOUR_SECRET_KEY'
```

```json Success theme={null}
{
  "customerId": "12345",
  "activities": [
    {
      "activityId": "ACT001",
      "type": "order",
      "orderId": "ORD000123",
      "pointsEarned": 9.5,
      "pointsRedeemed": 100,
      "date": "2025-10-19T12:10:00Z"
    },
    {
      "activityId": "ACT002",
      "type": "order",
      "orderId": "ORD000122",
      "pointsEarned": 15.0,
      "date": "2025-10-18T14:30:00Z"
    }
  ]
}
```

## When to Use Each

* **Display purchase history**: show customers their recent orders and points earned (customer activities).
* **Transaction verification**: confirm a specific order's point breakdown (order transactions).
* **Customer support**: resolve disputes about transactions.
* **Analytics**: track behavior and program engagement.

## Tips & Gotchas

* Use the **order transactions** endpoint for a detailed breakdown of one order.
* Use the **customer activities** endpoint for a complete purchase history.
* Both endpoints support pagination for large result sets.

## Related Resources

> [card] [Order Transactions API](https://docs.gameball.co/api-reference/order/order-transactions.md)
>
> Complete API reference for order transactions

> [card] [Customer Activities API](https://docs.gameball.co/api-reference/customers/progress/get-customer-activities.md)
>
> Complete API reference for customer activities


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