generated: '2026-07-21'
method: searched
source: https://api.emplifi.io/
docs: https://api.emplifi.io/
authentication:
  styles: [http-basic, oauth2-authorization-code]
  ref: authentication/socialbakers-authentication.yml
request_model:
  note: >-
    Metrics and posts queries are issued as POST requests carrying a JSON body
    (profiles, metrics, dimensions, date_start, date_end). Reference data
    (profiles, labels, queries) is retrieved with GET. Content-Type is
    application/json; charset=utf-8.
  consumer_header: x-api-consumer
pagination:
  style: cursor
  applies_to: posts endpoints (per-network posts/videos/tweets)
  response_fields: [next, remaining]
  page_size_max: 100
  note: >-
    Posts endpoints return up to 100 items per request with `next` (cursor to
    the following page) and `remaining` (items left) in the response.
idempotency:
  supported: false
  note: >-
    The API documents no idempotency-key header. Read/metrics operations are
    naturally idempotent (POST-as-query); Assets write operations
    (create/edit/delete/archive/restore) are not documented as idempotent.
error_envelope:
  shape: '{ "success": false, "errors": [ { "code": <int>, "errors": [<string>] } ] }'
  success_flag: success
  format: custom-json
  ref: errors/socialbakers-error-codes.yml
  note: Not RFC 9457 problem+json; errors are surfaced in a `success`/`errors` envelope.
success_envelope:
  shape: '{ "success": true, "header": [...], "data": ... }'
versioning:
  scheme: uri-path
  current: '3'
  ref: lifecycle/socialbakers-lifecycle.yml
rate_limiting:
  ref: rate-limits/socialbakers-rate-limits.yml
  note: Hourly account (1000) and user (500) quotas; 429 on exceed.
metadata:
  networks: [facebook, instagram, twitter, youtube, linkedin, pinterest, tiktok, snapchat]
event_surface:
  webhooks: false
  asyncapi: false
  checked: '2026-08-13'
  note: >-
    The Emplifi Public API v3 — the Socialbakers-lineage API this profile covers
    — publishes NO webhook, streaming or event surface: it is poll-only, and the
    only push-shaped mechanism in the docs is scheduled export. Emplifi does
    document webhooks, but only for Emplifi Ratings & Reviews, which is the
    acquired TurnTo product served from api.turnto.com and documented at
    developers.turnto.com. That is a different product line on a different host
    from a different acquisition, so it is deliberately NOT recorded as an event
    surface for this API and no `Webhooks` pointer is emitted here.
  evidence:
  - {url: 'https://docs.emplifi.io/platform/latest/home/emplifi-ratings-and-reviews-webhooks.md', status: 200, note: 'Ratings & Reviews (TurnTo) webhooks — different product line'}
  - {url: 'https://api.emplifi.io/', status: 200, note: 'Public API v3 reference — no webhook/event section among its 129 anchors'}