SocialCrawl

Which call do I use for a profile or a post?

Profile or profile plus posts, the 1-credit or 5-credit Instagram call, a raw or a full list, and which comment call.

Start with the table, then read the section for the job you have. Costs are per successful call, and failed and cached responses are not charged. Every price is the endpoint's own entry in Endpoint pricing.

Quick comparison

The jobThe callUse another when
An account's stats/v1/tiktok/profileYou also want recent posts: use /v1/tiktok/profile/full
An Instagram post/v1/instagram/postYou need the share count: use /v1/instagram/post/stats
A page of posts or reels/v1/instagram/profile/postsYou need engagement on every item: use /v1/instagram/profile/posts/full
Comments on a post/v1/tiktok/post/commentsYou want the whole tree: use /v1/prism/comments
Fresh numbers on URLs you hold/v1/prism/post-statsYou hold one URL only: use that platform's post call

The table names the call and the exception. Each section below carries the current credit cost of every row.

Profile, or profile plus posts?

profile is one upstream call that returns the unified author object. profile/full is a composite: the same profile, the account's recent posts, and computed analytics in one call, so you skip the follow-up list request.

Your goalUse this endpointWhyCredit cost
Just the profile object/v1/tiktok/profileOne call, author only1cr (LinkedIn 5cr)
Profile + recent posts + analytics in one call/v1/tiktok/profile/fullComposite, no follow-up list call5cr

If you already hold the handle and only need counts, use plain profile. If your next step is always "and their recent posts", profile/full is one call instead of two.

Instagram: the 1-credit or the 5-credit endpoint?

Instagram is served by two upstreams. The 1-credit endpoints cover the public surface. The 5-credit endpoints return data the public surface hides: share counts, follower and following lists, stories, tagged posts, locations, and comment lists.

Your goalUse this endpointWhyCredit cost
Profile, posts, reels, single post/v1/instagram/profile, /v1/instagram/profile/posts, /v1/instagram/profile/reels, /v1/instagram/postPublic surface, cheapest upstream1cr
A post's share count/v1/instagram/post/statsThe share count for any one post URL5cr
Followers / following / similar accounts/v1/instagram/followers, /v1/instagram/following, /v1/instagram/similarLists the public surface does not expose5cr
Active stories/v1/instagram/storiesEphemeral data, second upstream only5cr
Comments on a post/v1/instagram/post/commentsComment list, second upstream only5cr
Posts by hashtag/v1/instagram/search/hashtagHashtag feed, every ranking pages1cr

The trap is /v1/instagram/post (1cr) versus /v1/instagram/post/stats (5cr). The cheap one returns everything about a post except the share count. Reach for post/stats only when you specifically need shares.

Note also /v1/instagram/basic-profile (1cr), a slimmer profile payload than /v1/instagram/profile.

A raw list, or the enriched /full list?

For Instagram posts and reels you can pull a plain page or the enriched composite. The plain list is one fast, cheap page. The /full variant fans out per item to attach views, likes, comments, and per-item share counts where available.

Your goalUse this endpointWhyCredit cost
One page of a user's reels/v1/instagram/profile/reelsFast, cursor-paginated1cr
Reels with views, likes, comments, share counts/v1/instagram/profile/reels/fullComposite, per-reel enrichment5cr per page of ~12 (5-25cr with limit)
One page of a user's posts/v1/instagram/profile/postsFast, cursor-paginated1cr
Posts with views, likes, comments, share counts/v1/instagram/profile/posts/fullComposite, per-post enrichment5cr per page of ~12 (5-25cr with limit)
Facebook reels with exact engagement/v1/facebook/profile/reels/fullComposite, per-reel enrichment5cr per page of 10 (5-25cr with limit)

Paging a long back catalogue without needing per-item share counts is far cheaper on the plain list. Use /full when you need engagement on every item and want one call.

The two meanings of limit

limit does two different jobs on this API, and on the /full composites it is the one that moves the price.

  • Page size. On most list endpoints limit caps a single upstream page and maps to that upstream's native parameter (Naver display, GitHub per_page, and so on). One call, one page, one charge. This is the behaviour Pagination documents.
  • Collect-until-N. On a small set of endpoints limit instead tells the endpoint to keep walking upstream pages itself until it has that many unique items, deduping server-side. You are billed per page or window actually consumed, and the unused budget is refunded. Omit limit and the budget is one page, so the price is unchanged.

The collect-until-N endpoints and their ceilings:

Endpointlimit maxWalk unitCost
/v1/instagram/profile/reels/full50page of ~125cr per page, 5-25cr
/v1/instagram/profile/posts/full50page of ~125cr per page, 5-25cr
/v1/facebook/profile/reels/full50page of 105cr per page, 5-25cr
/v1/threads/search100date window of ~151cr per window, 1-7cr
/v1/prism/commentsn/acomment page2-200cr (Instagram flat 5cr)

So /v1/instagram/profile/reels/full?handle=nike&limit=50 is five pages, not one, and costs 25 credits rather than 5. Budget from the range, not the floor.

