PlateIQ · OAuth Scopes

PlateIQ OAuth Scopes

OAuth 2.0 searched

PlateIQ uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyEnterprise SaasAccounts PayableInvoice AutomationPaymentsFintechRestaurantsProcurementSpend ManagementERP Integration

Scopes: 0 Flows: Method: searched

Scopes (0)

PlateIQ implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference: https://docs.ottimate.com/auth

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://docs.ottimate.com/auth.md
docs: https://docs.ottimate.com/auth
provider: plateiq
api: Ottimate API
flow: client_credentials
notes: >-
  The Ottimate OAuth2 client-credentials flow currently supports a single scope.
  The effective data an integration can reach is further constrained by the
  API User's account/company/location scoping (see account-structure/scoping).
scopes:
- name: accounts.can_access_dashboard
  description: >-
    Grants the OAuth application access to the Ottimate dashboard data surface
    for the provisioned API User. Currently the only supported OAuth scope.