Skip to content
Developers
Get an API token

Freshness and releases

How each Novi product numbers its releases, how often data moves, and how to tell which version you have.

View MarkdownOpen in Claude(opens in a new tab)

Data refreshes and API releases are separate: check both.

Novi UDM Data (v4) Novi Forecasts API Novi EVA API
Release number Novi release numbers, such as 26.4.3. Each release also records its data model version API version in semver, such as 1.102.0, plus the platform release that carries it, such as 1.31 Path version /v1. Release numbers not published yet
Current Release 26.4.3, 2026-10-29, data model version v1.6.80 API 1.103.0 on platform 1.32, 2026-11-18 /v1
Data refresh On a regular schedule. Each query returns the latest load. Bulk files are built every weekday Each model set’s dataset has an as-of date Not published yet
What you have The data dictionary names the release. DOWNLOADS_FULL and DOWNLOADS_DIFF give each file’s RUN_ID GET /health returns version and app_version. GET /dataset returns as_of MCP data results carry schema_version
Per-table refresh times Not published yet Not applicable Not published yet
  • The current release, 26.4.3, is the first release of Novi Wells in Snowflake. Every view and column in it is new.
  • Between releases, data refreshes on a regular schedule. Existing columns can change through fixes, improved logic or deprecation. They are not removed.
  • Columns documented but not yet released are marked staged. You cannot query them.
  • 22 of the 29 base views carry CREATED_AT and UPDATED_AT, so you can pick up only what changed.
  • Bulk diff zips carry changes from one weekday run to the next. DOWNLOADS_DIFF keeps the last 7 runs.
  • /api/v1 only grows. Some releases tighten validation, so a request accepted loosely before can become an invalid-input error.
  • A done plan does not change, except its name and whether it is saved. Curve points past model_months can move with a release.
  • Legacy Forecasts, your company’s earlier predrill forecast runs served as read-only plans, can change. Read one again when its origin.indexed_at is newer.

The REST API is versioned by its /v1 path. MCP data results carry schema_version in every envelope.

Item Status
A “data as of” time and refresh cadence for each Novi UDM Data view Planned