# Make (/docs/integrations/make) Pull social media data into Make without writing a server. You can call SocialCrawl from any Make scenario with an HTTP module. One GET request returns structured data you can map into the next module. Setup takes three steps: store the key, add the module, branch on the answer. ## Before you start Create an API key in the dashboard under API Keys. Keep it in Make's own credential storage, not typed into a field of a scenario you share or export. Prove the key with a call that costs nothing: ```bash title="Check the key (0 credits)" curl "https://www.socialcrawl.dev/v1/credits/balance" \ -H "x-api-key: sc_your_key_here" ``` A reply with `"success": true` and your balance in `data.balance` means the key works. ## Connect Add an HTTP module that makes a request, and set these fields: | Field | Value | | ------- | ---------------------------------------------------------------------- | | URL | `https://www.socialcrawl.dev/v1/tiktok/profile/videos` | | Method | `GET` | | Query | `handle` = `mrbeast` | | Headers | `x-api-key`, with the key taken from your stored credential | Change the path and the query to call any other endpoint. Browse the [platform directory](/platforms) to find one. ## Read the answer Every response has the same shape, so one mapping works for every platform. Branch on `success`. A list puts its rows in `data.items`, and `pagination.next_cursor` is the token for the next page. ```json title="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, run the module again with `next_cursor` as the `cursor` query parameter, and stop when `has_more` is `false`. See [Pagination](/docs/pagination.md). ## When it stops Make treats an HTTP answer of 400 or above as an error, and a scenario stops on an error unless the module has an error handler. Add an error handler to the HTTP module so a refused call becomes a message instead of a silent stop. When credits run out, the answer is a 402 with `error.type` set to `INSUFFICIENT_CREDITS`. In the response body, 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. Send both to an email module so the owner sees them. Run the scenario once with a failing key to see where your module places the body. 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](/docs/errors.md) and [Rate limits](/docs/rate-limits.md). ## What a run costs It depends on the endpoint, and some endpoints are priced by what they return. [Endpoint pricing](/docs/endpoint-pricing.md) lists each one, and [Credits](/docs/credits.md) explains cache hits and refunds. Before you schedule a scenario, `GET /v1/utility/estimate` quotes a call for 0 credits. - [Errors](/docs/errors.md): Every error code, with the fix and whether to retry. - [Batch endpoints](/docs/batch.md): Many URLs in one request instead of one module run per item. - [Endpoint pricing](/docs/endpoint-pricing.md): What each endpoint costs before you schedule it.