Create a new usage limit that references a meter.
Limits enforce caps on meter values over time periods. You can scope limits to:
The all_time period creates limits that never reset (useful for resource counts).
API Key or Personal Access Token (PAT). When using PAT, include X-Project header.
Human-readable name for the limit
1ID of the meter this limit references
1Limit value
x > 0Time period for the limit. Boundaries are calculated from customer billingCycleStart.
hour, day, week, month, annual, all_time Customer ID to scope the limit to
Key-value pairs to filter or scope the rule. Keys must be alphanumeric with underscores (max 64 chars). Values are strings (max 256 chars).
Alert thresholds as percentages
1 <= x <= 100Limit created
Unique identifier for the limit
ID of the project that owns this limit
Human-readable name for the limit
ID of the meter this limit references
Limit value
Time period for the limit (hour, day, week, month, annual, all_time). Period boundaries are calculated from the customer billingCycleStart.
Additional dimension filters for scoping
ISO 8601 timestamp when the limit was created
ISO 8601 timestamp when the limit was last updated
Optional customer ID to scope the limit to
Alert thresholds as percentages (e.g., [80, 100])
1 <= x <= 100