Observe by Snowflake tokens

Learn about the different types of tokens in Observe by Snowflake and how to use each type of token.

Observe by Snowflake token types

Observe by Snowflake has the following primary types of tokens that are used to authenticate users and systems.

Token typeDescriptions
User session tokensUser session tokens are automatically created each time a user logs in to the Observe by Snowflake platform.
  • Login session tokens are generated when you log in to Observe by Snowflake using a user name and password.

  • SSO session tokens are generated when you log in to Observe by Snowflake via a SAML IDP.

User session tokens are bound to a specific user. The default session timeout is 31 days. If you use Observe by Snowflake within 9 days of expiration, the session timeout is extended by 10 days. The UI only warns you about 2 minutes before the token actually expires.

Contact your Observe by Snowflake representative to change the default session timeout and session renewal values.
API tokensAPI tokens are created by the user in the Observe by Snowflake platform, as described in Observe by Snowflake API authentication. API tokens are used to interact with Observe by Snowflake's REST APIs and are bound to a specific user or service account, depending on how the token was created.
Ingest tokensIngest tokens authenticate telemetry sent to Observe by Snowflake's collection endpoints. Create them in Data & integrations > Ingest tokens or during an Add Data setup flow. Standalone tokens do not select a destination; routing selects the source dataset. Existing associated tokens can retain destination bindings. See Ingest Tokens for creation, scope, rotation, and API management, and Ingest Routing for destination selection.
📘

Note

API tokens cannot be used to ingest data via the Observe by Snowflake ingestion pipeline. If you are attempting to ingest data, you must obtain a data ingest token.