Scopes

Access is decided at three levels, and all three must allow a request:

1. Loops approves the scopes your application may use.
2. The merchant grants some or all of them, for the locations they choose.
3. The endpoint requires a specific scope.

Available in the developer preview

Scope	Allows
merchant:read	Read the merchant’s profile and brands
locations:read	Read locations and their channel connections
orders:read	Read orders and receive order events
events:read	List past events and request redelivery

Planned

Scope	Will allow
catalog:read / catalog:write	Read and update menus
orders:write	Accept, reject, mark ready and cancel orders
inventory:read / inventory:write	Read and update item availability
hours:read / hours:write	Read and update opening hours; pause stores

A write scope always needs its read scope. A merchant granting orders:write, for example, also grants orders:read.

Asking for more

Request additional scopes in the Loops Partners portal, with a short explanation of what you’ll use them for. After Loops approves a scope, each merchant has to approve it before it applies to their connection.