Facebook: fill the rows, or fetch them yourself?

Four Facebook list endpoints take an optional include parameter that joins every row on the page to its own detail record inside the same call. Without the parameter the call is unchanged and costs 1 credit. With it, the endpoint holds 1 credit per row, keeps only the rows a fresh lookup actually filled, and refunds the rest, which is why the price below is a range rather than a figure. Rows already in cache are filled for free, and a row Facebook publishes no number for stays null and costs nothing.

Page posts and photos

Your goalUse this callWhyCredit cost
One page of a page's posts/v1/facebook/profile/postsText, reactions, comments and publish time. No share count, and no view count on reels1cr
The same posts with share counts, plus exact reel views and duration/v1/facebook/profile/posts?include=engagementJoins each of the 3 rows on the page to its own post record in the same call1-4cr
A page's photos with author, likes, comments, shares and publish date/v1/facebook/profile/photos?include=detailsThe photo listing carries none of those, so all 8 rows on the page are joined1-9cr

include=engagement is the move when you are making the list call anyway: the page plus its 3 rows is at most 4 credits in one round trip, where fetching the same three permalinks yourself is the page call plus three /v1/facebook/post calls, at the same 4 credits but four round trips and your own permalink bookkeeping. Two other routes to the same numbers are still the better answer in their own cases.

Your situationUse this callWhyCredit cost
You are already fetching the page's feed and want share counts on it/v1/facebook/profile/posts?include=engagementOne round trip, and a row already cached or without a public share count is free1-4cr
You already hold post URLs and want current numbers on them/v1/prism/post-statsUp to 100 URLs, any platform, in one POST, with dead links refunded1cr
You want reels with exact views, likes, comments and shares/v1/facebook/profile/reels/fullMerges per-reel engagement server-side for a whole page of 105cr per page of 10 (5-25cr with limit)

Reach for /v1/prism/post-stats when the URLs are already in your database and you are refreshing numbers rather than reading a feed, since it takes up to 100 of them at once, across platforms, and refunds the dead ones. Reach for /v1/facebook/profile/reels/full for reels specifically: a flat 5 credits buys a page of 10 reels with exact engagement on every one, which joining ten rows one at a time could not beat.

The two event lists

Your goalUse this callWhyCredit cost
One page's own events/v1/facebook/profile/eventsTitle, link, start time, venue, city, time line and the cancelled, past and online flags1cr
Those events with description, address, coordinates, hosts, cover and RSVP counts/v1/facebook/profile/events?include=detailsThe page's listing carries none of those, so all 8 rows on the page are joined1-9cr
What is on in a city/v1/facebook/eventsSame row shape, and this feed does carry the cover image and the RSVP counts1cr
Those city events with description, address, city, coordinates and hosts/v1/facebook/events?include=detailsAt most 12 events on a page, so the ceiling is higher than the page feed's1-13cr

Both event lists carry the rendered time line, the venue, the city, the start timestamp and the cancelled, past and online flags on post.ext.event with no token at all. What include=details adds is the description, the street address, the coordinates, the hosts, the category, the privacy and the attendance count, plus the cover image and the RSVP counts on a page's own event list, which never carried either. An event's end time and ticket link stay null either way, because Facebook does not publish them for these events.

The join adds 2 to 7 seconds to a page of posts whose rows are not already cached, 2 to 8 seconds to a page of photos, 2 to 6 seconds to a page's own events, 2 to 8 seconds to a city feed of events, never more than 12, and nothing when the rows are cached. Every joined response carries a hydration block itemising the rows, the lookups, the cache hits, the credits held and kept, and the milliseconds, so you can read back exactly what you paid for.

Which comment endpoint?

Four endpoints touch comments. The distinction is one page versus the whole tree, and a single comment versus a batch re-check.

Your goalUse this endpointWhyCredit cost
One page of top-level comments/v1/tiktok/post/comments, /v1/reddit/post/commentsCursor-paginated single page1cr (Reddit 5cr, Instagram 5cr)
Every comment on a post, replies nested/v1/prism/commentsServer-paginated to completion, one call2-200cr (metered by comment pages; Instagram flat 5cr)
Look up one comment by URL or id/v1/tiktok/comment, /v1/instagram/commentSingle-comment resolver2-6cr (Instagram 5-15cr)
Re-check up to 25 known comments/v1/prism/comment-lookupBatch, failed items refunded2cr

Use the per-platform post/comments when one page is enough and you want to control paging.

Freshening numbers at scale

When you already hold post or comment URLs and want current numbers, the batch endpoints re-check many at once and refund the ones that fail.

Your goalUse this endpointWhyCredit cost
Current engagement on one post/v1/tiktok/postSingle post detail1cr
Current engagement on up to 100 mixed-platform posts/v1/prism/post-statsOne POST, per-URL results, failed URLs refunded1cr
Re-check up to 25 known comments/v1/prism/comment-lookupOne POST, per-item results, failed items refunded2cr