List a customer group's customers
The customers in one group, paged. This is where membership lives, and the group resource deliberately carries no members array: a group with 50,000 buyers would otherwise serialise 50,000 ids into one row of a list response, on a resource whose page cap says nothing about how many people it names. THE OTHER HALF OF THE B2B SYNC PATH is GET /price-lists//customer- groups. Together they are price list to groups to customers, which is how a wholesale integration learns which buyers get which negotiated prices. Neither leg is useful without the other. THE ROWS ARE THE SAME CUSTOMER RESOURCE /customers serves, with the same fields and the same nullability. One customer has one shape whichever route found them, so a client can hand a row here to the same parser it uses there. CURSOR ONLY, no offset and no total. A merchant tagging customers inserts rows into this membership continuously, and an offset walk drops or repeats one on every page turn; here a dropped row is a buyer who silently stops receiving wholesale prices. AN EMPTY GROUP IS A 200 WITH AN EMPTY PAGE. A group id that does not exist, or belongs to another store, is a 404. The two are distinguished deliberately: a 200 for a mistyped id would record “this tier has no buyers” and apply retail prices to everyone in it. MEMBERSHIP IS READ-ONLY HERE. Nothing on this API adds or removes a member, for the reason the group family publishes no writes at all: a group’s price-list targeting rows cascade with it, and a price list left untargeted applies to EVERY customer.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Path Parameters
Query Parameters
Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
1 <= x <= 100The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.