Social Data API overview

Give the API a public post URL or a creator's handle and it performs a server-side lookup: how the post is performing, who commented on it and who the creator is. Nobody is redirected or asked to sign in.

That is the difference from Vouch, which verifies private data by asking the user to prove it from inside their own account. Most creator campaigns use both: Vouch to confirm the handle is theirs and the audience is real, this API to read what happened on the post.

What you can look up

Post lookups take the post URL, and profile lookups take the platform and the handle. There is nothing to create first.

What counts as a data lookup

A data lookup is a call that reads the platform. Every lookup is live: the API reads the post or profile when you call, passes the result straight to your app and keeps no copy:

Calling again is how you get newer data.

One call is one lookup, however many comments it returns; a page of comments is one call. A lookup that fails does not count. GET /auth/usage reports your usage by token, route and day.

Getting access

Book a call (opens in a new tab) to get an API token and your base URL. The call is also where lookup volumes and pricing are agreed.

These credentials are separate from Vouch: an API token here instead of a customerId.

Engagement verification

On top of the lookups, the API can confirm that a specific registered creator commented on or liked a post, track that as an attempt and notify your webhook. It works through campaigns, which keep a stored copy of a post's comments, metrics and Instagram likers. It is available on request; ask about it on the call. See Engagement verification.