API

Introduction

List API keys

Returns API key metadata for the authenticated project. Secret values are never included in list responses.

GET
https://api.novaai.com/v1/api-keys

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

Project whose key metadata should be returned.

limit

integer

optional

Maximum number of key records to return in one page.

cursor

string

optional

Pagination cursor from a previous list response.

Response behavior

A successful GET 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 GET /v1/api-keys from a trusted server environment. Keep your NovaAI API key out of browser bundles and pass only the data required for list api keys 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.

GET/v1/api-keys
GET /v1/api-keys HTTP/1.1
Authorization: Bearer NOVA_API_KEY
Content-Type: application/json
200Success response
{
"id": "list_api_keys_01",
"object": "nova.resource",
"status": "succeeded"
}
400Invalid request
{
"error": {
"message": "Invalid request",
"type": "invalid_request_error",
"code": "invalid_parameter"
}
}

Create a free website with Framer, the website builder loved by startups, designers and agencies.