Attribute session to ticket

post

https://api.revenium.ai/profitstream/v2/api/sessions/{sessionId}/attribution

Record a point-in-time attribution between a coding-assistant session and a ticket. A different ticket opens a new time interval; re-posting the same ticket as the current interval (without effectiveFrom) is a no-op. An explicit effectiveFrom is idempotent on (org, sessionId, effectiveFrom): it updates that interval in place (last-write-wins).

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

sessionId

string

required

Opaque identifier for the coding-assistant session (e.g. Claude Code session UUID).

Query Params

teamId

string

Unique identifier of the team (organization). Format: Revenium hashid (URL-safe encoded string). Optional when authenticating with a metering API key: the team is then derived from the key's own organization, and an explicit value that names a different organization is rejected. Required when authenticating on the management plane (WRITE-scoped API key or JWT session).

Body Params

Session → ticket attribution payload

ticketId

string | null

ticketTitle

string | null

reason

string | null

source

string

enum

Allowed:

subscriberEmail

string | null

repo

string | null

branch

string | null

effectiveFrom

date-time | null

splits

array of objects | null

Weighted multi-ticket split (PRODUCT-2656 PR5), 1-10 entries. Mutually exclusive with ticketId; exactly one of the two must be supplied. Weights are normalized server-side to sum to 1.0 (tolerance ±0.01) and apportion the SERVER-MOVABLE cost subset only — rows already customer-attributed are left out of both the assignment and the denominator. Gated behind the coding-assistant-splits-enabled feature flag.

splits

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

application/hal+json

*/*

200Attribution recorded successfully.

400Invalid request parameters or validation error.

401Unauthorized - Authentication required.

403Forbidden - User does not have access to the requested team.

404Team not found.

409Conflict - a concurrent write is recording the same (session, effectiveFrom) interval.

422Unprocessable entity - semantic validation failure. Returned when effectiveFrom is in the future (beyond a small clock-skew tolerance); an attribution cannot take effect before the work it labels.

429Too Many Requests

500Internal server error.