The Mobile First Company · OAuth Scopes
The Mobile First Company OAuth Scopes
OAuth 2.0
searched
The Mobile First Company 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.
CompanyCommunicationTelephonyVoiceSMSCRMArtificial IntelligenceMCPWebhooksSmall Business
Scopes: 0
Flows:
Method: searched
Scopes (0)
The Mobile First Company 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.
Scopes are attached to Allo API keys (created in Settings > API) and to OAuth clients / the MCP server. The 19 scopes below are advertised verbatim in the OAuth authorization-server metadata; WEBHOOKS_READ_WRITE, BILLING and PARTNER are documented in the API-key scope reference / partner endpoints but are not listed in scopes_supported.
Scopes are attached to Allo API keys (created in Settings > API) and to OAuth clients / the MCP server. The 19 scopes below are advertised verbatim in the OAuth authorization-server metadata; WEBHOOKS_READ_WRITE, BILLING and PARTNER are documented in the API-key scope reference / partner endpoints but are not listed in scopes_supported.
📄 Provider scope reference: https://help.withallo.com/en/v2/api-reference/guides/authentication