Agoda API endpoint
Use Crawlora's Search Agoda hotels by city API to extract supported public Agoda data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/agoda/hotels/searchReturns hotel search results for an Agoda city: the matching property ids for that city plus a direct link to each property's listing page. Callers may supply a known Agoda city id or a free-text city name; when both are supplied city_id takes precedence. Credential-free public data from Agoda's own hotel search. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| city_id | integer | No | Numeric Agoda city id, e.g. 9395 for Bangkok. Either city_id or city is required; city_id takes precedence when both are supplied. | ||
| city | string | No | Free-text city name, resolved to a numeric city id via Agoda's own destination search. Ignored when city_id is also supplied. | ||
| page | integer | No | 1 | 1-indexed result page, defaults to 1 | |
| limit | integer | No | 10 | Results per page, defaults to 10, maximum 50 | |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/agoda/hotels/search?page=1&limit=10" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
- One of `city_id` or `city` is required; supplying neither returns `400` before any upstream request is made. An explicit non-positive `city_id` also returns `400`. An unknown/unresolvable city returns `404`. - Each result only carries `property_id` and a direct `source_url` — Agoda's own search does not reliably return richer inline content (name, rating, thumbnail) credential-free. Call the hotel-detail endpoint with each `property_id` for full hotel content. Example response: ```json { "code": 200, "msg": "OK", "data": { "city_id": 9395, "page": 1, "limit": 10, "count": 10, "properties": [ { "property_id": 10630, "source_url": "https://www.agoda.com/search?cid=-1&selectedproperty=10630&city=9395" } ] } } ```
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 500 | Internal Server Error | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"city_id": 9395,
"page": 1,
"limit": 10,
"count": 10,
"properties": [
{
"property_id": 10630,
"source_url": "https://www.agoda.com/search?cid=-1&selectedproperty=10630&city=9395"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/agoda.searchResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | agoda.SearchResponse | No | ||||
| data.city_id | integer | No | 9395 | |||
| data.count | integer | No | 10 | |||
| data.limit | integer | No | 10 | |||
| data.page | integer | No | 1 | |||
| data.properties | array | No | ||||
| data.properties[].property_id | integer | No | 10630 | |||
| data.properties[].source_url | string | No | https://www.agoda.com/search?cid=-1&selectedproperty=10630&city=9395 | |||
| msg | string | No | OK |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/agoda/hotels/search?page=1&limit=10" \
-H "x-api-key: $CRAWLORA_API_KEY"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 terms