User Agents

This page explains the supported user agent configurations and how to maintain them for optimal performance across all Hyper Solutions APIs.

Overview

Hyper Solutions APIs support two user agent variants for all bot protection bypass services (Akamai, DataDome, Incapsula, and Kasada).

Supported User Agents

Windows User Agent (Recommended)

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36

Windows remains our recommended default.

macOS User Agent

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36

macOS user agent support is available for specific use cases where Windows user agents may face temporary restrictions or when targeting sites with macOS-specific requirements.

Chrome Version Management

Current Version

At the time of writing, Chrome stable version is 141. Your user agent string must reflect the current stable Chrome version to avoid detection.

Monitoring Chrome Releases

Track Chrome stable releases at: https://chromiumdash.appspot.com/schedule

Chrome follows a roughly 4-week release cycle for stable versions. Monitor this schedule to stay informed about upcoming releases.

Update Timeline

Recommended update strategy:

1. Monitor the Chrome release schedule for new stable versions

2. Wait 3-7 days after the stable release date

3. Update your user agent string to the new version

4. Update all related headers accordingly

Why wait 3-7 days?

• Allows time for real users to naturally update their browsers

• Avoids being among the very first to use a new version

• Ensures stability and widespread adoption of the release

Required Updates

When updating to a new Chrome version, you must update:

1. User Agent String: Update the version number (e.g., 141.0.0.0 → 142.0.0.0)

2. sec-ch-ua Header: Update to match the new version

   "Chromium";v="141", "Not(A:Brand";v="8", "Google Chrome";v="141"

3. sec-ch-ua-platform Header:

   • Windows: "Windows"

   • macOS: "macOS"

Critical: All version numbers must be consistent across your entire request configuration. Mismatched versions are a strong indicator of automated traffic.

Best Practices

Version Consistency

• Never mix versions: All Chrome version references must match

• Update completely: When upgrading, update all headers simultaneously

• Test after updates: Verify your configuration works after version changes

Platform Consistency

• Stick to one platform: Don't switch between Windows and macOS mid-session

• Match all platform indicators: Ensure all platform-specific headers align

• Maintain throughout session: Use the same configuration for all requests in a session

Monitoring and Maintenance

• Set version alerts: Create reminders for Chrome release dates

• Test in advance: Prepare updated configurations before deploying

• Monitor success rates: Track performance after version updates

• Document your configuration: Keep records of what works for your use cases

Troubleshooting

Detection Issues After Chrome Update

If you experience increased detection after a Chrome release:

• Verify you've updated all version-dependent headers

• Ensure version numbers are consistent across all headers

• Check that you're not updating too early (wait 3-7 days)

• Confirm your TLS fingerprint matches the Chrome version

Platform-Specific Blocks

If one platform gets blocked:

• Consider switching to the alternate platform temporarily

• Contact support for guidance on your specific situation

• Monitor if the block is temporary or permanent

• Ensure all platform-specific headers are correctly configured