ScraperAPI silently ignores keep_headers and session_number 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.