Use the Oviond REST API to manage Oviond resources programmatically.
This article is for developers, technical operators, and agencies building custom workflows around Oviond.
You will need:
access to your Oviond account,
an Oviond API key,
a safe place to store the key,
the API base URL: `https://api.oviond.com`.
Do not expose API keys in screen captures, prompts, shared documents, source code, or support tickets.
Use the live API documentation to confirm exact endpoints, methods, request bodies, and response shapes:
`https://api.oviond.com/docs`
Generate an API key from the API keys area in the Oviond app.
Store the key securely as a secret or environment variable.
Send requests to:
`https://api.oviond.com`
Add the API key to the Authorization header:
Authorization: Bearer YOUR_API_KEYFor requests with a body, send JSON with:
Content-Type: application/jsonBefore creating or changing anything, test the connection with a safe read request from the API docs.
Your integration should be able to authenticate with the Oviond REST API and call supported endpoints for account, clients, projects, pages, widgets, data sources, templates, themes, automations, users, media, and other resources.
The API key is missing, invalid, or not sent as a Bearer token.
The authenticated account or key does not have permission for that action.
Check the endpoint path and resource ID.
Check the request body against the OpenAPI schema.
The account has hit the rate limit. Wait before retrying.
Send Oviond support:
endpoint path,
HTTP method,
status code,
redacted request body,
error response,
what you expected to happen.
Never send your API key.