http_session_get_cookies
Get all cookies stored in a session. Optionally filter by URL to get only cookies that would be sent to a specific domain. Returns cookies as a JSON array with domain, name, value, path, expiry, secure, and httponly fields.
When to use http_session_get_cookies
Use http_session_get_cookies when you need to read, set, or clear cookies to manage session state. It is part of Owl Browser's Cookie Management toolset and runs inside a self-hosted, source-level stealth engine, so every call inherits the same undetectable browser fingerprint as the rest of your automation — no separate anti-detect setup required.
Usage Example
Parameters
Required
session_idstringrequiredThe session ID.
Optional
urlstringOptional URL filter. Only returns cookies that would be sent to this URL.
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does http_session_get_cookies do?
Get all cookies stored in a session. Optionally filter by URL to get only cookies that would be sent to a specific domain. Returns cookies as a JSON array with domain, name, value, path, expiry, secure, and httponly fields. It belongs to Owl Browser's Cookie Management category and is available through the REST API, the Python SDK (browser.http_session_get_cookies()), the Node.js SDK, and the MCP server.
What parameters does http_session_get_cookies accept?
http_session_get_cookies accepts 1 required parameter (session_id) and 1 optional parameter. All parameters are sent as JSON in a POST request to /api/execute/http_session_get_cookies.
Is http_session_get_cookies detectable by anti-bot systems like Cloudflare or DataDome?
No. http_session_get_cookies executes inside Owl Browser's Chromium engine, which applies fingerprint spoofing at the C++ source level rather than through JavaScript patches. Every tool call shares the same consistent, human-like fingerprint, so anti-bot systems such as Cloudflare, DataDome, and Akamai see an ordinary browser.
Related Tools
browser_get_cookiesRetrieve all cookies from the browser context with full details including httpOnly, secure, sameSite, domain, path, and expiration. Optionally filter by URL to get only relevant cookies.
browser_set_cookieSet a cookie in the browser context with full control over all attributes. Supports domain, path, secure, httpOnly, sameSite, and expiration settings. Useful for injecting session tokens or test cookies.
browser_delete_cookiesDelete cookies from the browser context. Can delete all cookies, cookies for a specific URL, or a specific cookie by name. Useful for testing login flows or clearing session state.
browser_update_profile_cookiesUpdate the profile file with the current cookies from the browser. Call after login to persist session cookies. Only updates cookies, preserving other profile settings.
http_session_set_cookiesImport cookies into a session. Accepts either a JSON array of cookie objects with domain, name, value, path fields, or Netscape cookie format lines. Useful for importing cookies from browser contexts (browser_get_cookies) into HTTP sessions for non-DOM operations.
browser_create_contextCreate a new isolated browser context with its own cookies, storage, and optional proxy configuration. Each context acts as an independent browser session. Use this to create multiple isolated browsing sessions, configure proxy/Tor connections, load browser profiles with saved fingerprints, and enable/disable LLM features. Returns a context_id to use with other browser tools.