Skip to content
Developers
Get an API token

Authentication

Every Novi credential type side by side, where each is used, how long it lasts and how to rotate it.

View MarkdownOpen in Claude(opens in a new tab)

Each product takes its own credential today.

Used for
Novi UDM Data reader account: Snowflake web interface, drivers, BI tools
How you send it
Snowflake sign-in
Lifetime
A temporary password you change at first sign-in
Rotate or revoke
Not published yet
Your own Snowflake users
Used for
Novi UDM Data shared into your Snowflake account
How you send it
Your Snowflake sign-in
Lifetime
Your account’s policy
Rotate or revoke
Your Snowflake administrator
Used for
Novi UDM Data over HTTPS
How you send it
Authorization: Bearer header
Lifetime
Reader-account starter token: 14 days by default. Replace it with a 365-day token
Rotate or revoke
Remove and add the token with ALTER USER
Key pair Preview
Used for
Novi UDM Data BI or lakehouse connection
How you send it
Private key file in your tool
Lifetime
While your subscription is active. The download link lasts 72 hours
Rotate or revoke
Not published yet
Used for
Novi Forecasts API and its MCP server, M&A Intelligence MCP server
How you send it
Authorization: Bearer header
Lifetime
1 to 365 days. The Forecasts app offers 7, 30 or 90 days, 1 year, or custom; 90 days is the default
Rotate or revoke
Revoke on the API tokens page; it stops working within two minutes. Create a new one to rotate
Used for
MCP servers for Forecasts, EVA and M&A Intelligence
How you send it
Your assistant signs you in
Lifetime
30 days
Rotate or revoke
Sign in again. Removing Access MCP cuts access within about two minutes
Used for
Novi EVA REST API
How you send it
x-api-key header
Lifetime
Not published yet
Rotate or revoke
Not published yet

Keep every credential in an environment variable or a secret manager. Never put one in code, a URL or a shared notebook. See Security.

In a reader account, each person gets a login by welcome email and signs in with role DATA_READER. For SQL over HTTPS, send a programmatic access token as a bearer token to your account URL followed by /api/v2/statements.

Novi UDM Data over HTTPS
curl -X POST "$NOVI_SNOWFLAKE_URL/api/v2/statements" \
-H "Authorization: Bearer $NOVI_SNOWFLAKE_TOKEN" \
-H "Content-Type: application/json" \
-d '{"statement": "SELECT COUNT(*) FROM NOVI_WELLS.WELL", "warehouse": "NOVI_WH", "database": "NOVI_DATA_ACCESS"}'

The reader-account starter token lasts 14 days by default: replace it with a one-year token. On your own Snowflake account, the setup script’s optional step issues the token.

A Novi API token acts as one person, with that person’s access.

The Create a token form: a name, and expiry choices of 7, 30 or 90 days, 1 year or custom, with 90 days selected.The Create a token form: a name, and expiry choices of 7, 30 or 90 days, 1 year or custom, with 90 days selected.
Create a token in the Forecasts app under Settings, then API tokens.
Novi Forecasts API
curl -sS --fail-with-body \
-H "Authorization: Bearer $NOVI_API_TOKEN" \
"$NOVI_API_BASE/me"
Novi API token lifecycleStep 1, in the Forecasts app under Settings, then API tokens: create a token and pick a lifetime of 7, 30 or 90 days, 1 year, or custom from 1 to 365 days. 90 days is the default. Step 2: copy it when you create it. Novi shows it only once. Tokens start with novi_pat_. Step 3, in your script: send it in the Authorization header as a bearer token. Each call acts as you, with your access. To rotate, create a new one. To revoke, use the API tokens page: anything using the token stops working within two minutes.123In the Forecasts appCreate a tokenSettings, then API tokens.Lifetime7 days30 daysDefault90 days1 yearCustom, 1 to 365 daysIn the Forecasts appCopy it onceNovi shows it only once.Copy it when you create it.novi_pat_…In your scriptSend it as a bearer tokenAuthorization:Bearer <token>Each call acts as you, withyour access.To rotate, create a new oneRevokeOn the API tokens page.Anything using it stopsworking within two minutes.Novi API token lifecycleStep 1, in the Forecasts app under Settings, then API tokens: create a token and pick a lifetime of 7, 30 or 90 days, 1 year, or custom from 1 to 365 days. 90 days is the default. Step 2: copy it when you create it. Novi shows it only once. Tokens start with novi_pat_. Step 3, in your script: send it in the Authorization header as a bearer token. Each call acts as you, with your access. To rotate, create a new one. To revoke, use the API tokens page: anything using the token stops working within two minutes.In the Forecasts appCreate a tokenSettings, then API tokens.Lifetime7 days30 daysDefault90 days1 yearCustom, 1 to 365 daysIn the Forecasts appCopy it onceNovi shows it only once. Copy itwhen you create it.novi_pat_…In your scriptSend it as a bearer tokenAuthorization:Bearer <token>Each call acts as you, with youraccess.123RevokeOn the APItokens page.Anything using itstops workingwithin twominutes.RotateCreate a newone.
  • Create it in the Forecasts app under Settings, then API tokens. You need the Access MCP permission to see that page.
  • Copy it when you create it. Novi shows it only once.
  • Format: tokens start with novi_pat_, which helps secret scanners find one committed by mistake.
  • Revoke it on the same page. Anything using it stops working within two minutes.
  • Issued for you: an administrator with user-management rights can also issue a token for a user. It acts as that user.
  • Limits: no token can create or manage tokens. Novi API tokens don’t work on the EVA MCP server or the EVA REST API.

Read-only service tokens not tied to a person are Planned.

Preview

Your assistant signs you in with your Novi login; you paste no token.

  1. Add the server URL to your assistant.
  2. Your browser opens Novi sign-in. Sign in as usual.
  3. Novi’s consent page shows the client, the product, your company, your email and how long the sign-in lasts. Approve it.
  4. The assistant can now use that product at your company, through its MCP server only. The sign-in does not work on Novi’s REST APIs or other products.

You need Access MCP and the product’s own permission. Supported clients: Claude (claude.ai and Claude Desktop), Claude Code and OpenAI Codex. Sign-in uses OAuth 2.1 with PKCE. Setup: Connect an assistant.

Create it on EVA’s Organization Settings page and send it in the x-api-key header. It acts for your EVA organization.

Novi EVA REST API
curl -s "$NOVI_EVA_API_BASE/v1/data/fields?group=Header" \
-H "x-api-key: $NOVI_EVA_API_KEY"

NOVI_EVA_API_BASE is the base URL on the EVA REST API page.