Skip to main content
POST
Set or remove one org member's monthly mu spending limit

Authorizations

Authorization
string
header
required

Supabase JWT token in Authorization: Bearer header

Query Parameters

org_id
string
required

Target org id. REQUIRED — a mu write never falls back to the caller's primary org. A non-member, or a member outside owner/admin, is denied 403.

Body

application/json
userId
string
required

The org member whose limit is being set. Must be a member of org_id.

Required string length: 1 - 256
hardCapMmuPerMonth
string | null
required

Monthly hard cap in millimu as a whole-number string (billing casts it to bigint, so it is not sent as a JSON number). "0" is a real setting — this member may spend nothing this month — and is deliberately distinct from null, which REMOVES the limit. The field is required: a missing field is a 400, never a silent removal.

Pattern: ^(0|[1-9]\d*)$

Response

Limit set or removed. {budget: <mnemom-billing Budget row>}.

budget
object