Browser-Based API Posting with Same Session (Headers, Tokens & Akamai Protection)
Budget: ₹12,500 – ₹37,500 INR
Project Description
I am looking for an experienced developer who can implement a solution to send POST API requests directly from an active browser session, maintaining full session integrity and security context.
The requirement is to replicate browser network requests exactly as they occur in DevTools — including all dynamic headers, cookies, tokens, and Akamai-related security parameters — without triggering bot protection or security blocks.
Core Requirements:
API request must originate from the same opened browser session
Must reuse:
All request headers
Session cookies
CSRF tokens
Authorization tokens
Dynamic security tokens
Akamai-related parameters
Must work with protected endpoints (Akamai / Bot Manager enabled)
Should avoid 403, 401, 504, or security validation failures
No external request libraries (like plain requests.post) unless properly bound to browser session
Maintain real browser fingerprint consistency
Preferred Technical Approach:
Selenium / SeleniumBase integration
Chrome DevTools Protocol (CDP) usage
Network interception or replay
In-browser JavaScript execution (fetch / XHR override)
Proper handling of dynamic request signing if applicable
Goal:
To programmatically trigger the same successful API call that the browser makes, while preserving complete browser session authenticity.
Deliverables:
Fully working implementation
Clean and optimized code
Explanation of approach used
Must be tested and verified against protected endpoint
I am looking for an experienced developer who can implement a solution to send POST API requests directly from an active browser session, maintaining full session integrity and security context.
The requirement is to replicate browser network requests exactly as they occur in DevTools — including all dynamic headers, cookies, tokens, and Akamai-related security parameters — without triggering bot protection or security blocks.
Core Requirements:
API request must originate from the same opened browser session
Must reuse:
All request headers
Session cookies
CSRF tokens
Authorization tokens
Dynamic security tokens
Akamai-related parameters
Must work with protected endpoints (Akamai / Bot Manager enabled)
Should avoid 403, 401, 504, or security validation failures
No external request libraries (like plain requests.post) unless properly bound to browser session
Maintain real browser fingerprint consistency
Preferred Technical Approach:
Selenium / SeleniumBase integration
Chrome DevTools Protocol (CDP) usage
Network interception or replay
In-browser JavaScript execution (fetch / XHR override)
Proper handling of dynamic request signing if applicable
Goal:
To programmatically trigger the same successful API call that the browser makes, while preserving complete browser session authenticity.
Deliverables:
Fully working implementation
Clean and optimized code
Explanation of approach used
Must be tested and verified against protected endpoint