Getting started
Introduction
Every endpoint works the same way: one HTTPS request, one Bearer token, one consistent JSON envelope. You'll be up and running in under five minutes.
3 steps to use Orlabia Tech
Create an API key
Sign up and generate a key in Dashboard → API Keys. Free credits are included — no card needed.
Send a request
Call any endpoint over HTTPS with your key in the Authorization header.
Handle the envelope
Every response uses the same { success, data, error } shape — one handler covers everything.
Dashboard → API Keys is where your API key lives. Send it on every request as Authorization: Bearer <key>.
Base URL
Request example
Parameters go in the query string for GET endpoints and the JSON body for POST endpoints:
curl "http://localhost:8001/v1/taobao/item_detail?item_id=675432198765¤cy=USD" \
-H "Authorization: Bearer YOUR_API_KEY"Response envelope
Every endpoint — success or failure — returns the same shape, so one response handler covers your whole integration:
{
"success": true,
"data": { "...": "payload, null on error" },
"error": null
}Status codes
| Code | Meaning |
|---|---|
| 200 | OK — request succeeded, credits charged |
| 400 | Bad request — missing or invalid parameter, not charged |
| 401 | Unauthorized — missing or revoked API key |
| 404 | Not found — item/shop does not exist, not charged |
| 429 | Rate limited — retry after the Retry-After header |
| 500 | Upstream error — safe to retry, not charged |
Rate limits & retries
Limits scale with your plan (1 req/s free → custom for enterprise). On 429 responses, wait for the Retry-After header before retrying. Rate-limited and failed requests are never charged, so exponential-backoff retries are always safe.
Jump into the reference
Full parameters, request samples in 5 languages and response examples for every endpoint.