Skip to content

Tell which error a person was shown

POST
/v1/events
curl --request POST \
--url https://beta-api.plune.ai/v1/events \
--header 'Content-Type: application/json' \
--cookie plune_session=<plune_session> \
--data '{ "kind": "error.shown", "code": "session_required" }'

The dashboard says which error code it showed the person of the session (#2494, ADR 0060 addendum 10.11.2026 §4): the code of the refusal’s body, or http_<status> when it has none. It becomes one product usage event error.shown for the signed-in user, kept by the code alone: no text, no address, no project. kind takes error.shown and nothing else, and code matches ^[a-z0-9_.:-]{1,64}$. The answer is 204 whether the events of this Plune are on or off, and when they are off nothing is written. The session alone: an API token gets 403 session_required. Thirty calls a minute.

Media type application/json
object
kind
required
string
Allowed values: error.shown
code
required
string
/^[a-z0-9_.:-]{1,64}$/
Examples

The refusal named its code

{
"kind": "error.shown",
"code": "session_required"
}

Taken (or the events are off: nothing written)

Not JSON, another kind, or a code outside the pattern

Media type application/json
object
error
required
string
Example
{
"error": "validation failed — code: Invalid string: must match pattern /^[a-z0-9_.:-]{1,64}$/"
}

No / invalid session

An API token

Media type application/json
object
error
required
string
Example
{
"error": "events are sent by the signed-in dashboard — an API token cannot",
"code": "session_required"
}

Rate-limited: the per-route throttle, or the per-minute request limit of the plan an API token counts by (#1442; the body names the plan, #2092). Retry-After carries the seconds until the window rolls over.

Media type application/json
object
error
required
string
Example generated
{
"error": "example"
}
Retry-After
integer

Seconds until the window rolls over