Utility Call Planner API
평소 말로 적은 작업에 필요한 호출을 순서대로 반환합니다. 호출마다 경로, 질문에서 채운 파라미터, 아직 비어 있는 파라미터, 크레딧 가격, 그리고 모르는 값을 자리표시자로 남긴 curl이 들어 있습니다.
GET /v1/utility/planUtility Call Planner API는 언제 쓰나요
할 일은 정했지만 어떤 엔드포인트를 불러야 할지 모를 때, 연동 코드를 쓰기 전에 무료로 사용하세요. 계획만 세우고 호출은 실행하지 않습니다.
API 레퍼런스 영문 원문
Turn a job written in plain words ("track mentions of Acme on TikTok and Reddit", "a creator's profile, posts and comments") into the exact calls to make, in order: method, path, the parameters your question filled, the ones still missing, which step's rows fill a later step, the credit price of each call, and a curl for each with every unknown value left as a {placeholder}. Jobs are planned from the task-recipe catalog (GET /v1/utility/recipes: comment exports, creator vetting, review comparisons, monitors, crawls and more) plus brand monitoring, one creator, a topic search, a saved search on a monitor, and one GET /v1/prism/discover run for a brand's reaction, the accounts behind a topic, trends, communities, or names to their own accounts; a one-call question returns that one call, and a job that combines several sources no recipe covers is planned as a chain (one call per source, a monitor per call when it repeats). A request to act on an account (post, reply, like, follow, delete) or about billing returns no steps. Every plan carries total: the whole job's credits (paging and per-row fan-out included, for the recipe's stated size) from the same pricing the API bills with. A question outside those returns uncertain with no steps instead of a guessed chain, and anything the API cannot return (a follower history, a new-post webhook) is listed under cannot. A search value that names no topic (a placeholder such as "keyword", a country name, an English phrase for a Korean or Chinese platform, or most of the sentence) is left out and asked for under missing, with a note saying why. A job that lists several topics plans each search step once per topic and names them under topics; one that names several markets is uncertain and lists them as ISO codes under markets. Beta: recipe matches are reliable; confirm a single-endpoint or multi-source plan with utility/find. Nothing is run. Free to call.
75개 플랫폼을 병렬로 검색합니다
Call Planner API로 무엇을 할 수 있을까요
Call Planner 엔드포인트가 통합 스키마와 계산 필드를 담은 Utility 데이터를 한 번의 요청으로 보내드려요. 스크래핑 인프라를 직접 만들거나 유지할 필요가 없어요.
요청 예시
# GET /v1/utility/plan: Free: 0 credits per call.
# --max-time 10: this endpoint's measured p99 latency x 1.5.
# --retry 3: retries timeouts, 429 and 5xx, honoring Retry-After.
# -o response.json keeps only the final attempt's body.
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
IDEMPOTENCY_KEY=$(od -An -N16 -tx1 /dev/urandom | tr -d ' \n')
curl -sS --max-time 10 --retry 3 -o response.json \
-H "x-api-key: YOUR_API_KEY" \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
"https://www.socialcrawl.dev/v1/utility/plan?query=Combine+%40acme%27s+TikTok+profile+with+their+recent+videos+and+the+comments+on+them" && cat response.json# GET /v1/utility/plan: Free: 0 credits per call.
import os
import random
import time
import uuid
import requests
API_KEY = os.environ.get("SOCIALCRAWL_API_KEY", "YOUR_API_KEY")
TIMEOUT_S = 10 # this endpoint's measured p99 latency x 1.5.
MAX_RETRIES = 3
URL = "https://www.socialcrawl.dev/v1/utility/plan"
def backoff(attempt):
# Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
return 2 ** attempt * (0.5 + random.random() / 2)
def socialcrawl(params):
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
idempotency_key = str(uuid.uuid4())
for attempt in range(MAX_RETRIES + 1):
try:
res = requests.get(
URL,
params=params,
headers={"x-api-key": API_KEY, "Idempotency-Key": idempotency_key},
timeout=TIMEOUT_S,
)
body = res.json()
except (requests.RequestException, ValueError):
# A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if attempt == MAX_RETRIES:
raise
time.sleep(backoff(attempt))
continue
if body["success"]:
return body
error = body["error"]
# Branch on error["type"], never on the message text.
if error["type"] == "RESOURCE_NOT_FOUND":
return None # refunded: nothing to read
retry_after = res.headers.get("Retry-After")
# SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
permanent = error["type"] == "SERVICE_UNAVAILABLE" and retry_after is None
if not error.get("retryable") or permanent or attempt == MAX_RETRIES:
raise RuntimeError(f"{error['type']}: {error['message']} (request_id {body['request_id']})")
# Retry-After (seconds) wins; otherwise back off.
time.sleep(float(retry_after) if retry_after else backoff(attempt))
params = {
"query": "Combine @acme's TikTok profile with their recent videos and the comments on them",
}
body = socialcrawl(params)
if body is not None:
print(body["data"])// GET /v1/utility/plan: Free: 0 credits per call.
const API_KEY = process.env.SOCIALCRAWL_API_KEY ?? "YOUR_API_KEY";
const TIMEOUT_MS = 10_000; // this endpoint's measured p99 latency x 1.5.
const MAX_RETRIES = 3;
type Page = { next_cursor: string | null; has_more: boolean };
type SocialCrawlResponse =
| { success: true; data: any; pagination?: Page; credits_used: number; request_id: string }
| { success: false; error: { type: string; message: string; retryable: boolean }; request_id: string };
const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));
// Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
const backoffMs = (attempt: number) => 2 ** attempt * 1000 * (0.5 + Math.random() / 2);
async function socialcrawl(url: URL) {
// One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
const idempotencyKey = crypto.randomUUID();
for (let attempt = 0; ; attempt++) {
let res: Response;
let body: SocialCrawlResponse;
try {
res = await fetch(url, {
headers: {
"x-api-key": API_KEY,
"Idempotency-Key": idempotencyKey,
},
signal: AbortSignal.timeout(TIMEOUT_MS),
});
body = (await res.json()) as SocialCrawlResponse;
} catch (error) {
// A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if (attempt >= MAX_RETRIES) throw error;
await sleep(backoffMs(attempt));
continue;
}
if (body.success) return body;
// Branch on error.type, never on the message text.
if (body.error.type === "RESOURCE_NOT_FOUND") return null; // refunded: nothing to read
const retryAfter = res.headers.get("Retry-After");
// SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
const permanent = body.error.type === "SERVICE_UNAVAILABLE" && retryAfter === null;
if (!body.error.retryable || permanent || attempt >= MAX_RETRIES) {
throw new Error(`${body.error.type}: ${body.error.message} (request_id ${body.request_id})`);
}
// Retry-After (seconds) wins; otherwise back off.
await sleep(retryAfter ? Number(retryAfter) * 1000 : backoffMs(attempt));
}
}
const url = new URL("https://www.socialcrawl.dev/v1/utility/plan");
url.searchParams.set("query", "Combine @acme's TikTok profile with their recent videos and the comments on them");
const body = await socialcrawl(url);
if (body) console.log(body.data);파라미터
| 파라미터 | 필수 | 설명 |
|---|---|---|
| query | 아니오 | The job in plain words, in any language. Up to 600 characters are read. Provide this or task |
| task | 아니오 | Alias for query (utility/find's name). Provide this or query |
Utility Call Planner API는 무엇을 돌려주나요
문서에 나온 응답 구조와 필드를 보여 주기 위해 만든 합성 예시예요. 값은 이해를 돕기 위한 것이며 실제 API 응답은 아니에요.
응답 예시 보기
{
"success": true,
"platform": "utility",
"endpoint": "/v1/utility/plan",
"data": {
"kind": "call_plan",
"version": 3,
"recipe": "creator_profile",
"uncertain": false,
"reason": "planned",
"confidence": 0.91,
"steps": [
{
"id": "tiktok_profile",
"method": "GET",
"path": "/v1/tiktok/profile",
"params": {
"handle": "acme"
},
"missing": [],
"credits": 1,
"run": "ready",
"curl": "curl -H \"x-api-key: YOUR_API_KEY\" \\n \"https://www.socialcrawl.dev/v1/tiktok/profile?handle=acme\""
},
{
"id": "tiktok_posts",
"method": "GET",
"path": "/v1/tiktok/profile/videos",
"params": {
"handle": "acme"
},
"missing": [],
"depends_on": "tiktok_profile",
"credits": 1,
"run": "after_approval",
"curl": "curl -H \"x-api-key: YOUR_API_KEY\" \\n \"https://www.socialcrawl.dev/v1/tiktok/profile/videos?handle=acme\""
},
{
"id": "tiktok_comments",
"method": "GET",
"path": "/v1/tiktok/post/comments",
"params": {},
"missing": [
"url"
],
"binds": {
"url": "tiktok_posts.items[].post.url"
},
"depends_on": "tiktok_posts",
"credits": 1,
"run": "blocked",
"curl": "curl -H \"x-api-key: YOUR_API_KEY\" \\n \"https://www.socialcrawl.dev/v1/tiktok/post/comments?url={url}\""
}
],
"ask": [],
"cannot": [],
"cannot_ids": [],
"alternatives": [],
"cheaper": "single_endpoint",
"deeper": null,
"catalog_recipe": "creator-profile-posts-comments",
"size": {
"description": "profile, one page of videos, first comment page on five videos",
"items": 5
},
"total": {
"calls": 7,
"hold": 7,
"expected_min": 7,
"expected_max": 7,
"exact": true,
"priced_with_examples": [
"url"
]
}
},
"credits_used": 0,
"request_id": "req_example000000",
"cached": false
}문서에 나온 응답 구조를 확인하기 위한 합성 예시예요. 값은 이해를 돕기 위한 것이며 운영 환경에서 가져온 응답이 아니에요.
Utility Call Planner API는 어떻게 동작하나요
API 키와 함께 GET 요청을 보내면, 통합 스키마와 계산 필드를 담은 깔끔한 JSON이 돌아와요.
메서드
GET
응답 형식
JSON
소셜 미디어 데이터를 몇 초 만에 수집하는 방법
개발자를 위한 가장 빠른 소셜 미디어 스크래핑 API. 월간 활성 사용자 100억 명 이상을 포괄하는 75개 플랫폼에서 프로필, 게시물, 댓글, 분석 데이터를 수집하세요.
모든 플랫폼을 하나의 스키마로
동일한 응답 구조로 75개 플랫폼을 조회하세요. 연동은 한 번이면 충분합니다.
단순 수집을 넘어 계산된 필드 제공
엔드포인트가 해당 지표를 지원하고 계산에 필요한 원본 값이 있을 때, 정규화된 레코드에 engagement_rate, estimated_reach, content_category, language를 함께 담아 바로 활용할 수 있습니다.
코드 한 줄 쓰기 전에, 데이터부터
Visual Data Explorer에 URL만 붙여넣으면 결과 카드와 정형화된 테이블, CSV 내보내기를 바로 사용할 수 있습니다.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}자주 묻는 질문
API, 요금제, 기능에 대한 질문과 답변입니다.
문의하기Call Planner API는 어떤 데이터를 돌려주나요?
Call Planner 엔드포인트는 언제 쓰면 좋나요?
Call Planner API 비용은 얼마인가요?
Call Planner API에는 어떤 파라미터가 필요한가요?
Call Planner API는 어떻게 호출하나요?
AI에게 SocialCrawl을 물어보세요
Utility Call Planner 데이터, 가져올 준비 되셨어요?
API 키 받고 60초 안에 Utility 데이터를 받아 가세요.
