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

# Global vs profile-scoped endpoints

> When to use a resource's global endpoint versus its profile-scoped counterpart.

Most Omneo resources are accessible through two distinct route patterns. Choosing the right one matters for both correctness and performance.

## 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

| Use case                                                 | Route to use   |
| -------------------------------------------------------- | -------------- |
| Bulk import or export                                    | Global         |
| Admin dashboard queries                                  | Global         |
| Reporting across all profiles                            | Global         |
| Loyalty app or member portal                             | Profile-scoped |
| POS or checkout integration showing a customer's balance | Profile-scoped |
| Reading or updating a single customer's records          | Profile-scoped |
| Triggers and automation actions                          | Global         |

## Endpoint pairs

The following groups each have both a global and a profile-scoped variant.

| Resource     | Global endpoint                            | Profile-scoped endpoint                                    |
| ------------ | ------------------------------------------ | ---------------------------------------------------------- |
| Transactions | [Transactions](/api-reference/transaction) | [Profile Transactions](/api-reference/profile-transaction) |
| Interactions | [Interactions](/api-reference/interaction) | [Profile Interactions](/api-reference/profile-interaction) |
| Rewards      | [Rewards](/api-reference/reward)           | [Profile Rewards](/api-reference/profile-reward)           |
| Benefits     | [Benefits](/api-reference/benefit)         | [Profile Benefits](/api-reference/profile-benefit)         |
| Points       | [Points](/api-reference/point)             | [Profile Points](/api-reference/profile-point)             |
| Redemptions  | [Redemptions](/api-reference/redemption)   | [Profile Redemptions](/api-reference/profile-redemption)   |
| Statuses     | [Statuses](/api-reference/status)          | [Profile Statuses](/api-reference/profile-status)          |

Each global endpoint overview includes a callout indicating when to use the profile-scoped route instead.

## Related

* [API Reference introduction](/api-reference/introduction)
* [Authentication](/dev-guides/core-setup/authentication)
* [Working with profiles](/dev-guides/profiles/working-with-profiles)