Docs menu
Slickdeals API endpoint
Slickdeals Categories API
Returns Slickdeals' own full category/tag list -- the discovery endpoint for GET /slickdeals/category's slug parameter. This is a separate taxonomy from the category/sub_category fields GET /slickdeals/deal returns for an individual deal (Slickdeals maintains multiple parallel category/tag id spaces, not one) -- these slugs are the ones GET /slickdeals/category's own browse pages accept. The list is refreshed from Slickdeals' own site periodically; an optional q parameter narrows it to a substring match.
GETapiKey1 credit/requestSlickdealsslickdeals.categoriesResponseDoc
Slickdeals/slickdeals/categoriesEndpoint facts
- Method
- GET
- API path
- /slickdeals/categories
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Slickdeals
- Response schema
- #/definitions/slickdeals.categoriesResponseDoc
How this endpoint behaves
Query parameters:
q(optional) — case-insensitive substring filter on slug or name, e.g.laptop.
Response includes categories[], count, source_url, and fetched_at. Each category has slug, 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/categories
- Checks passed, 7 days to 14 Oct 2026
- 99.8%
- Median response time
- 1.48 s
Sampled response
- Request, 14 Oct 2026
- GET /slickdeals/categories
- Items in categories
- 422
- Fields filled in every checked item
- 3
| Field | Filled in, of 422 checked | Values in the sample |
|---|---|---|
| slug | 422 | |
| name | 422 | “Apple” and 420 other values |
| url | 422 | slickdeals.net |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| q | string | No | Case-insensitive substring filter on slug or name | laptop | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/slickdeals/categories?q=coffee" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"msg": "OK",
"data": {
"categories": [
{
"slug": "laptop-bag",
"name": "Laptop Bags",
"url": "https://slickdeals.net/deals/laptop-bag/"
},
{
"slug": "apparel",
"name": "Clothing & Accessories",
"url": "https://slickdeals.net/deals/apparel/"
}
],
"count": 421,
"source_url": "https://slickdeals.net/deal-categories/",
"fetched_at": "2026-09-15T06:00:00Z"
}
}Request schema
No body schema
Response schema
#/definitions/slickdeals.categoriesResponseDoc
| 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.CategoriesResponse | No | ||||
| data.categories | array | No | ||||
| data.categories[].name | string | No | Laptop Bags | |||
| data.categories[].slug | string | No | laptop-bag | |||
| data.categories[].url | string | No | https://slickdeals.net/deals/laptop-bag/ | |||
| data.count | integer | No | 421 | |||
| data.fetched_at | string | No | ||||
| 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/categories?q=coffee" \
-H "x-api-key: $CRAWLORA_API_KEY"