Record a Billing system event
POST/events
Appends one business event for the runtime user resolved from X-Principal-Id and X-User-Id. Billing Events are facts recorded inside the Billing bounded context; they are not limited to chargeable events and do not themselves carry pricing, reward, or consumer-routing semantics. The body event_key is a developer-chosen uniqueness boundary within the resolved runtime Billing User. The first accepted write becomes the stored event. Every later submission of that key for the same user returns 200 and the original event, regardless of differences in event fields, payload, or labels. Different users may reuse the same key. Choose the key granularity to match the occurrence being modeled, such as one signup or one login per day.
Request
Responses
- 200
- 201
- 401
- 403
- 422
- 429
- 503
Existing event for this user and event key (first write wins)
Created
Unauthorized
Forbidden (realm/account mismatch, billing account not derived from your session/principal, or insufficient role)
Unprocessable Entity (validation, visibility, or binding/meter unresolved)
Rate limited
Response Headers
Seconds to wait before retry.
Provider unavailable, transient failure, or an ambiguous provider mutation reported as BILLING.PAYMENT_PROVIDER_OUTCOME_UNKNOWN.