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 type | Descriptions |
|---|---|
| User session tokens | User session tokens are automatically created each time a user logs in to the Observe by Snowflake platform.
Contact your Observe by Snowflake representative to change the default session timeout and session renewal values. |
| API tokens | API 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 tokens | Ingest 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. |