Developer guides
Use the official Packagist beta SDK from Laravel, Symfony, and PHP backend integrations. Built on curl with no runtime dependencies beyond standard extensions.
Verified HTTP pattern
POST /google/search
Request
POST https://api.crawlora.net/api/v1/google/search
x-api-key: $CRAWLORA_API_KEY
Content-Type: application/json
{
"country": "us",
"keyword": "best CRM software",
"language": "en",
"limit": 10,
"page": 1
}Base URL
https://api.crawlora.net/api/v1
Auth header
x-api-key
Example endpoint
POST /google/search
The PHP SDK is published to Packagist as crawlora/sdk and developed at https://github.com/Crawlora-org/crawlora-php-sdk. Install the current promoted beta release and keep API keys in server-side environments. Requires PHP 8.1+ with the curl and json extensions.
Developer workflow
Install from Packagist with Composer. Releases use the SDK tag scheme, so use the dev version constraint shown below.
composer require crawlora/sdk:^1.5@dev
Developer workflow
export CRAWLORA_API_KEY="your_api_key_here"
Developer workflow
Construct a client, then call grouped endpoint helpers or the dynamic operation interface.
<?php
require 'vendor/autoload.php';
use Crawlora\Client;
// Reads CRAWLORA_API_KEY from the environment if apiKey is omitted.
$client = new Client(['apiKey' => getenv('CRAWLORA_API_KEY') ?: '']);
$result = $client->bing->search(['q' => 'coffee shops']);
foreach ($result['data'] as $item) {
echo $item['title'] ?? '', "\n";
}
$client->close(); // release the pooled curl connectionDeveloper workflow
The status codes below are common integration patterns. Endpoint detail pages list documented failure responses where available.
| Status / code | Meaning | How to handle |
|---|---|---|
| 400 | Invalid request or missing required input. | Validate request bodies before calling Crawlora and surface useful messages to users. |
| 401 | Missing or invalid API key. | Check the `x-api-key` header and rotate the key from the console if needed. |
| 402/403 | Plan, permission, or billing issue where applicable. | Check plan access, credit state, and endpoint availability. |
| 429 | Rate limit exceeded. | Back off with jitter and reduce concurrency. |
| 5xx | Temporary execution or upstream failure. | Retry safe jobs with exponential backoff and keep the failure visible. |
Developer workflow
Use Crawlora for structured public web data workflows. Customers are responsible for compliance with applicable laws, third-party rights, platform rules, and Crawlora terms. Keep API keys server-side, validate inputs, and avoid collecting or storing unnecessary sensitive data.
Read Crawlora termsDeveloper workflow
Use these pages to move between endpoint discovery, examples, pricing, and responsible-use guidance.
Developer workflow
Common questions for this Crawlora developer integration path.
Yes. The official PHP beta SDK is published to Packagist as crawlora/sdk and developed at https://github.com/Crawlora-org/crawlora-php-sdk. Install it with composer require crawlora/sdk:^1.5@dev.
PHP 8.1 or newer with the curl and json extensions. The SDK has no other runtime dependencies.
Releases are aliased from the main branch using the -sdk.N tag scheme, which is not a standard Composer version, so the ^1.5@dev constraint resolves the current beta.
Pass apiKey when constructing the Client, or omit it to read CRAWLORA_API_KEY from the environment. JWT authorization is also supported.
Yes. Register the client in your service container or instantiate it directly; it is a plain PHP client with no framework coupling.
Open the endpoint detail page from the docs catalog to inspect request parameters, examples, and schema references.
Require crawlora/sdk from Packagist, set CRAWLORA_API_KEY, then inspect endpoint docs for platform-specific schemas.