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

required

Unique identifier of the team (organization). Format: Revenium hashid (URL-safe encoded string).

Body Params

Session → ticket attribution payload

ticketId

string

required

Ticket identifier matching ^[A-Za-z][A-Za-z0-9_]{0,63}-\d{1,10}$ or the literal 'none'

ticketTitle

string | null

Human-readable ticket title, ≤ 500 characters

reason

string | null

Reason for associating this session with the ticket, ≤ 500 characters

source

string

enum

required

Source coding assistant

Allowed:

subscriberEmail

string | null

Email of the subscriber/developer running the session, ≤ 255 characters

repo

string | null

Repository name or URL, ≤ 255 characters

branch

string | null

Branch name, ≤ 255 characters

effectiveFrom

date-time | null

ISO-8601 timestamp from which this attribution is effective; defaults to server receive time

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 (e.g. malformed ticketId pattern).

429Too Many Requests

500Internal server error.