Introduction

This section covers the API at api.quiver.ai.

If you are using the app at app.quiver.ai, start with the App docs.

Authentication

The QuiverAI API uses API keys with bearer authentication.

Create and manage keys in API Keys.
Follow the Quickstart to run your first call.
Keep keys server-side and load them from environment variables or secret managers.

Authorization: Bearer <QUIVERAI_API_KEY>

Send API requests to: https://api.quiver.ai/v1 Use these headers on JSON requests:

Authorization: Bearer <QUIVERAI_API_KEY>
Content-Type: application/json

Each successful request to generation or vectorization endpoints uses 1 credit.
Billing is per request, including requests where n > 1.
In Usage, API calls appear with a request ID.

The API returns standard HTTP status codes and a JSON error payload. Current public API rate limit for SVG endpoints:

20 requests per 60 seconds
Scoped per organization
Applied to POST /v1/svgs/generations and POST /v1/svgs/vectorizations
Exposed through X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset

{
  "status": 429,
  "code": "rate_limit_exceeded",
  "message": "Rate limit exceeded",
  "request_id": "req_01J..."
}

400 Bad Request: malformed body, missing required fields, or invalid parameter values.
401 Unauthorized: API key missing, malformed, or revoked.
402 Payment Required: insufficient credits. Purchase more at Billing.
403 Forbidden: account is frozen or blocked.
404 Not Found: the requested model does not exist.
429 Too Many Requests: rate limit exceeded. Retry after the period in the Retry-After header.
500 Internal Server Error: unexpected server error.
502 Bad Gateway: the upstream inference service returned an error.
503 Service Unavailable: the inference backend could not be reached.

Use exponential backoff for retries and respect Retry-After when present.

QuiverAI provides an official Node.js SDK:

npm install @quiverai/sdk

For other languages, call the REST API directly.