Skip to main content
Use runs.consume before a billable step when its usage amount is known. It applies a synchronous metered event to the run and can reject the step before it creates cost. If the provider has already incurred variable usage, use runs.settle.

Request

string
required
The budgeted run ID.
string
required
The specific feature or entitlement to consume against the running budget.
string
required
Logical key used to deduplicate this run consumption event.
string
Broad event kind configured in Unprice.
string
Optional event ID from your system.
number
Optional epoch-millisecond event timestamp.
object
Event properties used by meters. The targeted feature’s meter reads the relevant field from this object.

Response

boolean
required
Whether the run consumption event was accepted.
string
required
Decision reason. Expected values include accepted, duplicate, insufficient_budget, expired, not_running, and entitlement_denied.
object
required
Current budget run summary after the decision.