beehiiv · OAuth Scopes
beehiiv OAuth Scopes
OAuth 2.0
searched
beehiiv 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.
NewsletterCreatorEmailSubscriptionPublishingMediaAdvertising
Scopes: 0
Flows:
Method: searched
Scopes (0)
beehiiv 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.
derive-oauth-scopes.py found nothing: the published OpenAPI declares only an HTTP bearer securityScheme and no oauth2 flows, so the scope surface exists only in the documentation and in the per-operation badges. This file is the searched reconciliation of both. The MCP server at mcp.beehiiv.com uses a separate, coarser scope vocabulary (read, write) — see mcp/beehiiv-mcp.yml.
derive-oauth-scopes.py found nothing: the published OpenAPI declares only an HTTP bearer securityScheme and no oauth2 flows, so the scope surface exists only in the documentation and in the per-operation badges. This file is the searched reconciliation of both. The MCP server at mcp.beehiiv.com uses a separate, coarser scope vocabulary (read, write) — see mcp/beehiiv-mcp.yml.
📄 Provider scope reference: https://developers.beehiiv.com/oauth2