Set resource billing controls
Saves the monthly limit and priority together, atomically. Both observed revisions are required. Conflicts leave both settings unchanged. Null removes a limit; zero blocks new charges. Existing paid service continues. Requires an organization API key with the stated billing scope, or a signed-in team owner or admin. Project and client credentials cannot access these controls. Billing must be configured. Writes require Pay-As-You-Go. These controls never enable charging of unpriced usage.
Requires a team API key with billing:manage. Project tokens are not accepted.
Authorizations
Send your team API key or project token as Authorization: Bearer <token>. The credential must have the required permissions. Project tokens can access only their own project.
Path Parameters
Specifies scope for this path parameter.
Allowed values
project, customer, number Identifier of the resource affected by this event.
Value constraints
Body
Specifies limit credits for this schema.
Accepted alternatives
Value constraints
0 <= x <= 1000000Must be a multiple of 0.000001Specifies priority for this schema.
Value constraints
0 <= x <= 1000000Specifies expected budget revision for this schema.
Value constraints
0 <= x <= 2147483646Specifies expected priority revision for this schema.
Value constraints
0 <= x <= 2147483646Response
Success
Structured data carried by this object.