Hanzo
OpenapiBilling

Changes one spend cap: raise or lower the ceiling, flip enforcement, retune the…

Changes one spend cap: raise or lower the ceiling, flip enforcement, retune the rate limit. Only the fields the body carries move.

PATCH /v1/billing/alerts/{id}

Addresshttps://api.hanzo.ai/v1/billing/alerts/{id}
MethodPATCH
Operationpatch_billing_alerts_by_id
AuthAuthorization: Bearer $HANZO_API_KEY

Changes one spend cap: raise or lower the ceiling, flip enforcement, retune the rate limit.

Only the fields the body carries move. Every mutable field is optional, and an absent one is PRESERVED rather than reset — so a change that flips enforcement cannot silently wipe the threshold it enforces.

A cap belonging to another org is a 404, not a 403: a guessed id must not become an oracle for what anyone else holds.

A named handler, not a closure, so zipdoc can lift this prose into the registry.

Request

10 fields, body application/json (required).

FieldInTypeRequiredDescription
idpathstringyes
enforcebodyboolean
idbodystring
projectbodystring
rateLimitRpmbodyinteger
servicebodystring
softPctbodyinteger
subjectbodystring
thresholdbodyinteger
titlebodystring

Response

StatusBodyMeaning
200Alertok

200 body — 18 fields.

FieldInTypeAlwaysDescription
createdAtbodystring
currencybodystring
enforcebodyboolean
idbodystring
overbodyboolean
periodbodystring
periodSpentCentsbodyinteger
projectbodystring
rateLimitRpmbodyinteger
resetsAtbodystring
servicebodystring
softPctbodyinteger
thresholdbodyinteger
titlebodystring
triggeredAtbodystring
updatedAtbodystring
userIdbodystring
warnbodyboolean

Failure carries the platform error shape — see Errors.

Examples

hanzo billing alerts update <id>

Billing API · All Hanzo APIs · Interactive reference

How is this guide?

On this page