Sessions

Dump the session's cookies and storage

The only endpoint that returns credentials. Works only while the session is active. The response is marked Cache-Control: no-store, private. Reading does not slide the TTL.

Pitfalls:

  • After release, delete, or TTL expiry the context is purged immediately and permanently. A released session answers 410 ERR::SESSION::RELEASED; an expired one 410 ERR::SESSION::EXPIRED. Do not retry a 410: create a new session and log in again.
  • Store this object yourself if you need it later. You can POST its session_context back to POST /v1/sessions to clone the session.
  • 500 ERR::SESSION::STATE_CORRUPT means the stored context cannot be opened (retired key, newer schema, corrupt blob). It will not recover; create a new session.
get/v1/sessions/{sessionID}/context

Request

  • Base URL: https://api.spicrawl.com
  • URL: https://api.spicrawl.com/v1/sessions/{sessionID}/context
  • Auth: HTTP bearer

Response

The live context.

session_idstring required

The session id.

schema_versioninteger required

Stored format version. Currently 1.

fingerprintobject nullable

Stored browser fingerprint, or null when none. Omitted only in edge cases.

domain_scoresobject

Per-domain standing, as stored. {} when empty.

retired'expired' | 'usage_exhausted' | 'explicit'

Why a worker retired the session. Absent while usable.

usage_countinteger required

Scrapes that used the session.

created_atstring date-time required

Creation time.

last_used_atstring date-time nullable required

Last use, or null if never used.

expires_atstring date-time required

Current sliding expiry.

warningstring required

Fixed reminder that this context is destroyed on release, delete or expiry. Save the object now if you need it later.

Changes

No recorded changes to this operation across all 1 revision of this API.