Authority & scopes
A request selects a resource. It never grants itself permission to access it.
Product-owned authority
Partner assignments constrain the allowed product, operation or dataset, retailer location, and purpose. Caller-supplied tenant, store, customer, or resource identifiers never create authority. Only send selectors that exist in the selected operation’s schema.
The reference shows each operation’s domain, authentication profile, and minimum data class. Required and optional customer-subject scopes are rendered separately when the contract declares them.
Data classes
- public: no tenant or customer data.
- partner_operational: operational facts within an approved partner assignment.
- customer_personal: personal data subject to the operation’s customer-controlled grant boundary.
- customer_sensitive: separately consented sensitive facts with purpose and retention controls.
- restricted: internal material that is not a public partner response.
Minimize what you keep
Request only the fields and scopes needed for your purpose. Customer grants can expire or be revoked. An earlier successful response is not permission for another customer, purpose, or future request.