Skip to main content
Oviond’s REST API uses Bearer token authentication. Every request must include a token in the Authorization header. For programmatic access, generate an API key from your settings. This page explains how to create an API key and pass it correctly in your requests.
The Oviond web app signs in with Supabase Auth and sends a session JWT as its Bearer token. For your own scripts and integrations, use an API key instead, as described below.

​
Generate an API key

API keys require the Manage API keys permission, so you must be an account owner or admin.
1

Open API key settings

In the Oviond app, go to Settings → API keys.
2

Create a new key

Click Create. Give it a descriptive name (for example, “Zapier integration” or “Custom dashboard”) so you can identify it later. Choose an access level: View, Edit, or Full. The key inherits your role and client access, capped at the access level you pick.
3

Copy and store the key

Your key is shown once and starts with oviond_. Copy it and store it securely — you won’t be able to see the full key again after you close this dialog.
Treat your API key like a password. Do not commit it to version control or expose it in client-side code.

​
Make authenticated requests

Include your API key in the Authorization header as a Bearer token on every request:
Replace YOUR_API_KEY with the key you generated above.

​
Example: Fetch your account

A successful response wraps your user profile in the standard success envelope. All fields are snake_case:

​
Authentication errors

Errors return the standard error envelope:
If you receive a 401, double-check that you’ve included the Authorization: Bearer <key> header and that the key hasn’t been revoked.

​
Manage your API keys

You can list, create, and revoke API keys at any time from Settings → API keys in the app, or via the API Keys API.
Each API key is scoped to your account and inherits the role and client access of the person who created it, capped at the key’s access level.