## TL;DR

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.

## Fix

1. 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.
   Expected: you can confirm this matches your situation.

## When to use

- You are dealing with this situation.
- The symptom matches: ScraperAPI silently ignores keep_headers and session_number 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 keep_headers and session_number when ultra_premium is on

## Why it happens

ScraperAPI's own SDK skills repo (scraperapi/scraperapi-skills): keep_headers=true forwards your custom headers to the target - BUT it is ignored when ultra_premium is true (incompatible). Related constraints from the same docs: session_number (sticky sessions) cannot be combined with premium or ultra_premium 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.