Entergram · OAuth Scopes
Entergram OAuth Scopes
OAuth 2.0
searched
Entergram 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.
MessagingNotificationCommunicationsCRMTelegramCustomer SupportTicketingSalesMCPWebhook
Scopes: 0
Flows:
Method: searched
Scopes (0)
Entergram 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.
Entergram's REST API authenticates with a workspace-scoped X-API-Key header and declares no OAuth flow in its OpenAPI. OAuth2 (authorization_code + PKCE) is used by the hosted MCP server; the scope set below is served verbatim in the RFC 8414 authorization-server metadata and RFC 9728 protected-resource metadata at mcp.entergram.com, and echoed in the 401 WWW-Authenticate challenge from the MCP endpoint. Scopes are workspace-granular read/write pairs plus OIDC scopes.
Entergram's REST API authenticates with a workspace-scoped X-API-Key header and declares no OAuth flow in its OpenAPI. OAuth2 (authorization_code + PKCE) is used by the hosted MCP server; the scope set below is served verbatim in the RFC 8414 authorization-server metadata and RFC 9728 protected-resource metadata at mcp.entergram.com, and echoed in the 401 WWW-Authenticate challenge from the MCP endpoint. Scopes are workspace-granular read/write pairs plus OIDC scopes.
📄 Provider scope reference: https://www.entergram.com/help-center/security-developers/claude-mcp-connector
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.