Customer export

GET /api/v1/customers lists your buyers page by page: the rows of the cabinet's customer list (its Clients section) — the same buyers in the same order (newest first purchase on top) and the same totals — plus the account references found on each buyer's orders and the moment the buyer last changed. Use it to fill your own database once and to keep it in sync. The partner's internal figures (commission, payout share, hold) are not in it, as in the webhooks.

The server API is for a partner whose application knows its own user: a payment is created from your server, with no button or panel on a page, and the user's state (subscriptions and purchases) is read by your own account reference. The key is the same as for the access check (API key tab in the cabinet), sent as Authorization: Bearer; the partner is identified by the key, there is no partner parameter. Rate limits are the same as for the access check: per your server's address and per key. Responses are JSON only and never cached. You can ask only about your own products and buyers: a foreign product or buyer and a non-existent one answer alike.

Request

GET https://app.norelio.eu/api/v1/customers?limit={1..100}&cursor={nextCursor}&updatedSince={date-time}
Authorization: Bearer {api key}

Every parameter is optional: limit — rows per page, 1 to 100 (default 100); cursor — the nextCursor of the previous page; updatedSince — an ISO 8601 date-time with a time zone (2026-03-14T00:00:00Z): only buyers whose own record or any of whose orders changed at or after that moment. A malformed value is 400 invalid_request.

curl -s "https://app.norelio.eu/api/v1/customers?limit=2" \
  -H "Authorization: Bearer $NORELIO_API_KEY"

curl -s "https://app.norelio.eu/api/v1/customers?limit=2&cursor=eyJ0IjoiMjAyNi0wMi0wMVQxODowMzoxMS4wMDBaIiwiayI6ImNtN2s5In0" \
  -H "Authorization: Bearer $NORELIO_API_KEY"

Response

200 OK. Each row of customers:

{
  "customers": [
    {
      "email": "buyer@example.com",
      "clientReferences": [
        "acc_10294"
      ],
      "firstPurchaseAt": "2026-03-14T09:26:53.000Z",
      "lastPaymentAt": "2026-03-14T09:26:53.000Z",
      "ordersCount": 1,
      "paidAmount": 1990,
      "refundedAmount": 0,
      "currency": "EUR",
      "updatedAt": "2026-03-14T09:26:54.000Z"
    },
    {
      "email": "second@example.com",
      "clientReferences": [],
      "firstPurchaseAt": "2026-02-01T18:03:11.000Z",
      "lastPaymentAt": "2026-03-01T18:03:12.000Z",
      "ordersCount": 2,
      "paidAmount": 1980,
      "refundedAmount": 990,
      "currency": "EUR",
      "updatedAt": "2026-03-02T10:15:00.000Z"
    }
  ],
  "nextCursor": "eyJ0IjoiMjAyNi0wMi0wMVQxODowMzoxMS4wMDBaIiwiayI6ImNtN2s5In0"
}

Paging

The response is an object with customers (the rows) and nextCursor: an opaque string to pass back as cursor for the next page, null on the last one. The order is stable — by first purchase, then by an internal id — so no buyer is repeated or skipped between pages, even when several bought at the same moment.

Keeping a copy in sync

To keep a copy in sync, remember the moment you START each run and pass it as updatedSince to the next one: a buyer who changes while you are reading the pages is then picked up by the next run. Between runs, the customer.state_changed webhook tells you about each change as it happens.

curl -s "https://app.norelio.eu/api/v1/customers?updatedSince=2026-03-14T00:00:00Z" \
  -H "Authorization: Bearer $NORELIO_API_KEY"

One buyer's subscriptions and purchases are in Customer state; changes as they happen, in Customer state notification.

Test mode

With the test key the export lists the buyers of your test orders, by the email of each paid, refunded or disputed test order, in the same shape and with the same paging; with the live key, real buyers only. Test buyers never appear in the cabinet's customer list. See Test mode.

Errors

An error from any API endpoint is JSON of one shape: an error object with code (one of the codes below) and message (a short English sentence). A 429 or 503 response carries a Retry-After header. The access check keeps its own, older error shape.

{
  "error": {
    "code": "direct_checkout_not_enabled",
    "message": "Creating payments from your server is enabled after the platform has reviewed your purchase terms. Ask support from the cabinet's Messages section."
  }
}