The Social Crow API lets you place and manage orders programmatically — no web interface needed. It is designed for resellers and developers who want to automate their workflow or build tooling on top of Social Crow's services.

Every request must include your API key in the Authorization header as a Bearer token. Requests without a valid key receive a 401 response with error code UNAUTHORIZED.

Generate or regenerate your key at any time from the API settings page. Regenerating immediately invalidates the previous key.

curl https://www.socialcrow.co/api/v1/balance \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Three steps to place your first order: check your balance, find a service, and submit the order.

# 1. Check your balance
curl https://www.socialcrow.co/api/v1/balance \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# 2. List available services
curl https://www.socialcrow.co/api/v1/services \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# 3. Place an order
curl -X POST https://www.socialcrow.co/api/v1/orders \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"serviceId":"1234","link":"https://instagram.com/username","quantity":1000}'

The official TypeScript SDK wraps the REST API with full types and a Result pattern: every method returns Result<T> instead of throwing. You never need try/catch.

# The SDK wraps the REST API — use the TypeScript tab for SDK usage.

Returns all active services with their IDs, names, categories, and customer-facing pricing. Cache this response — services change infrequently.

Response fields

curl https://www.socialcrow.co/api/v1/services \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Places a single order using your account balance. Returns an orderId, the charge deducted from your balance, and the currency on success (HTTP 201). Each call creates exactly one order for one service.

curl -X POST https://www.socialcrow.co/api/v1/orders \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "serviceId": "1234",
    "link": "https://instagram.com/username",
    "quantity": 1000
  }'

# Response (HTTP 201)
# { "data": { "orderId": "V1StGXR8", "charge": 1.25, "currency": "USD" } }

Get the exact charge amount for an order without placing it. Uses the same pricing logic as order creation — including rounding and minimums — so the returned amount matches what would be deducted from your balance. Useful when service rates are per 1,000 units but you order fewer (e.g. 100 followers at $6.24/1,000); the actual charge may differ from a naive rate × quantity ÷ 1000.

Same validation as Create Order: quantity must be within the service's min/max; drip-feed and comment-type services require their respective fields.

curl -X POST https://www.socialcrow.co/api/v1/quote \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"serviceId":"1234","quantity":100}'

# Response (HTTP 200)
# { "data": { "serviceId": "1234", "quantity": 100, "charge": 0.63, "currency": "USD" } }

Returns the current status of a single order, synced fresh from the external panel on each call. Only orders placed via API (tied to your account) are accessible.

Status values

curl https://www.socialcrow.co/api/v1/orders/V1StGXR8 \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Check the status of up to 100 orders in a single request. Returns a map of orderId → status. Order IDs that don't belong to your account return an error entry rather than a 404 — useful for batch reconciliation.

curl -X POST https://www.socialcrow.co/api/v1/orders/bulk \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"orders": ["V1StGXR8", "Xk9pLqM2", "unknown_id"]}'

Returns a paginated list of all orders placed via the API for your account, sorted newest first.

# First page
curl "https://www.socialcrow.co/api/v1/orders" \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# Page 2
curl "https://www.socialcrow.co/api/v1/orders?page=2" \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Returns the current account balance in USD. The value is accurate to 4 decimal places with no rounding. Balances are always positive — orders are rejected if balance is insufficient.

curl https://www.socialcrow.co/api/v1/balance \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# Response
# { "data": { "balance": "12.3400", "currency": "USD" } }

Submits a refill request for a delivered order. Social Crow offers a 30-day refill guarantee — if the count on a delivered order drops, you can request a top-up here.

Response fields

curl -X POST https://www.socialcrow.co/api/v1/refills \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"orderId":"ABC123456789DE"}'

Returns the current status of a refill request for a given order. The :id path parameter is the orderId returned when the order was created.

Refill status values

Response fields

curl https://www.socialcrow.co/api/v1/refills/ABC123456789DE \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Submit refill requests for up to 100 orders in a single call. Returns a map of orderId → result. Orders that are ineligible or not found return an error entry in the map rather than a 4xx response — allowing you to process the full batch in one pass.

curl -X POST https://www.socialcrow.co/api/v1/refills/bulk \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"orders":["ABC123456789DE","ord_def456"]}'

Check the refill status of up to 100 orders in a single request. Returns a map of orderId → refill status. Orders with no refill request, or that don't belong to your account, return an error entry rather than a 404.

curl -X POST https://www.socialcrow.co/api/v1/refills/status \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"orders":["ABC123456789DE","ord_def456"]}'

The API uses a consistent, predictable error system across every endpoint. Whether you use the REST API directly or the TypeScript SDK, errors always have the same shape and the same typed codes — making it straightforward to handle each case explicitly in your code.

Response shape

Every response is either a success envelope or an error envelope — never both. HTTP status codes reflect the category of error.

Handling errors in your code

The TypeScript SDK makes error handling completely explicit via the Result pattern — check result.ok first, then branch on result.error.code. Your IDE autocompletes every possible code value. For other languages, check for the error key in the JSON response before accessing data.

# All responses are JSON — check for the "error" key before using "data".
response=$(curl -s -X POST https://www.socialcrow.co/api/v1/orders \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"serviceId":"1234","link":"https://instagram.com/u","quantity":1000}')

if echo "$response" | python3 -c "import sys,json; d=json.load(sys.stdin); sys.exit(0 if 'error' in d else 1)" 2>/dev/null; then
  code=$(echo "$response" | python3 -c "import sys,json; print(json.load(sys.stdin)['error']['code'])")
  msg=$(echo "$response"  | python3 -c "import sys,json; print(json.load(sys.stdin)['error']['message'])")
  echo "Error [$code]: $msg"
else
  order_id=$(echo "$response" | python3 -c "import sys,json; print(json.load(sys.stdin)['data']['orderId'])")
  echo "Order placed: $order_id"
fi

Error codes