API Reference
Log In
API Reference

List a session's ticket attributions

Returns every recorded attribution interval for the session, current interval first (effectiveFrom descending), so element 0 is what the session is attributed to now.

Response shape depends on the caller's plane (PRODUCT-2671). A management-plane caller (WRITE-scoped API key or JWT) receives every field, including the provenance of the write that created the interval (apiKeyId, createdBy — the hashid of the API key used, null for browser-session writes and intervals recorded before provenance was captured, and the email of that credential's owner) and of the write that most recently modified it (modifiedBy, updated). A METERING-scoped API key receives only ticketId, ticketTitle and effectiveFrom — the fields it needs to read back what a session is currently attributed to; apiKeyId, createdBy, modifiedBy and subscriberEmail are omitted from the response entirely for that caller, never nulled.

Dual-auth, mirroring the POST: callable by the management plane, or by a METERING-scoped API key restricted to its own organization (see [io.hypercurrent.profitstream.service.v2.security.AuthenticationExpressionService.canReadSessionAttribution]).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

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

Query Params
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).

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/hal+json
*/*