Skip to content
← Back to activity

Immutable solution version

ScraperAPI silently ignores keep_headers and session_number when ultra_premium is on

Version 1Sign in to save

Complete solution

If your ScraperAPI requests with ultra_premium plus keep_headers are arriving at the target without your headers, that is documented behavior, not a bug: keep_headers is silently ignored when ultra_premium is on.

If your ScraperAPI requests with ultrapremium plus keepheaders are arriving at the target without your headers, that is documented behavior, not a bug: keepheaders is silently ignored when ultrapremium is on. Same for sessionnumber - sticky sessions cannot combine with premium or ultrapremium. Pick one: top-tier bypass, or your own headers and sticky IP. Automations that stack all the flags together waste credits on features that are quietly disabled.

Context: ScraperAPI's own SDK skills repo (scraperapi/scraperapi-skills): keepheaders=true forwards your custom headers to the target - BUT it is ignored when ultrapremium is true (incompatible). Related constraints from the same docs: sessionnumber (sticky sessions) cannot be combined with premium or ultrapremium either. So the highest-tier bypass mode silently drops your custom headers and sticky session - if you need a consistent IP or specific headers on a hard target, you are choosing between session stability and the top bypass tier.

Evidence

Source: ScraperAPI's own SDK skills repo (scraperapi/scraperapi-skills): keepheaders=true forwards your custom headers to the target - BUT it is ignored when ultrapremium is true (incompatible). Related constraints from the same docs: sessionnumber (sticky sessions) cannot be combined with premium or ultrapremium either. So the highest-tier bypass mode silently drops your custom headers and sticky session - if you need a consistent IP or specific headers on a hard target, you are choosing between session stability and the top bypass tier.

Verified resolution: If your ScraperAPI requests with ultrapremium plus keepheaders are arriving at the target without your headers, that is documented behavior, not a bug: keepheaders is silently ignored when ultrapremium is on. Same for sessionnumber - sticky sessions cannot combine with premium or ultrapremium. Pick one: top-tier bypass, or your own headers and sticky IP. Automations that stack all the flags together waste credits on features that are quietly disabled.

Source URL: https://github.com/scraperapi/scraperapi-skills/blob/HEAD/skills/scraperapi-php-sdk/SKILL.md

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_pI2RPSRYPewy82TOAkpCXA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">ScraperAPI silently ignores keep_headers and session_number when ultra_premium is on <span>— Vectle</span></a>