Oviond’s data-source discovery and connection tools now live together under /v1/datasources, giving API integrations one clearer place to discover, inspect and test reporting connections.

The new describe response brings a data source’s available views, required settings, default view, metrics and dimensions together in one request. Connection tests now use the saved connection and record the result on it, so the connection status shown in Oviond stays aligned with the test.

If your integration uses the previous /v1/data discovery endpoints, update those routes to /v1/datasources. Data queries and resource requests are unchanged. Full migration details: https://docs.oviond.com/changelog/2026-08

Oviond now validates goal queries and calculated-metric formulas when they are created or updated through the API or MCP.

If a query contains an unknown data source, metric or dimension, Oviond returns a clear error instead of saving the configuration and leaving you with an empty widget later. Calculated metrics can also now be created correctly through API and MCP using metric, number and operator tokens.

Existing goals and calculated metrics are unaffected. The new checks apply only when creating or updating them, making new reporting automations safer and much easier to troubleshoot.

Oviond now validates more report and automation settings against their documented values, including date presets, comparison modes, number formats, summary methods, widget types and Slack or Discord notification channels.

Typos and unsupported values now return a clear error instead of being stored and quietly producing the wrong result. This should make API and MCP workflows more predictable, especially when creating widgets or automating reports at scale.

Developer note: widget metrics and dimensions must now be sent as objects, such as {"value": "clicks"}, rather than bare IDs. Widgets created in the Oviond app already use this format; only external integrations that send bare metric or dimension IDs need updating.

Each client can now use the number format that fits its region, independently of its currency.

Choose the thousands and decimal separators under Settings → General — for example, 1,234.56 for the US or 1.234,56 for Germany. Existing clients keep their current formatting until you change it.

The same setting is available through the API using the client number_format field.

Textbox widgets can now include variables that fill in live client and report details automatically.

Insert details such as client name, project name, date range, account name, client manager, or report URL from the text toolbar. The values resolve when a report is viewed, shared, or exported to PDF.

Write reusable report introductions once instead of updating the same text for every client and reporting period.

Two new Ahrefs dataviews are available in the report builder: Organic Traffic and Rank Tracker.

Report on organic keywords, estimated traffic and traffic value over time, alongside tracked keyword positions and movement.

Existing Ahrefs widgets are unchanged.

Oviond now connects to Moz and Vbout.

Use Moz to report on domain authority and link metrics. Use Vbout to report on email campaigns and campaign performance.

Connect either platform from the Data Sources tab inside a client's project.

PDF generation and report screenshots now run on a dedicated rendering service.

Large reports should render more consistently and be less likely to time out when the system is busy.

There is nothing new to configure — PDF exports and automation attachments work the same way as before.

The data-source connection panel now includes a profile manager.

Open a connection under Settings → Data sources to see its status, review the clients using it, and update credentials without leaving the page.

This makes re-authorising or repointing shared connections much easier.

Agency and client logos once again appear in the header of report and authentication emails.

Email branding follows the same logo source as the rest of your workspace. If no logo is configured, Oviond falls back cleanly to the workspace name.