RubiConnect · OAuth Scopes
RubiConnect OAuth Scopes
OAuth 2.0
probed
RubiConnect 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.
CPaaSCommunications APIsBusiness MessagingRCSWhatsApp BusinessSMSMarketing & CampaignsConversational AIMCPAI Agents
Scopes: 0
Flows:
Method: probed
Scopes (0)
RubiConnect 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.
The REST OpenAPI declares only apiKey + http bearer security schemes (no oauth2 block), so no scopes are derivable from the spec. OAuth 2.0 is used by the hosted MCP server and is described only in the served authorization-server metadata, which advertises a single scope.
The REST OpenAPI declares only apiKey + http bearer security schemes (no oauth2 block), so no scopes are derivable from the spec. OAuth 2.0 is used by the hosted MCP server and is described only in the served authorization-server metadata, which advertises a single scope.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.