Update rate-limit policy
Updates project-level request controls used to protect production workloads and manage quota behavior.
Authentication
Send a project-scoped NovaAI API key in the Authorization header using the Bearer scheme. Requests without valid credentials return 401 Unauthorized.
Authorization
string
required
Request properties
project_id
string
required
Identifier of the project to update.
requests_per_minute
integer
optional
Requested request-rate ceiling for the project.
burst_limit
integer
optional
Optional temporary burst allowance.
Response behavior
A successful PATCH request returns a structured NovaAI resource response. Validate the returned identifier before persisting it, and handle 400 Bad Request for malformed input or 401 Unauthorized for invalid project credentials.
Integration notes
Use PATCH /v1/projects/{project_id}/rate-limits from a trusted server environment. Keep your NovaAI API key out of browser bundles and pass only the data required for update rate-limit policy in each request.
Validate inputs before sending the request, log the returned request identifier for troubleshooting, and use exponential backoff for temporary failures or rate-limit responses. Treat malformed payloads and authorization failures as non-retryable until corrected.
Error handling
Inspect the error type and code returned by NovaAI before retrying. Correct invalid parameters for 400 responses, refresh or replace credentials for 401 responses, and wait before retrying requests that are temporarily limited.