Slickdeals Deal API for Price Trackers
Slickdeals deal pages are JavaScript-driven and protected by bot detection, which makes a thin HTTP client a poor fit on its own.
This page explains how a managed rendering layer can accept a Slickdeals URL, handle proxies and a headless browser, and return either rendered HTML or structured JSON. It also maps the deal fields you can expect, the request options that change credit cost, and the failure modes worth separating before you build a price-tracking workflow.
What the API does with a Slickdeals URL
You send a Slickdeals URL to the API. The service renders the page in a browser environment, rotates proxies, and returns the result. Without extraction rules you get rendered HTML. With extract_rules you can target elements using CSS or XPath selectors and receive structured JSON. With ai_extract_rules you can describe the fields you want in natural language and let the service return structured JSON without writing selectors. The practical effect is that your client stays a thin HTTP call rather than a fleet of headless browsers and proxy providers.
Deal fields you can pull
A Slickdeals deal page can expose title, deal price, retailer, coupon code, vote count, comment depth, frontpage status, category, and posting timestamp. The same surface supports price-tracking, deal-aggregation, and availability monitoring. The table below is a reader guide to those fields and the decisions they support; it is not a schema contract.
Field and control map
Use this map to decide which fields belong in your monitoring record and which request options you actually need. Turning on JavaScript rendering, premium proxies, or stealth proxies changes the credit cost per successful request, so the cheapest request is not always the one that returns usable data.
Worked example: one deal page into a monitoring record
Suppose you want to watch a single Slickdeals thread for a laptop deal. You send the thread URL with extract_rules that target the deal title, price, retailer, vote count, comment depth, and frontpage status. The response is JSON you can write into a row keyed by the thread URL and a capture timestamp. On the next run, compare the new price and vote count against the previous row. If the price rises or the frontpage status disappears, your alerting layer can flag the deal as cooling. If the request returns HTML instead of JSON, the extraction rule did not match the rendered markup; if it returns a block page, the request needs stealth_proxy or a different proxy class. Keeping those two failures separate stops you from rewriting selectors when the real problem is bot detection.
Failure distinction checklist
Before changing your code, classify the failure. A block page or CAPTCHA usually means the request needs stealth_proxy or a stronger proxy class. A page that renders but returns empty fields usually means the extraction rule targets markup that is not present after rendering. A request that times out or returns partial content usually points to rendering or network conditions rather than a selector problem. A 200 response with HTML where you expected JSON usually means extract_rules or ai_extract_rules was not applied. Separating these cases keeps your debugging focused and avoids unnecessary credit spend on options that do not address the actual failure.
Credit cost per request
Requests start at 1 credit each. Each successful request that enables JavaScript rendering costs 5 API credits total, not 1 plus 5. Each successful request that enables premium proxies costs 10 API credits with JavaScript rendering disabled, or 25 API credits with JavaScript rendering enabled. Stealth proxy costs 75 credits per successful request. API credits are valid for one month and do not roll over. Check the current pricing page before committing to a volume plan.
Choosing a plan shape
The plan structure separates standard tiers from enterprise tiers. Standard tiers differ by monthly credit allowance and concurrent request limit, while enterprise tiers add higher concurrency and support features. The exact prices, credit allowances, and included features are first-party commercial terms that must be confirmed by the owner before publication. Use the owner-input template below to capture those terms rather than treating any historical figure as a current offer.
Account and legal considerations
You do not need a Slickdeals account to use the API; you need an API key from the service. Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. The service states that it does not collect or store personal data from scraped sites unless the user explicitly requests it. Treat that as a policy statement to verify against your own compliance requirements, not as legal advice.
| Field or control | What it gives you | When to use it |
|---|---|---|
| title | Deal headline text | Always include for identification |
| deal price | Current listed price | Price tracking and alerts |
| retailer | Retailer tagged on the thread | Grouping and filtering |
| coupon code | Code attached to the deal | Promotion tracking |
| vote count | Community vote total | Popularity ranking |
| comment depth | Thread engagement depth | Distinguishing active deals |
| frontpage status | Whether the deal is on the frontpage | Availability and urgency signals |
| category | Deal category | Segmentation |
| posting timestamp | When the deal was posted | Freshness checks |
| render_js | JavaScript rendering | Pages that need client-side execution |
| stealth_proxy | Stronger bot-detection bypass | Block pages or CAPTCHAs |
| country_code | Geo-targeted requests | Region-specific deal views |
| extract_rules | CSS or XPath structured output | Deterministic JSON fields |
| ai_extract_rules | Natural-language structured output | Fields without selectors |
Field availability depends on what renders on the public page. Request options change credit cost as described in the credit-cost section.
Frequently asked questions
Do I need a Slickdeals account to use the API?
No. You need an API key from the rendering service, not a Slickdeals login. Send the public URL and the service handles rendering and proxies.
Is scraping Slickdeals legal?
Public-facing pages can usually be scraped, but you should review Slickdeals' terms of service before deploying and avoid content behind a login. This is general guidance, not legal advice.
What data can I extract from Slickdeals?
Anything that renders on the public page. Use extract_rules with CSS selectors or ai_extract_rules for natural-language extraction to get structured JSON back. Typical fields include title, price, retailer, coupon code, votes, comment depth, frontpage status, category, and posting timestamp.
How do I start scraping Slickdeals?
Create an account to get an API key, then send a GET request with the target Slickdeals URL. The service renders the page, rotates proxies, and returns the data. Test with the free credits before scaling up.
Will I get blocked when scraping Slickdeals?
The service rotates residential proxies and uses a real headless browser so requests resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request.
How much does it cost to scrape Slickdeals?
Requests start at 1 credit each. Each successful request that enables JavaScript rendering costs 5 API credits total, not 1 plus 5. Each successful request that enables premium proxies costs 10 API credits without JavaScript rendering or 25 with it. Stealth proxy costs 75 credits per successful request. API credits are valid for one month and do not roll over. Check the current pricing page for plan prices and free-credit terms.
What is the difference between extract_rules and ai_extract_rules?
extract_rules uses CSS or XPath selectors you write, which gives deterministic output when the markup is stable. ai_extract_rules lets you describe the fields in natural language and returns structured JSON without selectors, which is useful when the page structure changes or you do not want to maintain selectors.