Developer guides
Use the official Maven Central beta SDK from JVM services, Spring applications, backend APIs, and data jobs. Built on java.net.http with no runtime dependencies.
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 Java SDK is published to Maven Central as net.crawlora:crawlora-sdk and developed at https://github.com/Crawlora-org/crawlora-java-sdk. Add the current promoted beta version 1.5.0-sdk.3 and keep API keys in server-side environments. Requires Java 17 or newer.
Developer workflow
Add the Maven Central artifact to your build. The SDK has no runtime dependencies beyond the JDK.
<dependency> <groupId>net.crawlora</groupId> <artifactId>crawlora-sdk</artifactId> <version>1.5.0-sdk.3</version> </dependency>
implementation "net.crawlora:crawlora-sdk:1.5.0-sdk.3"
Developer workflow
export CRAWLORA_API_KEY="your_api_key_here"
Developer workflow
Build a client with your API key, then call typed endpoint groups or the dynamic operation interface.
import net.crawlora.CrawloraClient;
import java.util.List;
import java.util.Map;
// Reads CRAWLORA_API_KEY from the environment if apiKey(...) is omitted.
CrawloraClient client = CrawloraClient.builder()
.apiKey(System.getenv("CRAWLORA_API_KEY"))
.build();
@SuppressWarnings("unchecked")
Map<String, Object> result = (Map<String, Object>) client.bing().search(Map.of("q", "coffee shops"));
for (Object item : (List<Object>) result.get("data")) {
System.out.println(((Map<String, Object>) item).get("title"));
}Developer 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 Java beta SDK is published to Maven Central as net.crawlora:crawlora-sdk and developed at https://github.com/Crawlora-org/crawlora-java-sdk. Pin the current version 1.5.0-sdk.3.
Java 17 or newer. The client is built on the JDK's java.net.http.HttpClient and has no runtime dependencies.
Pass your API key to CrawloraClient.builder().apiKey(...), or omit it to read CRAWLORA_API_KEY from the environment. JWT authorization is also supported.
Yes. It includes automatic retries with exponential backoff and Retry-After handling, plus client-side rate limiting and before/after middleware hooks.
Yes. Add the net.crawlora:crawlora-sdk coordinate to your pom.xml dependencies or your Gradle implementation configuration.
Open the endpoint detail page from the docs catalog to inspect request parameters, examples, and schema references.
Add the Maven Central artifact, pin the current version, set CRAWLORA_API_KEY, then inspect endpoint docs for platform-specific schemas.