How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

StakPak Sessions API

The Sessions API from StakPak — 4 operation(s) for sessions.

StakPak Sessions API is one of 20 APIs that StakPak publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sessions. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 8 operations across 4 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://apiv2.stakpak.dev, http://localhost:4000.

8 operations 4 paths 30 schemas 1 DELETE4 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://apiv2.stakpak.dev
Authentication
HTTP Bearer, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

StakPak Sessions API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Api_Key). It accepts HTTP bearer tokens (JWT) (Token). An API key is passed in the cookie as .idToken (cookie).

Paths & Operations 8

Across 4 paths, the API surfaces 8 operations — 1 DELETE, 4 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Sessions 8
GET
/v1/sessions
List Sessions
list_sessions_handler 5 params → 200400
POST
/v1/sessions
Create Session
create_session_handler body → 200400
GET
/v1/sessions/checkpoints/{checkpoint_id}
Get Checkpoint
get_checkpoint_handler 1 param → 200404
GET
/v1/sessions/{session_id}
Get Session
get_session_handler 1 param → 200404
DELETE
/v1/sessions/{session_id}
Delete Session
delete_session_handler 1 param → 200404
PATCH
/v1/sessions/{session_id}
Update Session
update_session_handler 1 param body → 200400404
GET
/v1/sessions/{session_id}/checkpoints
List Checkpoints
list_checkpoints_handler 4 params → 200404
POST
/v1/sessions/{session_id}/checkpoints
Create Checkpoint
create_checkpoint_handler 1 param body → 200400404

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are ChatMessage (13 properties), SessionSummary (10 properties), Session (9 properties), CheckpointSummary (7 properties). Each schema is shown below with its type and property counts.

LLMTokenUsage
object
4 properties 3 required
ErrorBody
object
2 properties 2 required
FunctionCall
object
2 properties 2 required
ContentPart
object
3 properties 1 required
CreateSessionResponse
object
Response for creating a session
2 properties 2 required
UpdateSessionResponse
object
Response for updating a session
1 property 1 required
ErrorResponse
object
1 property 1 required
ListSessionsResponse
object
Response for listing sessions
1 property 1 required
UpdateSessionRequest
object
Request body for updating a session
2 properties
ChatMessage
object
13 properties 1 required
Session
object
Full session with active checkpoint
9 properties 6 required
CreateSessionRequest
object
Request body for creating a new session
4 properties 2 required
GetSessionResponse
object
Response for getting a single session
1 property 1 required
SessionSummary
object
Summary for listing sessions (without full checkpoint state)
10 properties 8 required
Role
string
ListCheckpointsResponse
object
Response for listing checkpoints
1 property 1 required
SessionVisibility
string
ImageUrl
object
2 properties 1 required
CheckpointState
object
Checkpoint state - only messages, no workflow-specific fields
1 property
CreateCheckpointRequest
object
Request body for creating a checkpoint in an existing session
2 properties 1 required
SessionStatus
string
MessageContent
Checkpoint
object
Full checkpoint with state
6 properties 5 required
DeleteSessionResponse
object
Response for deleting a session
2 properties 2 required
GetCheckpointResponse
object
Response for getting a single checkpoint
1 property 1 required
ToolCall
object
3 properties 3 required
PromptTokensDetails
object
4 properties
CreateCheckpointResponse
object
Response for creating a checkpoint
1 property 1 required
ModelInfo
object
Model information for tracking which model generated a message
2 properties 2 required
CheckpointSummary
object
Summary for listing checkpoints
7 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stakpak-sessions-api-openapi.yml Raw ↑

Other APIs StakPak publishes across the network.

StakPak Account API
StakPak Account (V2) API
StakPak Agents API
StakPak Agents (V2) API
StakPak Billing (V2) API
StakPak Chat API
StakPak Commands API
StakPak Knowledge API
StakPak Knowledge Registry API
StakPak MCP API
StakPak Memory API
StakPak Memory (V2) API
Where this information came from

This is an independent, third-party profile of StakPak Sessions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.