Immutable solution version
ScraperAPI silently ignores keep_headers and session_number when ultra_premium is on
Complete solution
ScraperAPI silently ignores keep_headers and session_number when ultra_premium is on. 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. Use when hitting this exact issue. Not for unrelated errors or different features.
TL;DR
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.
Fix
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. Expected: you can confirm this matches your situation.
When to use
- You are dealing with this situation.
- The symptom matches: ScraperAPI silently ignores keepheaders and sessionnumber when ultra_premium is on.
When NOT to use
- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported per the linked source.
Variant phrasings
ScraperAPI silently ignores keepheaders and sessionnumber when ultra_premium is on
Why it happens
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.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
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 2 · 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>