Custom Headers
BrowserAPI allows you to add your own headers to a request and get customised results.
Custom HTTP headers are useful when you want to provide additional information to your request. If your request requires passing custom HTTP headers, all you have to do is to append WSA-
to your header's name and add them to your request.
For example, the Sec-Fetch-Dest: document
header will be passed as WSA-Sec-Fetch-Dest: document
.
Only use this feature to get customized results, do not use this feature to avoid blocks. BrowserAPI has a powerful internal engine that takes care of everything for you.
Only the following headers can be overwritten:
accept
accept-encoding
accept-language
cache-control
connection
content-type
dnt
origin
referer
save-data
sec-ch-ua
sec-ch-ua-mobile
sec-ch-ua-platform
sec-fetch-dest
sec-fetch-mode
sec-fetch-site
sec-fetch-user
sentry-trace
upgrade-insecure-requests
user-agent x-amzn-trace-id
x-forwarded-port
x-i18n-language
x-lpm-session
x-requested-with
x-unique-id
Additional headers may be added per domain by contacting our support.
Custom Headers Integration Examples
Important! The url
parameter has to be encoded.
( i.e. &url=https%3A%2F%2Fwww.webscrapingapi.com%2F )
Last updated