The two patterns
Global endpoints operate on all records of a resource across the entire tenant. They are designed for integration work: importing data, running bulk operations, querying across all profiles, or triggering admin-level updates. Example:GET /v3/transactions returns all transactions in the tenant.
Profile-scoped endpoints operate on records belonging to a specific profile. They are designed for customer-facing work: building loyalty UIs, profile screens, membership apps, or any context where you already hold a profile identifier.
Example: GET /v3/profiles/{id}/transactions returns transactions for one profile.
Both patterns expose the same underlying data. The difference is scope, access pattern, and the assumptions built into the response shape.
When to use each
Endpoint pairs
The following groups each have both a global and a profile-scoped variant.
Each global endpoint overview includes a callout indicating when to use the profile-scoped route instead.