Skip to main content

What are browser profiles?

Browser profiles define the network profile labels that wreq-js sends to the native layer. Profiles can influence behavior such as:
  1. TLS handshake preferences
  2. HTTP protocol behavior
  3. Default request headers
  4. Platform-specific header values
Final wire behavior is determined by the native engine and may vary by profile and runtime.

Available browsers

wreq-js profile families include:
  1. Chrome
  2. Firefox
  3. Safari
  4. Edge
  5. Opera
  6. OkHttp

Listing profiles

Using a profile

Specify the browser option in your fetch call:

Operating systems

Different operating systems have different header values and behaviors. Use the os option to emulate a specific platform:

Example: Windows Chrome

Example: iOS Safari

Profile updates

Profile labels are sourced from the native layer and can evolve with upstream updates.
Use a recent version of wreq-js if you want the latest profile set.

Custom headers

By default, browser emulation headers are automatically added. To use only your custom headers: