Set the quantity of a Limitation Feature (write)
push_usage_quantitySets the absolute quantity of a customer's limitation feature, such as seats or users, so ProAbono bills provisioned capacity instead of occupied usage.
Instructions
WRITE. Sets the current quantity of a Limitation Feature of a customer to an absolute value -- seats, projects, users. Send the quantity the application has provisioned, the seats bought and not the seats occupied: that is what ProAbono bills on. The value is absolute, so sending it twice is harmless, which is why this write takes no increment. Limitation Features only; use push_usage_increment for a metered Feature and push_usage_enabling for an OnOff one. Quote it first with quote_usage_change when it is billable.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"customer_ref": "<customer_ref>",
"feature_ref": "<feature_ref>",
"quantity_current": "<quantity_current>"
},
"name": "push_usage_quantity"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date_stamp | No | When the change happened, ISO 8601 in UTC. Defaults to now. A future date is not supported. | |
| feature_ref | Yes | Shared reference of the Feature (ReferenceFeature). | |
| customer_ref | Yes | Shared reference of the customer. | |
| subscription_id | No | Which subscription the Usage belongs to. Needed when the customer has several running. | |
| quantity_current | Yes | The absolute quantity now provisioned. Replaces the current value. |