Docs menu
Slickdeals API endpoint
Slickdeals Forums API
Returns Slickdeals' own full legacy sub-forum list (e.g. Hot Deals, Coupons, Freebies) -- the discovery endpoint for GET /slickdeals/search's forum_id parameter. A separate, coarser-grained taxonomy from GET /slickdeals/categories' 421-entry tag list: this is the classification GET /slickdeals/deal, /slickdeals/search/advanced, and /slickdeals/frontpage already surface as forum_id, with this endpoint as the way to resolve an id to a name or filter search results by it. The list is refreshed from Slickdeals' own site periodically; an optional q parameter narrows it to a substring match on name.
GETapiKey1 credit/requestSlickdealsslickdeals.forumsResponseDoc
Slickdeals/slickdeals/forumsEndpoint facts
- Method
- GET
- API path
- /slickdeals/forums
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Slickdeals
- Response schema
- #/definitions/slickdeals.forumsResponseDoc
How this endpoint behaves
Query parameters:
q(optional) — case-insensitive substring filter on name, e.g.deal.
Response includes forums[], count, source_url, and fetched_at. Each forum has id, name, and url. The list is refreshed from Slickdeals' own site periodically (cached, not fetched fresh on every call).
Live monitoring
- Monitored request
- GET /slickdeals/forums
- Checks passed, 7 days to 14 Oct 2026
- 99.8%
- Median response time
- 2.26 s
Sampled response
- Request, 14 Oct 2026
- GET /slickdeals/forums
- Items in forums
- 27
- Fields filled in every checked item
- 3
| Field | Filled in, of 27 checked | Values in the sample |
|---|---|---|
| id | 27 | |
| name | 27 | “Hot Deals” and 26 other values |
| url | 27 | slickdeals.net |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| q | string | No | Case-insensitive substring filter on name | deal | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/slickdeals/forums?q=coffee" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"msg": "OK",
"data": {
"forums": [
{
"id": 9,
"name": "Hot Deals",
"url": "https://slickdeals.net/forums/forumdisplay.php?f=9"
},
{
"id": 10,
"name": "Coupons",
"url": "https://slickdeals.net/forums/forumdisplay.php?f=10"
}
],
"count": 26,
"source_url": "https://slickdeals.net/forums/",
"fetched_at": "2026-09-15T11:00:00Z"
}
}Request schema
No body schema
Response schema
#/definitions/slickdeals.forumsResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | Code is the HTTP status code or a custom code used to indicate the result of the request @example 200 | |||
| data | slickdeals.ForumsResponse | No | ||||
| data.count | integer | No | 26 | |||
| data.fetched_at | string | No | ||||
| data.forums | array | No | ||||
| data.forums[].id | integer | No | 9 | |||
| data.forums[].name | string | No | Hot Deals | |||
| data.forums[].url | string | No | https://slickdeals.net/forums/forumdisplay.php?f=9 | |||
| data.source_url | string | No | ||||
| msg | unknown | No | Msg is the message that describes the result of the request @example "Request successful" |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Code examples
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/slickdeals/forums?q=coffee" \
-H "x-api-key: $CRAWLORA_API_KEY"