Profiles

Profiles store cookies and local storage for Chromium sessions. The profile state itself is never returned by the API. It only goes into a session.

Name rules

• 1 to 64 characters
• Letters, digits, periods, underscores, or hyphens
• First character must be a letter or digit
• Pattern: ^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$

Use a profile on create

{
  "engine": "chromium",
  "profile": "my-login-1",
  "country": "us"
}

The session starts with that profile when it exists. When the session ends, cookies and local storage are saved back and the 30-day retention clock resets from updated_at.

List profiles

curl "https://stealth-staging-direct-zjk4365f7y54.geonode.com/v1/profiles" \
  -H "X-API-Key: YOUR_API_KEY"

Each item includes name, updated_at (Unix seconds), bytes, cookies, and origins. Derive expiry as about 30 days after updated_at. There is no separate expiry field.

Delete a profile

curl -X DELETE "https://stealth-staging-direct-zjk4365f7y54.geonode.com/v1/profiles/my-login-1" \
  -H "X-API-Key: YOUR_API_KEY"

Success returns 204.

Notes

• Firefox sessions do not use profiles
• Never put real cookies or customer profile data in docs or tickets
• If save fails at end, check profile_note on the session (empty, over_cap, unreadable)