/api/v1/releases/deploysDeploys & request sessions
Tell Fictura what shipped, so issues can name suspect commits, and how a backend's requests went, for release health.
npx fictura-sdk deploy records a deploy from CI, and the Python and Node SDKs send request sessions. This page is the contract behind them.
Deploys
Send your SDK app key as x-api-key, or Authorization: Bearer fk_data_… with the releases:write scope.
Up to 200 characters.
Up to 40 characters. Defaults to production.
The deployed commit, and an http(s) link to the repository.
finished_at defaults to now.
Each: sha (7 to 64 hex characters, required), optional message, author, timestamp and files (the paths it changed). files is what lets an issue match its stack to a commit.
curl -X POST https://api.fictura.co/api/v1/releases/deploys \
-H "Authorization: Bearer fk_data_..." \
-H "Content-Type: application/json" \
-d '{"release":"2.0.68","commit_sha":"9fceb02","commits":[{"sha":"9fceb02","message":"Fix checkout","files":["src/checkout.ts"]}]}'The 200 is {"ok": true, "deploy_id": "…", "commits": 1}. A bad body answers 400 invalid_body with details.
Request sessions
POST /api/v1/sessions/aggregates with your SDK app key as x-api-key. Every request is one session, counted per minute by how it ended.
curl -X POST https://api.fictura.co/api/v1/sessions/aggregates \
-H "x-api-key: gk_..." \
-H "Content-Type: application/json" \
-d '{"release":"2.0.68","environment":"production","aggregates":[{"started":"2026-10-01T09:14:00Z","ok":1180,"errored":4,"crashed":1}]}'aggregates holds at most 500 entries, or send one flat with started, ok, errored and crashed at the top level. started can be up to 7 days old and up to an hour ahead. Counts for the same release, environment and minute add up. release is up to 200 characters and environment up to 40.
The 200 is {"ok": true, "stored": 1, "rejected": 0}, where rejected counts entries skipped as unreadable. A body with no usable shape, or over 500 entries, answers 400 invalid_body.