KonbiniAPI · OAuth Scopes
KonbiniAPI OAuth Scopes
OAuth 2.0
probed
KonbiniAPI publishes 5 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the KonbiniAPI API on a user’s behalf.
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.
Social MediaInstagramTikTokXRedditLinkedInActivityStreams 2.0Web ScrapingData ExtractionPublic DataInfluencer MarketingSocial ListeningCreator ToolsMCPAgent SkillsAgentsA2A
Scopes: 5
Flows:
Method: probed
Scopes (5)
| Scope | Description | Flows |
|---|---|---|
| api_key | Authorizes the MCP server to call KonbiniAPI on the account's behalf using its API key, and to spend that account's credits. This is the only scope that grants data access, and it grants all of it — there is no per-platform or read-only subdivision. | |
| offline_access | Issues a refresh token so an agent can keep calling without the user present. Required for unattended automation (Zapier, n8n, Make, Pipedream). | |
| openid | Standard OIDC scope; requests an ID token identifying the signed-in KonbiniAPI account. | |
| profile | Standard OIDC scope; releases name, picture, given_name and family_name claims. | |
| Standard OIDC scope; releases the email and email_verified claims. |
📄 Provider scope reference: https://docs.konbiniapi.com/reference/mcp/overview
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.