When to use
Use custom headers and cookies when you need to:- Access authenticated content: Retrieve data behind login walls
- Maintain sessions: Preserve user state across requests
- Mimic real users: Include user-specific headers for personalized data
- API authentication: Send API keys or tokens in headers
- Regional content: Set language or region preferences
This is an advanced feature. Misconfigured headers or cookies may trigger anti-bot detection or cause requests to fail.
Supported Parameters
Headers
| Parameter | Type | Description | Required |
|---|---|---|---|
headers | Object or String | Custom HTTP headers to send with request | No |
method | String | HTTP method: GET, POST, PUT, DELETE, etc. | When using POST/PUT |
body | String or Object | Request body for POST/PUT requests | When using POST/PUT |
Cookies
| Parameter | Type | Description | Required |
|---|---|---|---|
cookies | String or Array | Cookies to include in request | No |
cookies[].key | String | Cookie name | Yes (when using array) |
cookies[].value | String | Cookie value | Yes (when using array) |
cookies[].domain | String | Cookie domain (defaults to request URL domain) | No |
Do not mix headers and cookies in the same request. Choose one method based on your needs.
Usage
Send custom headers
Include headers as an object:POST requests with headers
Send POST requests with custom headers and body:Send cookies (string format)
Use simple string format for multiple cookies:Send cookies (object format)
Use object format for domain-specific cookies:Important constraints
Don’t mix headers and cookies:- Improper headers may trigger anti-bot detection
- Invalid cookies can cause request failures
- Test thoroughly before production use
- Monitor success rates when using custom headers/cookies
- Total header size: 32 KB
- Individual header: 8 KB
- Cookie header: 4 KB
This is an advanced feature requiring careful configuration. Always test in a development environment first.

