prism

Up to 5,000 profiles or post URLs in one background job, at the batch endpoints' own prices.

Runs a batch too large for one call in the background. POST a JSON body { "endpoint": "prism/profiles" | "prism/post-stats", "items": [...] } with 1 to 5,000 items in the item shape that endpoint takes ({ platform, handle, custom_id?, stop_at_id? } or { url, custom_id? }). The job is split into chunks of 50 (25 with include: "posts") and each chunk runs exactly as a call to that endpoint would: same sources, same rows, same per-row price. The response is 202 with job_id; read GET /v1/prism/jobs/{job_id} for status and results. Every item is validated before anything is held, and a bad item is a 400 that names its position. Add webhook: { url } (public https) to be told when the job completes: the 202 returns webhook.secret once, and each delivery is signed in the x-socialcrawl-signature header as t=<unix>,v1=<hex HMAC-SHA256 of "<t>.<body>">. The webhook carries the summary and a results URL, not the rows. An Idempotency-Key header returns the existing job instead of a second one.

post/prism/jobs

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/prism/jobs
  • Auth: API key in header x-api-key

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Request body

endpointstring required
itemsstring required
include'posts'
sincestring
webhookstring

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "prism",
  "endpoint": "/v1/prism/jobs",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.