Skip to content

RedGifs Creator and Video Metadata Scraping

RedGifs pages mix creator profiles, video pages, view and like counts, upload dates and engagement signals.

OUTPUT FORMATSHTMLJSONMarkdown

A RedGifs scraper API lets you collect that data without running your own headless browser fleet or proxy pool. You send a URL plus request controls; the API renders the page, handles bot detection, and returns either rendered HTML or structured JSON.

What a RedGifs request can return

A single request against a RedGifs creator or video page can return video metadata, view count, like count, creator handle, upload date and engagement signals. The output shape depends on the extraction mode you choose:

  • Rendered HTML — the page after JavaScript has executed, useful when you want to parse it yourself.
  • extract_rules JSON — CSS selectors mapped to field names, returned as parsed JSON.
  • ai_extract_rules JSON — a natural-language specification of the fields you want, returned as parsed JSON.

The three modes are alternatives, not layers. Pick one per request based on how stable the page markup is and how much of the extraction logic you want to own.

Request controls and what each one changes

The API exposes a small set of parameters that change how a RedGifs request is executed. Treat them as independent switches:

ControlWhat it changesWhen to use it
render_jsRuns the page in a real headless browser and returns post-render HTMLPages whose content only appears after JavaScript executes
stealth_proxyRoutes through residential proxies with browser-like behaviourTargets that show aggressive bot detection
country_codeRoutes through a residential IP in the chosen countryContent that varies by geography
extract_rulesCSS selectors mapped to field namesYou know the markup and want deterministic JSON
ai_extract_rulesNatural-language field specificationMarkup shifts often or you want to describe fields in words

These controls compose: a single request can enable render_js, set country_code, and pass extract_rules together.

From account to first RedGifs request

  1. Create an account. You get an API key and free credits to start.
  2. Pick a client. Python, Node.js, Go, PHP, Ruby and Java SDKs are available, plus raw cURL examples.
  3. Send the RedGifs URL. POST or GET the target page to the API. Rendering and anti-bot handling happen server-side.
  4. Add advanced parameters only when needed. render_js for JavaScript, stealth_proxy for CAPTCHA pressure, country_code for geo-targeting, and extract_rules or ai_extract_rules for structured output.

A dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL — useful if you want to confirm a request shape before wiring it into code.

Worked example: turning a creator page into a record

Suppose you want one row per creator video with the creator handle, upload date, view count, like count and engagement signal. A practical sequence is:

  1. Send the creator page URL with render_js enabled so the video grid is present in the returned HTML.
  2. Pass extract_rules mapping each CSS selector to a field name — for example a selector for the handle, one for the date, one for views, one for likes.
  3. Receive parsed JSON with those field names as keys.

If the markup changes and your selectors stop matching, switch to ai_extract_rules with a natural-language description of the same fields. The output contract (parsed JSON keyed by your field names) stays the same; only the extraction mechanism changes. This is the main reason to keep extraction logic separate from your storage layer.

Three different failure modes, three different fixes

Requests against RedGifs can fail for reasons that look similar but need different responses:

  • Concurrency limit reached. The API enforces concurrency limits per plan, not per-target rate limits. If you exceed your plan's concurrent requests, the fix is to reduce in-flight requests or move to a plan with higher concurrency.
  • Target throttling. If RedGifs itself throttles aggressive request patterns, space out requests or use multiple sessions. This is a property of the target, not of your plan.
  • Bot detection. If a target becomes aggressive about blocking, enable stealth_proxy on the request. Proxy rotation and headless browser rendering already run by default; stealth_proxy is the escalation step.

Separating these three cases prevents the common mistake of raising concurrency when the real problem is target-side throttling.

Plan structure and credit mechanics

Plans are organised into Standard and Enterprise tiers, each with a monthly price, an API credit allowance, and a concurrent-request ceiling. Credit consumption depends on which features a request enables:

  • Base requests start at 1 credit each.
  • JavaScript rendering costs 5 API credits per successful request.
  • Premium proxies cost 10 or 25 API credits per successful request, depending on whether JS rendering is also enabled.
  • API credits are valid for one month and do not roll over.

Geotargeting routes through 200+ countries and territories (40+ on classic proxies). Screenshots and CSS/XPath extraction rules are included across plans. Priority email support, a dedicated account manager and team management appear on higher tiers. All prices are exclusive of VAT.

The complete plan matrix — every tier, price, credit allowance and feature inclusion — is delivered as an immutable table module alongside this page. Read it as a dated reference and confirm current terms before committing to a plan.

Adjacent capabilities that pair with RedGifs scraping

Beyond the core request, the platform exposes features that are useful when RedGifs data feeds a larger pipeline:

  • AI web scraping — describe the fields you want in natural language.
  • Screenshot API — capture specific RedGifs content as an image.
  • Google Search API — pull RedGifs-related results from a SERP.
  • JavaScript scenarios — automate clicks, scrolls and typing before extraction.
  • Markdown output — receive a page as clean Markdown.
  • n8n integration — run extraction inside a no-code workflow.

Each of these is a separate product surface with its own documentation; they are not required for a basic RedGifs request.

RedGifs scraper API plan matrix (dated reference)
PlanMonthly priceAPI creditsConcurrent requestsJS renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Prices are exclusive of VAT. API credits are valid for one month and do not roll over. Requests start at 1 credit each; JS rendering costs 5 credits per successful request; premium proxies cost 10 or 25 credits per successful request depending on JS rendering. Geotargeting covers 200+ countries and territories (40+ on classic proxies). This is a dated reference; confirm current terms before purchase.

Frequently asked questions

Will I get blocked when scraping RedGifs?

Residential proxies are rotated and a real headless browser is used, so requests resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request.

Can I scrape RedGifs without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby or cURL.

How do I handle JavaScript when scraping RedGifs?

Pass render_js=true on the request. The page runs in a real headless browser, JavaScript executes server-side, and the post-render HTML is returned.

Can I scrape RedGifs from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography.

What's the rate limit for scraping RedGifs?

The API enforces concurrency limits per plan, not per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from RedGifs?

Choose one of two paths. With extract_rules, you supply CSS selectors and pair each selector with the field name you want it to populate. With ai_extract_rules, you describe the fields in natural language instead of writing selectors. Either way, the API returns the result as parsed JSON rather than raw HTML.