Account Groups4

Account Settings9

Accounts16

Ad Accounts47

Ad Audiences7

Ad Campaigns50

Ad Creatives17

Ad Insights11

Ad Library1

Ad Targeting5

Analytics25

API Keys4

Blogs10

Broadcasts10

Business Agent55

Calls3

Comment Automations6

Comments15

Connect57

Connected Apps2

Contacts7

Conversions14

Custom Fields6

Discord24

GMB Attributes3

GMB Food Menus2

GMB Location Details2

GMB Media3

GMB Place Actions4

GMB Reviews5

GMB Services2

GMB Verifications4

iMessage17

Inbox Analytics7

Instagram5

Invites1

Lead Gen8

LinkedIn Mentions1

Logs1

Media1

Mentions2

Messages16

Messaging Ads3

Phone Numbers30

Posts10

Product Catalogs19

Products3

Profiles5

Queue6

Reach and Frequency4

Reddit Search2

Reviews3

Sequences10

Slack1

SMS22

Tools1

Tracking Tags10

Twitter Engagement8

Usage6

Users2

Validate4

Verify3

Voice18

Webhooks7

WhatsApp46

WhatsApp Calling16

WhatsApp Flows15

WhatsApp Phone Numbers16

WhatsApp Sandbox3

WhatsApp Templates1

Workflows14

Webhooks

Webhook Events55

Analytics

Analytics changed since a cursor

Cursor feed of the analytics snapshots that CHANGED, across every account you can read, in one paginated stream. Built for integrations that would otherwise call GET /v1/analytics once per connected account. Each page carries changes from many accounts at once, so your call count scales with how much actually changed rather than with how many accounts you have. Measured against a fleet of roughly 1,600 connected accounts: about 1,599 per-account analytics calls an hour became about 205 delta calls an hour, a 7.8x reduction.

Bootstrap once, then stay in sync. Take the cursor FIRST: call this endpoint with NO cursor and it answers with an empty data array plus the feed's current position in nextCursor. Then load your baseline from GET /v1/analytics, the historical endpoint, because this one is a rolling 7-day change log and cannot replay history. Then resume from the cursor you took before the baseline. Taking the cursor afterwards instead drops every change that lands while the baseline is loading: it is in neither the row you already read nor the feed you resume behind it. The overlap this order creates is safe, because metrics are absolute values rather than increments, so draining it leaves every post on its newest value. nextCursor is present on every response, empty pages included, so you always have something to advance with.

Ordering. Entries come back oldest first, in the order the feed received them. That order is NOT syncedAt: syncedAt is stamped when an account's sync cycle started, and a slow cycle writes its rows after a faster cycle that started later, so syncedAt can go backwards between consecutive entries. Do not sort, filter or resume on it. The cursor is the only stable position, and it is opaque: pass it back verbatim, and do not parse, construct or compare cursors.

hasMore: false does not mean the feed ended. This stream has no end and nextCursor is never null. hasMore: true means more changes are already waiting, so call again straight away. hasMore: false means you are caught up: keep the cursor and poll again on your normal interval.

The newest changes settle before they are served. The feed deliberately holds back its last few seconds of writes, so that a row can never become visible behind a cursor you have already advanced past. A read issued the instant an analytics.synced webhook lands will therefore often return an empty page for that account. Do not read an empty page as "nothing changed": poll again with the SAME cursor you last used rather than advancing.

Repeats inside one instant. A sync cycle occasionally records the same post twice at the same feed position. When that happens the feed delivers one of those rows, not both. Measured over a day of production traffic, about 1.3% of rows fall in such a group and 99.4% of those groups are identical rows, so this is far more often deduplication than loss. Metrics are absolute values rather than increments, so a later entry for the same post supersedes an earlier one.

Retention is 7 days. Changes older than that leave the feed. A cursor older than 6 days is rejected with a 400 (a day of margin, because expiry is lazy). Recover the same way you bootstrapped: take a fresh cursor from a call to this endpoint with no cursor, then re-load from GET /v1/analytics, then resume from that cursor. A consumer that polls at least daily never reaches this.

Pairs with the analytics.synced webhook, so changes can be read on notification instead of on a timer. That event carries no cursor of its own: keep using the nextCursor this endpoint gave you.

Requires the same analytics access as GET /v1/analytics, and shares the stricter per-second rate-limit window applied to analytics endpoints.

get/v1/analytics/delta

Query parameters

cursorstring

Opaque cursor from a previous response's nextCursor. Omit it to start from now: the response is then an empty page carrying the feed's current position. Rejected with a 400 when malformed, or when older than the retention window.

limitinteger

Page size. Out-of-range values are a 400, never a silent clamp.

platformstring

Filter to a single platform (for example "youtube"). Omit for every platform.

profileIdstring

Filter by profile ID (default "all"). Must be a valid profile ID or "all".

Response

One page of changed analytics

nextCursorstring required

Cursor to send on the next call. ALWAYS present, including on an empty page, so you always have something to advance with, and it never moves backwards. Opaque: pass it back verbatim, and do not parse, construct or compare cursors.

hasMoreboolean required

True when more changes are already waiting past nextCursor, so call again immediately. False means you are caught up: keep nextCursor and poll again later. This feed never ends, so hasMore: false does NOT mean nextCursor is null.

Example response

{
  "data": [
    {
      "platform": "youtube"
    }
  ],
  "nextCursor": "v1.WyIyMDI2LTA5LTAxIDE3OjEyOjA0IiwiNjVmMWMwYTllMmI1YWYwMDEyYWIzNGNkIl0"
}

Changes

Changed in 7 of the 56 revisions of this API.35

Sep 25, 20262c04683ce69416See the full diff
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Sep 21, 2026339f59df69dd1See the full diff
- ○
  added the required property /// to the response with the status
  response-required-property-added
Sep 17, 2026be448f13ecdc3See the full diff
- ○
  added the required property /// to the response with the status
  response-required-property-added
- ○
  added the required property /// to the response with the status
  response-required-property-added
- ○
  added the required property /// to the response with the status
  response-required-property-added
Sep 16, 20263e6ddf2a99ea4See the full diff
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
Sep 15, 20260dba7d004d758See the full diff
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
Sep 10, 2026e70ed06e71502See the full diff
- ○
  added the required property /// to the response with the status
  response-required-property-added
- ○
  added the required property /// to the response with the status
  response-required-property-added
Sep 2, 20263f632ccead881See the full diff
- ○
  endpoint added
  endpoint-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history