Docs menu
Slickdeals API endpoint
Slickdeals Deal Types API
Returns Slickdeals' own deal-type tag list (Coupon, Free / Freebie, Giveaway, Gift Card, Mail In Rebate, Online Only, YMMV, ...) -- the discovery endpoint for GET /slickdeals/search's deal_type_id parameter. Confirmed identical across multiple Slickdeals sub-forums, unlike the broader interest-tag space it is drawn from, which was not found to be reliably enumerable. An optional q parameter narrows it to a substring match on name.
GETapiKey1 credit/requestSlickdealsslickdeals.dealTypesResponseDoc
Slickdeals/slickdeals/deal-typesEndpoint facts
- Method
- GET
- API path
- /slickdeals/deal-types
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Slickdeals
- Response schema
- #/definitions/slickdeals.dealTypesResponseDoc
How this endpoint behaves
Returns Slickdeals' own deal-type tag list (Coupon, Free / Freebie, Giveaway, Gift Card, Mail In Rebate, Online Only, YMMV, ...) — the discovery endpoint for GET /slickdeals/search's deal_type_id parameter. These are drawn from Slickdeals' own "Quick Category Filter" tag mechanism, confirmed identical across multiple sub-forums (unlike the broader interest-tag space that mechanism also exposes, which was not found to be reliably enumerable).
Query parameters:
q(optional) — case-insensitive substring filter on name, e.g.free.
Response includes deal_types[], count, source_url, and fetched_at. Each deal type has id and name — there is no standalone browse URL for a deal type, since it is a search-filter value only, not itself a browsable page. The list is refreshed from Slickdeals' own site periodically (cached, not fetched fresh on every call).
Live monitoring
- Monitored request
- GET /slickdeals/deal-types
- Checks passed, 7 days to 14 Oct 2026
- 99.8%
- Median response time
- 2.02 s
Sampled response
- Request, 14 Oct 2026
- GET /slickdeals/deal-types
- Items in deal_types
- 10
- Fields filled in every checked item
- 2
| Field | Filled in, of 10 checked | Values in the sample |
|---|---|---|
| id | 10 | |
| name | 10 | “Brick & Mortar (B&M)” and 9 other values |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| q | string | No | Case-insensitive substring filter on name | free | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/slickdeals/deal-types?q=coffee" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"msg": "OK",
"data": {
"deal_types": [
{
"id": 1688,
"name": "Coupon"
},
{
"id": 1774,
"name": "Free / Freebie"
},
{
"id": 66,
"name": "Your Mileage May Vary (YMMV)"
}
],
"count": 10,
"source_url": "https://slickdeals.net/forums/forumdisplay.php?f=9",
"fetched_at": "2026-09-15T12:00:00Z"
}
}Request schema
No body schema
Response schema
#/definitions/slickdeals.dealTypesResponseDoc
| 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.DealTypesResponse | No | ||||
| data.count | integer | No | 10 | |||
| data.deal_types | array | No | ||||
| data.deal_types[].id | integer | No | 1774 | |||
| data.deal_types[].name | string | No | Free / Freebie | |||
| 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/deal-types?q=coffee" \
-H "x-api-key: $CRAWLORA_API_KEY"