stemp Logostemp Developer

Scopes

Permission scopes that control access to the Stemp API.

Scopes

Scopes control what actions an API token or OAuth2 app can perform. When creating an API token, select only the scopes your integration needs.

API & App Scopes

Templates

Access to wallet card templates

ScopeDescription
template:readRead templates
template:createCreate templates
template:updateUpdate templates
template:deleteDelete templates

Wallet Passes

Access to wallet passes

ScopeDescription
pass:readRead wallet passes
pass:createCreate wallet passes
pass:updateUpdate wallet passes
pass:deleteDelete wallet passes

Loyalty

Manage stamps and points

ScopeDescription
loyalty:manageManage stamps and points (add, remove, redeem)

Users

Access to end-users (customers)

ScopeDescription
user:readRead users
user:createCreate users
user:updateUpdate users

Organization

Access to organization settings

ScopeDescription
org:readRead organization
org:updateUpdate organization (name, slug, etc.)
org:deleteDelete organization

Organization Settings

Advanced organization settings

ScopeDescription
org:settings:readRead organization settings
org:settings:updateUpdate organization settings

Team Members

Access to organization members

ScopeDescription
org:members:readRead organization members
org:members:manageManage organization members (add, remove, change roles)

API Tokens

API token management

ScopeDescription
api_token:manageManage API tokens

Platform Scopes

Platform scopes are only available to installed apps (via OAuth2) and cannot be used with API tokens. They provide access to stemp infrastructure services.

ScopeDescriptionAvailable for
platform:email:sendSend emails via the stemp email infrastructure and view email logsApp only

See the Platform API documentation for details on using platform services.

Scope Contexts

Not all scopes are available in all contexts:

ContextDescriptionExample
APIAvailable for API tokens created in the consolepass:read, user:create
AppAvailable for OAuth2 app installationspass:read, platform:email:send

Some scopes are API-only (e.g., api_token:manage, app:manage) and some are app-only (e.g., platform:email:send). Most scopes are available in both contexts.

Best Practices

  • Least privilege — request only the scopes your integration needs.
  • Separate tokens — use different API tokens for different parts of your system with minimal scopes each.
  • A typical POS integration only needs pass:read, pass:create, loyalty:manage, and user:read.
  • Platform scopes should only be requested if your app actively uses platform services like email.