> ## Documentation Index
> Fetch the complete documentation index at: https://docs.evade.now/llms.txt
> Use this file to discover all available pages before exploring further.

# Replay requests

> Apply Evade's output without changing the solved request context.

A successful solve returns the complete headers and browser user agent required
for the protected request. Treat that output as one atomic request context.

## Apply every header

Use all entries from the returned `headers` object, including ordinary browser
headers, cookies, and generated Shape headers. Do not copy only headers whose
names appear challenge-specific.

## Preserve the browser identity

Use the returned `user_agent` exactly. It is the identity used for challenge
fetching, fingerprint selection, client hints, and header generation.

## Preserve the network identity

Route the replay request through the same proxy used to create the solve session.
Switching proxy exits can change the IP, country, timezone, language, and cookies
that were encoded into the generated payload.

## Preserve the destination

Send the headers to the exact `target_api` using the exact
`target_api_method`. Generate a new header set before changing either value.

When the response contains `one_time: true`, send the request immediately and
only once. Its target and method are the replay contract embedded by the page;
there is no reusable solve session.

<Warning>
  Generated headers are not general-purpose authentication tokens. Do not cache
  one header set and reuse it for unrelated URLs, methods, proxies, or sessions.
</Warning>