Cookies

Veyak provides dedicated tools to inspect, manage, and test HTTP cookies across your API requests.

Overview

Cookies are critical for session-based authentication, token rotation, and tracking state across stateful web services. Veyak separates cookie workflows into:

  1. Request Cookies — Manually defined cookies sent with your outgoing HTTP requests.
  2. Response Cookies — Automatically extracted Set-Cookie headers parsed from server responses.

Setting Request Cookies

To send cookies with your request:

  1. Open any HTTP request tab.
  2. Click the Cookies sub-tab in the request editor.
  3. Click Add cookie (or the + button).
  4. Fill in the fields:
Field Description Example
Name Cookie key name session_id
Value Cookie payload or token abc123xyz789
Domain Target domain scope api.example.com
  1. You can add multiple cookies. Each cookie is sent via the standard HTTP Cookie header during the call.
  2. To delete a cookie, click the Trash icon next to the row.

Inspecting Response Cookies

When a server sets one or more cookies via the Set-Cookie response header:

  1. Send your HTTP request.
  2. In the Response Panel, switch to the Cookies sub-tab.
  3. Veyak automatically extracts each cookie, displaying:
    • Cookie Name
    • Value
    • Assigned Domain
  4. This makes it simple to verify whether login endpoints, session generators, or csrf tokens are issuing the expected cookie attributes without having to parse raw header strings manually.

Using Environment Variables with Cookies

Just like headers and URLs, cookie values can reference environment variables:

Name:   session_id
Value:  {{ACTIVE_SESSION_TOKEN}}
Domain: {{API_DOMAIN}}

When switching environments from dev to production, cookie values update automatically.