Listrak · OAuth Scopes

Listrak OAuth Scopes

OAuth 2.0 searched

Listrak publishes 10 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Listrak API on a user’s behalf.

Tokens are issued from https://auth.listrak.com/OAuth2/Token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Email MarketingSMS MarketingMarketing AutomationCross-ChannelRetailPush NotificationsData ImportPrivacyE-CommerceCustomer DataTransactional MessagingSegmentationProduct ReviewsMedia ManagementTwo-Way SMSRCS
Scopes: 10 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://auth.listrak.com/OAuth2/Token
Flows
clientCredentials

Scopes (10)

ScopeDescriptionFlows
Contact Contact access - read, create, update, subscribe and unsubscribe contacts on a list. clientCredentials
Event Event access - contact events used to drive triggered/behavioral sends. clientCredentials
List List access - lists, folders, IP pools, imports and the resources scoped under a list. clientCredentials
Message Message access - messages, saved messages, content, campaigns, split tests and sends. clientCredentials
Report Report access - message activity, link clickers, summaries and other reporting reads. clientCredentials
Segmentation Segmentation access - profile (segmentation) fields, field groups and field values. clientCredentials
Customer Customer access - import retail customer records. clientCredentials
Order Order access - import retail order records. clientCredentials
Product Product access - import retail product catalog records. clientCredentials
Review Review access - import product reviews and rating summaries. clientCredentials

Source

OAuth Scopes

Raw ↑
generated: '2026-08-13'
method: searched
source: https://api.listrak.com/email/swagger/docs/v1
docs: https://api.listrak.com/email
notes: >-
  Listrak declares one OAuth 2.0 client_credentials scheme per API, all issuing from
  https://auth.listrak.com/OAuth2/Token. Only the Email REST API publishes a populated `scopes` map
  in its securityDefinitions; the Data Import API declares an empty scopes map but its operations
  still carry per-operation scope requirements, so the Data scopes below were read from the
  operation-level `security` requirements rather than the flow map. The SMS and Privacy APIs declare
  the same OAuth2 scheme with an empty scopes map and their operations request no named scope - for
  those APIs access is governed by the Integration's configured access level rather than by a scope
  string. The Media API's 403 condition names a `Media` role on the token, which is the same
  permission concept expressed as a role claim rather than an OAuth scope.
  In Listrak's model a "scope" maps to the permission checkboxes on the Integration in the Listrak
  application; a token can only carry scopes the Integration was granted.
schemes:
- name: OAuth2
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.listrak.com/OAuth2/Token
  sources:
  - openapi/_original/listrak-email-openapi.json
  - openapi/_original/listrak-sms-openapi.json
  - openapi/_original/listrak-data-openapi.json
  - openapi/_original/listrak-privacy-openapi.json
scopes:
- scope: Contact
  description: Contact access - read, create, update, subscribe and unsubscribe contacts on a list.
  api: Email REST API
  flows: [clientCredentials]
  operation_count: 6
  sources: [openapi/_original/listrak-email-openapi.json]
- scope: Event
  description: Event access - contact events used to drive triggered/behavioral sends.
  api: Email REST API
  flows: [clientCredentials]
  operation_count: 9
  sources: [openapi/_original/listrak-email-openapi.json]
- scope: List
  description: List access - lists, folders, IP pools, imports and the resources scoped under a list.
  api: Email REST API
  flows: [clientCredentials]
  operation_count: 73
  sources: [openapi/_original/listrak-email-openapi.json]
- scope: Message
  description: Message access - messages, saved messages, content, campaigns, split tests and sends.
  api: Email REST API
  flows: [clientCredentials]
  operation_count: 39
  sources: [openapi/_original/listrak-email-openapi.json]
- scope: Report
  description: Report access - message activity, link clickers, summaries and other reporting reads.
  api: Email REST API
  flows: [clientCredentials]
  operation_count: 16
  sources: [openapi/_original/listrak-email-openapi.json]
- scope: Segmentation
  description: Segmentation access - profile (segmentation) fields, field groups and field values.
  api: Email REST API
  flows: [clientCredentials]
  operation_count: 11
  sources: [openapi/_original/listrak-email-openapi.json]
- scope: Customer
  description: Customer access - import retail customer records.
  api: Data Import REST API
  flows: [clientCredentials]
  operation_count: 1
  sources: [openapi/_original/listrak-data-openapi.json]
- scope: Order
  description: Order access - import retail order records.
  api: Data Import REST API
  flows: [clientCredentials]
  operation_count: 1
  sources: [openapi/_original/listrak-data-openapi.json]
- scope: Product
  description: Product access - import retail product catalog records.
  api: Data Import REST API
  flows: [clientCredentials]
  operation_count: 1
  sources: [openapi/_original/listrak-data-openapi.json]
- scope: Review
  description: Review access - import product reviews and rating summaries.
  api: Data Import REST API
  flows: [clientCredentials]
  operation_count: 2
  sources: [openapi/_original/listrak-data-openapi.json]
role_claims:
- name: Media
  description: >-
    Not an OAuth scope. The Media REST API checks for a `Media` role on the bearer token plus
    `CompanyID` / `MasterAdminID` claims; a token without them fails 403 ERROR_FORBIDDEN.
  api: Media REST API
  sources: [openapi/_original/listrak-media-openapi.json]
unscoped_apis:
- api: SMS REST API
  note: OAuth2 declared with an empty scopes map; no operation requests a named scope.
- api: Privacy REST API
  note: OAuth2 declared with an empty scopes map; no operation requests a named scope.
- api: Cross Channel REST API
  note: Fronted by an AWS API Gateway custom authorizer; no scopes published.
- api: Two-Way SMS Conversation API
  note: Fronted by an AWS API Gateway custom authorizer; no scopes published.
- api: Mobile App Push API
  note: Uses an `x-api-key` device key, not OAuth; no scopes.
cross_links:
  authentication: authentication/listrak-authentication.yml

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/listrak-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.