Skip to content
Developers
Get an API token

Accounts and access

What you need for each Novi product, who grants it, and what you receive.

View MarkdownOpen in Claude(opens in a new tab)
Product You need Who sets it up You receive
Novi UDM Data (v4) A subscription that names your basins Novi. Start with your Customer Success Advisor or support@novilabs.com A reader-account welcome email, a setup script for your own Snowflake account, or BI connection details
Novi Forecasts API A Novi login at your company’s host, with Access Forecasts. Access MCP to see the API tokens page Your company’s Novi administrator grants the permissions through a role. You create your own tokens Novi API tokens
Novi EVA API (REST) An EVA organization You create a Developer API Token on EVA’s Organization Settings page A key for the x-api-key header
EVA MCP server Preview Access EVA and Access MCP, and membership in the company whose host you use Your company’s Novi administrator grants Access MCP through a role A sign-in from your assistant
M&A Intelligence MCP server Preview Access Intelligence M&A. Access MCP to sign in from an assistant Your company’s Novi administrator A sign-in, or use of a Novi API token
Path What happens Who acts
Reader account Novi adds each person, who gets a welcome email with a login. The role is DATA_READER and the warehouse NOVI_WH Novi
Share into your account Your Snowflake administrator sends Novi your account details, then runs the setup script Novi emails, novi_setup.sql. You pay for the warehouse that runs your queries Novi, then your Snowflake administrator
BI or lakehouse connection Preview Novi creates one machine user and sends connection details with a private key link that works for 72 hours Novi, on request
  • Every path shows only the basins in your subscription.
  • The same database can also hold NOVI_INTEL, NOVI_MA_INTEL and NOVI_NDN. Each needs its own subscription.
  1. Sign in to Novi at your company’s host. Your user needs the Access Forecasts permission to use the API.
  2. To create tokens you also need Access MCP. Without it, API tokens does not appear in the Forecasts app’s Settings.
  3. Create a token under Settings, then API tokens. See Authentication.

A token sees your company’s plans and data and nothing else.

  • REST: create a Developer API Token on the Organization Settings page in EVA. The key acts for your EVA organization. It is not a Novi API token.
  • MCP server: your Novi user needs Access EVA and Access MCP and must belong to the company whose host you use. API keys and Novi API tokens don’t work here: you sign in from your assistant. See Connect Claude to EVA.

The MCP server needs Access Intelligence M&A. Signing in from an assistant also needs Access MCP. A Novi API token for a user with Access Intelligence M&A works too. See Agents and MCP.