Crawlora Docs
Use cURL to test Crawlora endpoints from a terminal before adding code to an application.
export CRAWLORA_API_KEY="crl_..."
This uses the real Search Bing web results endpoint at https://api.crawlora.net/api/v1/bing/search.
curl -X GET "https://api.crawlora.net/api/v1/bing/search?q=coffee&page=1&count=10&country=us&lang=en" \ -H "x-api-key: $CRAWLORA_API_KEY"
curl -X GET "https://api.crawlora.net/api/v1/bing/search?q=coffee&page=1&count=10&country=us&lang=en" \ -H "x-api-key: $CRAWLORA_API_KEY" | jq .
curl -X GET "https://api.crawlora.net/api/v1/bing/search?q=coffee&page=1&count=10&country=us&lang=en" \ -H "x-api-key: $CRAWLORA_API_KEY" \ -o crawlora-response.json
curl -v -X GET "https://api.crawlora.net/api/v1/bing/search?q=coffee&page=1&count=10&country=us&lang=en" \ -H "x-api-key: $CRAWLORA_API_KEY"
This shape is illustrative. Endpoint docs are the source of truth when a generated failure schema is available.
{
"error": {
"code": "rate_limit_exceeded",
"message": "Rate limit exceeded.",
"request_id": "req_..."
}
}Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora termsUse the TypeScript, Python, or Go examples for production integration patterns.