Resolve a handle, list its posts, then capture the engagement on each one. The same chain runs on every network, and one batch call returns current stats for up to 100 mixed-platform post URLs.
Handle in, posts and numbers out
A creator analytics API resolves a public handle and returns its profile, its posts and the engagement on each post as structured data. SocialCrawl runs the same resolve then list chain on every network across 46 platforms, and a single batch call returns current stats for up to 100 mixed-platform post URLs, with failed URLs refunded.
Every one of these is a shipped pattern, not a roadmap item. The endpoint chain under each card is the actual call sequence.
One handle in, the profile out, then its recent posts with engagement attached. This is the most repeated chain on the whole API, and it behaves the same way whichever network you point it at.
profile -> profile/posts -> post/statsSend up to 100 mixed-platform post URLs in a single request and get current engagement for each. You are charged per successful URL and dead links are refunded. A roster that used to take hundreds of calls each morning collapses into two.
prism/post-stats (100 URLs per call)Resolve the handle, then page through the video feed with cursors. Re-run it on your own cadence to build a per-post time series rather than a single reading.
tiktok/profile -> tiktok/profile/videosChannel record first, then videos and shorts, so you can see publishing cadence and format mix next to the engagement on each upload.
youtube/channel -> channel/videosWalk an account's entire post history with cursors when the last page is not enough. Backfill once, then switch to incremental pulls.
instagram/profile/posts/full (archive)Send up to 50 platform and handle pairs and get one canonical author record per row. Handles that fail to resolve are refunded, so a messy input list is not an expensive one.
prism/profiles (one handle, many networks)Four calls cover the whole job. Two of them are batch endpoints, which is what makes a daily roster affordable.
Reads are priced in credits. Batch endpoints charge per successful row, and dead links or unresolvable handles are refunded automatically.
GET /v1/instagram/profileHandle in, canonical profile out, including follower counts and the account identifiers the later calls need.
1 creditGET /v1/instagram/profile/postsPage through the account's posts with cursors. Each post carries its engagement at the moment of capture.
1 credit per pagePOST /v1/prism/post-statsUp to 100 post URLs from mixed platforms in one request, returning current engagement per URL. This replaces the per-post loop.
1 credit per successful URLGET /v1/prism/profilesUp to 50 platform and handle pairs in one request, returning one canonical author per row for your whole tracked roster.
1 credit per resolved handleEach of these is a live lane on the same key. Follow a link to see that platform's full endpoint surface.
Most teams either connect the official APIs, which only reach accounts that authorise them, or run one scraper per network. Here is what changes.
| Capability | SocialCrawl | Typical setup |
|---|---|---|
| Whose accounts | Any public account, including competitors and creators you have not signed yet. | Only accounts that connect and authorise the tool first. |
| Batch capture | Up to 100 mixed-platform post URLs per request, charged per successful URL. | One request per post, so a daily roster becomes hundreds of calls. |
| Failed lookups | Dead links and unresolvable handles are refunded automatically. | Billed on attempts, including the ones that return nothing. |
| Metric honesty | Documented per platform, so you know which numbers a network exposes for accounts you do not own. | A single metrics promise that quietly breaks on half the networks. |
| Coverage | One key covers creator accounts across 46 platforms. | One integration per network, each with its own auth and response shape. |
| Pricing model | Credit packs that never expire, charged per call, so a backfill is a one-off cost. | Monthly seats or tiers priced by tracked creator count. |
A creator analytics API turns a public handle into structured records: the profile, the posts and the engagement on each post. It replaces the dashboards sold per seat with a feed you can store, join against your own data and chart however you like.
Followers, following, post counts, and per-post likes, comments and timestamps across the networks. Views and shares are returned where the platform exposes them, which on Instagram means video formats such as reels. Instagram never exposes saves to any provider, and story metrics are owner only, so no API can return them for someone else's account.
Yes. Everything here reads public data, so the account you track does not need to connect anything or know you are tracking it. Watching a competitor set on the same schedule as your own accounts is one of the most common uses of the API.
Use the batch stats endpoint. Send up to 100 post URLs from mixed platforms in one request and store what comes back with your own capture timestamp. Failed URLs are refunded, so a roster with dead links does not cost you for them.
Yes. The full archive endpoint paginates an account's entire post history with cursors. Deep archives run to thousands of records, so backfill once, keep the cursor position, then switch to incremental pulls for everything after that.
Pull a set of recent posts, exclude the pinned ones so an old hit does not distort the average, then divide the engagement on the remainder by follower count. A common refinement is to weight shares more heavily than likes, since shares are harder to inflate.
Per call. Reads draw from never-expire credit packs rather than a per-creator subscription, so tracking 20 accounts and tracking 2,000 differ in volume, not in licence. Signup includes 100 free credits and no card is required.
Ask AI about SocialCrawl
100 free credits on signup. No card, no per-creator pricing, no sales call.
curl -G "https://socialcrawl.dev/v1/instagram/profile/posts" \
-H "x-api-key: $SOCIALCRAWL_API_KEY" \
--data-urlencode "handle=natgeo"curl -X POST "https://socialcrawl.dev/v1/prism/post-stats" \
-H "x-api-key: $SOCIALCRAWL_API_KEY" \
-H "content-type: application/json" \
-d '{"urls":["https://www.instagram.com/p/ABC/","https://www.tiktok.com/@user/video/123"]}'Both calls run against live data. Swap the key and the handle and they work as written.