SocialCrawl

Support

How to reach a person, what to send so we can find your call, and how to report a bad response from your own code.

Write to socialcrawl@ridio.io. A person on the team reads every message and answers from the same address.

What should I send?

Send the request_id of the call. Every response carries it in the body and in the X-Request-Id header, and it lets us find the exact request, what it cost and what the platform sent back.

Response
{
  "success": false,
  "request_id": "req_V1StGXR8Z5jdHi6B",
  "error": {
    "type": "UPSTREAM_ERROR",
    "status": 502
  }
}

With it, send what you expected and what came back. If you paste the request, leave your API key out of it.

Report a bad response from your code

POST /v1/feedback files a report against one of your own calls. It costs 0 credits, and an agent can send it as well as a person.

cURL
curl -X POST https://www.socialcrawl.dev/v1/feedback \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "request_id": "req_V1StGXR8Z5jdHi6B", "category": "wrong_data", "message": "The follower count is a week old." }'

category is one of wrong_data, empty, slow, error, billing or other. The answer is 201 for a new report and 200 when your account has already reported that call.

Is the API down?

Check the status page first: Status explains what each platform and endpoint state means and how to subscribe to changes. A 5xx answer is refunded, and Errors says which codes are safe to retry.

Buying, invoices and larger volumes

Invoices and VAT covers invoices, tax IDs and bank transfer. For a volume above the largest pack, see What a volume costs and Enterprise, then write to the same address.

On this page