All APIsClose

Other connection options

Introduction

There are several ways to connect to the data platform. Snowflake supports application development using many programming languages and development platforms. With native clients (connectors, drivers) from Snowflake, you can develop applications with any of the following capabilities:

  • GO
  • JDBC
  • .NET
  • js
  • PHP
  • Python
  • SQLAlchemy
  • It is also possible to make a direct connection to a proprietary Snowflake data warehouse.

Snowpark
The Snowpark library provides REST APIs for querying data from Snowflake. Snowflake's REST API provides a secure, flexible and scalable way to process large amounts of data from Snowflake and supports various queries, filters and commands, giving users flexible ways to access data.

SnowSQL
SnowSQL is a CLI (Command Line Interface) tool that allows users to use Snowflake through, for example, a command promp. It supports commands for running SQL queries, managing database objects and configuring Snowflake accounts.

Direct connection to your own Snowflake data warehouse
To establish a direct connection between two Snowflake data warehouses, we use the Cross-Account Data Sharing feature. This allows ANVA to safely and securely share data with your own Snowflake data warehouse.

Features

SnowSQL

  • SSL/TLS encryption, authentication and authorization
  • Compatible with various operating systems, including Windows, Linux and macOS.
  • Designed to scale with user needs and can be used to handle large amounts of data.
  • Supports various configuration options and can be customized to meet users' needs.
  • Ability to integrate with various applications and tools, including BI tools.

RESTAPI

  • Uses HTTP methods such as GET, POST, PUT and DELETE to manage data.
  • Supports JSON format, which makes it easy to retrieve and process data. It also provides support for other file formats such as CSV and Avro.
  • Supports pagination, allowing users to retrieve large amounts of data in smaller parts. This helps reduce server load and improves performance.
  • Asynchronous processing: Snowflake's REST API supports asynchronous processing, meaning users can submit multiple requests and their processing can be monitored via status checks.
  • Supports caching to improve performance by reducing the number of requests sent to the server.
  • Comprehensive monitoring and logging features, including query execution statistics and error messages, to help users diagnose and resolve problems.

Direct connection to own Snowflake data warehouse
It is possible to connect directly between Snowflake data warehouses residing on different cloud platforms, including Amazon Web Services (AWS) and Microsoft Azure or Google Cloud.

Specifications

SnowSQL
SnowSQL is a command line client provided by Snowflake. SnowSQL is used to manage and communicate data stored in Snowflake via SQL commands. It allows users to run queries and manage database objects such as tables.

Snowpark
The Snowpark library provides REST APIs for querying data from Snowflake.

ANVA provides credentials to unlock data from Snowflake. With that, you as a user can use the Snowflake REST API to retrieve and download data from Snowflake. To use the API, you must first create an API user account and get credentials from ANVA to the objects you want to unlock. Then you can use REST API calls to retrieve and download the data in the desired format.

To retrieve data using the Snowflake REST API, perform the following steps:

  • Set the appropriate authorization information to access the Snowflake account.
  • Use the REST API calls to retrieve the data. You can use different queries and filters to narrow down the results to the data you need.
  • Download the data in the desired format. Snowflake supports various file formats, such as CSV, JSON and Excel.
  • Process the data in the desired tool or application.

Designed to be secure and scalable, the Snowflake REST API can be used for various use cases, such as automating data integration processes, creating custom reports and dashboards, and integrating Snowflake data with other tools and applications. Snowpark does not require a separate cluster outside Snowflake for calculations. All calculations are done within Snowflake.

Direct connection Snowflake data warehouse
To set up Cross-Account Data Sharing, ANVA will enable file/data sharing from your organization in the data platform. We will then set up the data with your account and permissions to grant access to the shared data. You can then use the shared data as if it were part of your own account (view).

To establish a direct connection between the two accounts, we must jointly set up the appropriate credentials and permissions in both accounts. Once this is completed, the accounts can communicate directly with each other without the need for additional resources or tools.

Supported versions of client drivers for Snowflake

As of August 1, 2025, client driver versions lower than listed below will no longer be supported based on the Snowflake support policy.

Update all drivers to the latest versions to take advantage of important fixes and improvements in security, performance and other features. Snowflake cannot help you with problems related to versions that are no longer supported.

Technical Documentation

Learn more about the various connection options with Snowflake:

https://docs.snowflake.com/api-reference

SnowSQL
Snowflake provides extensive documentation and support for SnowSQL, including sample code and tutorials, to help users implement SnowSQL in their workflows and processes. Use the Snowflake Client Repository to download SnowSQL, the ODBC driver, the Snowpark library or SnowCD over HTTP (for example, using curl).

Learn more about SnowSQL: https://developers.snowflake.com/snowsql/

Snowpark
Learn more about Snowpark APIs: https://docs.snowflake.com/en/developer-guide/snowpark/index

Direct connection Snowflake Datawarehouses
Learn more about data sharing: https://docs.snowflake.com/en/user-guide/data-sharing-intro

Access data platform
For access, ANVA provides a private key file with a strong password, these must be set up during configuration.

The private key file should preferably be stored in a location where as few people as possible have access.