SocialCrawl

Use SocialCrawl with Postman

Pull social media data into Postman without writing a server.

You can call SocialCrawl from Postman with a request and one collection variable. Setup takes three steps: store the key, send a free request, send a real one.

Before you start

Create an API key in the dashboard under API Keys. Add a collection variable named socialcrawl_key and put the key in its current value, not its initial value, because the initial value syncs to Postman's cloud. Never paste the key into a request URL. Prove the key with a call that costs nothing.

Connect

Create a collection and add a request. Set the method to GET and the URL to https://www.socialcrawl.dev/v1/credits/balance. Open the Authorization tab, choose API Key, enter the key name x-api-key, set the value to {{socialcrawl_key}}, and add it to the Header.

The same request in cURL
curl "https://www.socialcrawl.dev/v1/credits/balance" \
  -H "x-api-key: sc_your_key_here"

Send it. A reply with "success": true and your balance in data.balance means the key works. Then change the URL to https://www.socialcrawl.dev/v1/tiktok/profile/videos?handle=mrbeast. Set Authorization on the collection and let each request inherit it.

Read the answer

Every response has the same shape. Branch on success. A list puts its rows in data.items, and pagination.next_cursor is the token for the next page.

Response (trimmed)
{
  "success": true,
  "data": { "items": [{ "id": "7654638524729216287" }] },
  "pagination": { "next_cursor": "sc.eyJ2Ijoy…", "has_more": true },
  "credits_used": 1,
  "credits_remaining": 99
}

To read the next page, add cursor as a query parameter with the next_cursor value, and stop when has_more is false. See Pagination.

When it stops

Add a test to the request's post-response script so a refused call shows as a failure in the Test Results tab:

Post-response script
pm.test("Status code is 200", function () {
  pm.response.to.have.status(200);
});

Postman sends no email. When credits run out, the status is 402 and the body has error.type set to INSUFFICIENT_CREDITS. Read error.message for the text and error.details.checkout_url for the link that opens checkout. When the link is absent, error.details.top_up_url opens the billing page.

Never retry a 402, because it fails until credits are added. Retry a 429 after the seconds in the Retry-After header, and a 502, 503 or 504 after a short backoff. See Errors.

What a run costs

It depends on the endpoint, and some endpoints are priced by what they return. Endpoint pricing lists each one, and Credits explains cache hits and refunds. Running a whole collection sends every request, so a collection run costs the sum of its calls. GET /v1/utility/estimate quotes a call for 0 credits.

On this page