Socialbakers · OAuth Scopes

Socialbakers OAuth Scopes

OAuth 2.0 searched

Socialbakers 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.

Tokens are issued from https://api.emplifi.io/oauth2/0/token.

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.

CompanyMarketingSocial MediaAnalyticsSocial Media AnalyticsSocial ListeningMarketing AnalyticsDigital Asset ManagementCustomer CareEmplifi
Scopes: 0 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.emplifi.io/oauth2/0/auth
Token URL
https://api.emplifi.io/oauth2/0/token
Flows
authorizationCode

Scopes (0)

Socialbakers 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 Emplifi (Socialbakers) Public API v3 supports OAuth 2.0 authorization code flow (Custom integration in Emplifi Settings). The published documentation does not enumerate a named OAuth scope catalog — access is governed by the integration's granted product permissions rather than request-time scopes. Recorded here so the OAuth surface is discoverable; no fabricated scope strings are included.

📄 Provider scope reference: https://api.emplifi.io/

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://api.emplifi.io/
docs: https://api.emplifi.io/
note: >-
  The Emplifi (Socialbakers) Public API v3 supports OAuth 2.0 authorization
  code flow (Custom integration in Emplifi Settings). The published
  documentation does not enumerate a named OAuth scope catalog — access is
  governed by the integration's granted product permissions rather than
  request-time scopes. Recorded here so the OAuth surface is discoverable;
  no fabricated scope strings are included.
schemes:
  - name: oauth2
    source: https://api.emplifi.io/
    flows:
      - flow: authorizationCode
        authorizationUrl: https://api.emplifi.io/oauth2/0/auth
        tokenUrl: https://api.emplifi.io/oauth2/0/token
        revocationUrl: https://api.emplifi.io/oauth2/0/token/revocation
scopes: []