GET
/
v2
/
customers
/
{merchant_id}
/
transactions
cURL
curl --request GET \
  --url https://api.loyaltylion.com/v2/customers/{merchant_id}/transactions \
  --header 'Authorization: Bearer <token>'
{
  "transactions": [
    {
      "id": 123,
      "customer": {
        "id": 123,
        "merchant_id": "<string>",
        "email": "<string>",
        "points_pending": 123,
        "points_approved": 123,
        "points_spent": 123
      },
      "points_approved": 123,
      "points_pending": 123,
      "created_at": "<string>",
      "resource": "activity",
      "activity": {
        "id": 123,
        "merchant_id": "<string>",
        "value": 123,
        "state": "pending",
        "customer": {
          "id": 123,
          "merchant_id": "<string>",
          "email": "<string>",
          "points_pending": 123,
          "points_approved": 123,
          "points_spent": 123
        },
        "created_at": "<string>",
        "rule": {
          "id": 123,
          "name": "<string>",
          "title": "<string>"
        },
        "flow": {
          "id": 123,
          "journey_id": 123,
          "name": "<string>",
          "block_id": "<string>"
        },
        "resource": null
      }
    }
  ],
  "cursor": {
    "prev": "<string>",
    "next": "<string>"
  }
}

Retrieve a list of transactions for this customer.

Unlike activities and rewards, transactions are immutable. For example, if an activity is triggered and then voided, it will typically create two transactions, one which adds points and a second which removes points.

Authorizations

​
Authorization
string
header
required

An API key linked to a Program in LoyaltyLion, with a set of permissions (scopes). API keys can be created manually, or acquired through an OAuth2 flow. The API key should be provided as a Bearer token in the Authorization header

Path Parameters

​
merchant_id
string
required

The ID of the customer in your platform or ecommerce store

Query Parameters

​
type
enum<string>
default:json

The format of the response

Available options:
csv,
json
​
since_id
integer

Return only resources whose id is after the specified id

Required range: x >= 0
​
limit
integer
default:100

Max number of resources to return per request

Required range: 1 <= x <= 500
​
cursor
string

Fetch another page of results using a cursor returned in a previous response

​
created_at_min
string

Return only transactions created on or after the specified ISO 8601 datetime string

​
created_at_max
string

Return only transactions created before the specified ISO 8601 datetime string

Response

200
application/json

200

The response is of type object.