Included in ODBC PowerPack

ODBC API Driver (Pre-Configured Connectors)

Universal API driver with 50+ pre-configured SaaS connectors and enhanced query builder.

Read and write data from popular online services with plain SQL, without learning their REST APIs. Pick a pre-configured connector, build queries with the query builder, get nested data as a flat table, or use your own connector file.

Included in the Enterprise edition and above

ZappySys ODBC Driver - Create API Driver
Driver UI, SQL query and live preview

Trusted by data teams worldwide

MicrosoftIBMOracleDell TechnologiesHPCiscoAT&TVerizonDHLFedExUPSWalmart

Also rated on Capterra★★★★★ , Trustpilot★★★★★ and BBBA+ — see why teams trust ZappySys

At a glance

What the API Driver (Pre-Configured Connectors) can do

Universal API driver with 50+ pre-configured SaaS connectors and enhanced query builder.

Pre-configured connectors

Pick a connector and query its tables. The Enterprise API Driver includes 50+ pre-configured SaaS connectors and an enhanced query builder.

  • Connector wizard with online search
  • Query builder
  • Custom connectors

Browse all connectors

Connection clause

Name the connector and its settings inside the query, or supply the configuration text directly.

  • Provider and service URL in SQL
  • Direct ConfigText
  • Parameters in WITH clause

See the SQL example

Bulk write

Insert, update, upsert and delete in bulk with a SOURCE clause that reads from SQL Server or another ODBC source.

  • SOURCE clause
  • INSERT / UPDATE / DELETE
  • SQL Server or ODBC source

See the SQL example

Familiar SQL

Use WHERE, ORDER BY, GROUP BY and built-in math, string, date and JSON functions on top of the data source.

  • Standard SELECT syntax
  • Custom functions in the SQL dialect
  • Driver options in a WITH clause

Query examples

Works with the tools you have

Any ODBC-compliant tool can use the DSN: Power BI, Tableau, Qlik, SSRS, Informatica, Excel and SSIS.

  • Create a DSN once, reuse it everywhere
  • 32-bit and 64-bit ODBC
  • Stored in the standard ODBC Data Source Administrator

Setup guide

Use it from code

Connect from Java, C#, Python, PowerShell and more with an ODBC connection string that names the DSN.

  • Standard ODBC connection strings
  • Parameterized queries
  • Same SQL as in the UI

Python example

SQL Server via Data Gateway

Query the driver from SQL Server (linked server / OPENQUERY) without installing it on the SQL Server machine, through the Data Gateway.

  • No driver install on the server
  • Works with SQL Server 2012 through 2025 (32/64 bit)
  • Same DSN, same SQL

About Data Gateway

See all features
  • In few clicks read /write data from popular online services using familiar SQL Query language (e.g. Google BigQuery, Sheets, SharePoint, JIRA, Zendesk and more…)
  • No need to learn Complex API Configurations / Pagination / Authentication details about REST API
  • Intuitive UI for easy step by step configuration without having API knowledge
  • Easily modify existing connector file based on your need.
  • Allows to create and use your own reusable connector file for custom API (or you can consider using our generic JSON Driver or XML Driver)
  • Integrate insight many ODBC Compliant Apps for Reporting / ETL / Database (e.g. Power BI, Informatica, MS Access, Excel, SSRS and more…)
  • Support for programming languages (e.g. JAVA, C#, Python, PowerShell and more…)
  • Tight integration with Microsoft SQL Server (With support for Gateway Option – No need to install Driver on Server)
  • Familiar SQL Query language support including WHERE, ORDER BY, GROUP BY constructs
  • Support for custom math/ string / datetime / JSON /XML functions in SQL query Language
  • The unparalleled performance with large file support
  • Latest security standards such as OData, OAuth and JWT (RFC 7519) (Call services like Google API, Facebook …)
  • REST API Pagination Support to consume multiple requests / loop
  • HTTPS / SSL / TLS 1.2 Support for more secure communication
  • Support for Proxy Server
Runs in your environment ·

SQL Server 2012–2025

through the Data Gateway · Read the FAQ

Ways to use it

Pick how you reach your data.

Configure the DSN once, then query it from any ODBC tool or from SQL Server.

Pick a pre-configured connector.

Search the online catalog or choose an embedded connector, then authenticate.

  • Embedded connectors
  • Search online
  • Query builder
ZappySys ODBC Driver - Create API Driver

Inside the UI

The driver UI, step by step.

Real screens from the ZappySys ODBC driver configuration.

Create the DSN

Add a user or system DSN and pick the API Driver (Pre-Configured Connectors).

SQL example

Pick a connector. Query it with SQL.

The API Driver ships with pre-configured connectors (Enterprise Edition). The Connection clause below picks the OData connector and queries its Customers table.

  1. Pre-configured connector

    Choose a connector in the driver wizard, or name it in the Connection clause of a query.

    Connection clause

    Provider   = 'OData'
    ServiceUrl = 'https://services.odata.org/V3/Northwind/Northwind.svc'
  2. Run the SQL query

    SQL QuerySELECT * FROM Customers CONNECTION (Provider = 'OData', ServiceUrl = 'https://services.odata.org/V3/Northwind/Northwind.svc')

    Each connector exposes tables and endpoints you query like database tables.

    Insert / Update / Upsert / Delete are supported where the API allows writes.

  3. Rows returned to your tool

    Result shape
    Table Rows
    Customers one row per API record

    Browse the full catalog of connectors in the API Integration Hub.

Statement taken from the driver’s query examples.

SQL query examples

Copy a query, change the source, run it.

21 of the 24 examples from the API Driver (Pre-Configured Connectors) help. Open one to see the SQL.

Read files, API responses and objects as rows.

Download Blob Data as Byte Array

This example shows how to download binary data (blob) as a Byte array. Use SaveContentAsBinary=1 to treat response as binary, and Meta=’data:Blob’ to return the data column as Byte[] (DT_IMAGE).

SELECT * FROM generic_request
WITH (
    URL='/small.png'
  --OR use full URL
  --URL='https://zappysys.com/downloads/files/test/small.png'
  , RequestMethod='GET'
  , SaveContentAsBinary=1
  , Meta='data:Blob'
)
-- Alternative options for Meta:
-- , Meta='data:DT_IMAGE' -- Direct SSIS type (DT_IMAGE for binary data)
-- , Meta='data:Byte(10000)' -- Binary data with length (becomes DT_BYTES if <= 8000, DT_IMAGE if > 8000)
-- Note: If you remove Meta='data:Blob', the data column will return as base64 string instead of Byte[] array

Open this example in the help

Download File to Disk

This example shows how to download a file directly to disk. Use SaveContentAsBinary=1 to treat response as binary, and ResponseDataFile to specify the target file path.

SELECT * FROM generic_request
WITH (
    URL='/small.png'
  --OR use full URL
  --URL='https://zappysys.com/downloads/files/test/small.png'
  , RequestMethod='GET'
  , SaveContentAsBinary=1
  , ResponseDataFile='c:\temp\small.png'
  , RawOutputDataRowTemplate='{Status:"Downloaded"}'
  , EnableRawOutputModeSingleRow=1
  , FileOverwriteMode='AlwaysOverwrite'
)
-- FileOverwriteMode options:
-- 'AlwaysOverwrite' or 0 - Always overwrite existing file
-- 'FailIfExists' or 1 - Fail if file already exists
-- 'SkipIfExists' or 2 - Skip download if file already exists

Open this example in the help

Custom Metadata / Override Mode
SELECT id,name,checknumber FROM MyTable
WITH
(
--//Custom Metadata (Direct Mode)<<<
--//Add all possible columns here and it will be part of metadata (this approach ignores any metadata comes from table itself). This approach usually helpful when Table has dynamic data (scan 300 rows to detect types) which may cause issue if zero records found.
META = 'id:int;checknumber:string(10);name:string(10);some_extra_column:datetime'

--//Custom Metadata with Override  (Direct Mode)<<<
--You can use @OverrideMode:1 in the column list to override meta for specific column(s) only and use all other columns from reported metadata for table - In below example we are changing default datatype/length for id and checknumber, all other columns are dynamic so dont have to supply in META clause
--META = '@OverrideMode:1;id:int;checknumber:string(10)'

--//Metadata from File (supply metadata stored in file)
--META = 'c:\mytable_meta.txt'
)

Open this example in the help

Basic SQL queries

Basic query examples.

--Whenever Possible try to write Simple Query. When you use WHERE / GROUP BY / ORDER BY Expressions. Driver may invoke Client side processing if server side doesnt support that construct.
--For comment use line comment with two dash (e.g. --my comment) or use block comment for multi line comment (e.g. /*my comment*/ )
--Any query must contain at least two required parts
--data source (or table) names and a list of column names
--column names come first (preceded by SELECT keyword)
--table names follow (preceded by FROM keyword)

--Here is the query that returns all rows with all columns (* stands for all columns) from 'Accounts' table
SELECT * FROM Accounts

--Use quoted identifiers when you have space or other character in names (e.g. Column or Table name contains space)
SELECT ID, "Account Name" FROM "Closed Accounts"
SELECT ID, [Account Name] FROM [Closed Accounts]

--returns all rows from 'Accounts' table, each row will have Id and Amount columns
SELECT Id, Amount FROM Accounts

--returns only those rows of 'Accounts' table that meet next condition: Amount is greater or equal to 1000.0
SELECT Id, Amount FROM Accounts WHERE Amount >= 1000.0

--returns only those rows of 'Accounts' table that meet next condition: Amount is greater than 1000 or DepartamentID is equal to 123
SELECT Id, Amount FROM Accounts WHERE (Amount > 1000.0 OR DepartamentID = 123)

--returns only those rows of 'Accounts' table that meet next condition: DepartamentID is equal to 1, 101 or 202
SELECT Id, Amount FROM Accounts WHERE DepartamentID IN (1, 101, 202)

--returns only those rows of 'Accounts' table that meet next condition: DepartamentID is equal to 321 and Amount is less than 100
SELECT Id, Amount FROM Accounts WHERE DepartamentID = 321 AND Amount < 100

--returns only those rows of 'Persons' table that meet next condition: Name column value starts with 'John'
SELECT * FROM Person WHERE Name LIKE 'John%'

--case statement
SELECT
 FirstName,
 LastName,
 CASE Country
  WHEN 'US' THEN 'NA'
  WHEN 'Canada' THEN 'NA'
  WHEN 'India' THEN 'Asia'
  WHEN 'China' THEN 'Asia'
  ELSE 'Unknown'
 END ColRegion
 FROM Person

Open this example in the help

See all 24 SQL examples in the help

Articles

Guides and tutorials for the API Driver (Pre-Configured Connectors)

GuideRead data from QuickBooks Online into SQL Server via JSON DriverQuickBooks Online is a well-known Cloud-based Accounting Software. In this post, you will learn how to implement QuickBooks Online API Integration with SQL Server or…zappysys.com blogRead articleGuideRead / Write REST API data in Talend (JSON / XML / SOAP)In this post we will learn how to read / write REST API data in Talend Open Studio. We will create a simple Talend Job using ZappySys JSON Driver to read from REST…zappysys.com blogRead articleGuideInsert, Update and Delete JIRA Issue in SQL ServerIn our previous blog we saw how to read JIRA data in SQL Server. In this blog, we will learn how to Insert, Update and Delete Issue in JIRA using ZappySys JSON Driver.…zappysys.com blogRead articleGuideRead JIRA data in SSRS Reports (SQL Server Reporting Services)In our previous blog we saw how to read rest api in SSRS reports. We recommend you go through that article first. In this post we will look at specific example on How…zappysys.com blogRead articleGuideHow to Import JIRA data in Power BI using JSON DriverIn our previous blog we saw how to import rest api in Power BI. We recommend you go through that article first. In this article, we will learn how to Import JIRA data…zappysys.com blogRead articleGuideGet Office 365 data in Power BI using Microsoft Graph API and ODBCIn this article, we will get Office 365 data in Power BI using Microsoft Graph API and ODBC drivers. Specifically, we will get Excel file data in OneDrive, events from…zappysys.com blogRead articleCollectionAll API Driver (Pre-Configured Connectors) articlesMore tutorials and how-to articles on the ZappySys blog.zappysys.com blogBrowse all articles

Compatibility and requirements

Built for Windows, and for your own environment.

  • Windows 11, 10, 8 and 7, and Windows Server 2022, 2019, 2016, 2012 R2 and 2008
  • .NET Framework 4.x. The JDBC Bridge Driver also needs Java 8 or later
  • 32-bit and 64-bit ODBC drivers. SQL Server 2012 through 2025 through the Data Gateway
  • Self-hosted: drivers run in your Windows process, business data does not pass through ZappySys servers, and credentials stay in your DSN
  • Free trial of ODBC PowerPack: test with your own data before you buy

FAQ

Questions about the API Driver (Pre-Configured Connectors)

Which tools and languages can use this driver?

Any ODBC-compliant tool, such as Power BI, Tableau, Qlik, SSRS, Informatica, Excel and SSIS. You can also connect from Java, C#, Python, PowerShell and other languages with an ODBC connection string.

Do I need to install the driver on SQL Server?

No. With the Data Gateway option the driver runs on the gateway machine and SQL Server connects to it through a linked server.

Which edition includes the API Driver (Pre-Configured Connectors)?

The API Driver (Pre-Configured Connectors) is included in the Enterprise edition of ODBC PowerPack. See the edition comparison for the full list.

Which connectors are included?

The Enterprise API Driver includes 50+ pre-configured connectors. Browse them in the API Integration Hub.

How do I choose or add a connector?

Pick one from the embedded list, search the online catalog, load a connector file (Enterprise), or paste the connector configuration text. Then use the query builder to generate the SQL.

Is there an SSIS version?

Yes. This driver uses the same data engine as the JSON Source in SSIS PowerPack.

Which SQL Server and Windows versions are supported?

Support for SQL Server 2025, 2022, 2019, 2017, 2016, 2014 and 2012 (32/64 bit) through the Data Gateway. See the system requirements.

Can I try it before buying?

Yes. Download ODBC PowerPack, create a DSN and test your own data before you buy.

Independent ratings

Trusted by data teams, recognized by the industry

See why teams trust ZappySys (opens in new tab)

What customers say

  • Customer story

    ZappySys has been a fantastic way to bring our small company into the world of APIs, automation, and systems integration by providing tools within an easy-to-use framework.

    Ben KingeryOxspring Paul
  • Customer story

    At Synchronous Customers, we need to connect various types of data quickly. The super handy ZappySys connectors and great documentation let us do it without writing a lot of code.

    Joel ConnerSynchronous Customers
  • Customer story

    We have worked with the ZappySys support team for over a year and have consistently found them extremely helpful — resourceful and creative in offering multiple solutions to our challenges.

    Senthil SekarPublicis Groupe
  • Trustpilot

    I’ve been using ZappySys for over 6 years — it makes development faster, and I introduced it to my current company.

    Anna JohnsonTrustpilot review
  • Customer quote

    I submitted a support request and had someone logged in and fixing things within 2 hours.

    Barry Wilson
  • Customer quote

    The REST source is very powerful — the only thing I found I could use after trying components from major vendors.

    Jes KirkupKTC
  • Customer quote

    Whenever we run into an obstacle, ZappySys has a solution for us. We are so glad that we chose ZappySys PowerPack.

    Kevin ChenBerricle

Start your free trial today

Install ODBC PowerPack and add a API Driver (Pre-Configured Connectors) DSN.

Preview your data in the driver UI before you connect your tool.

  • One DSN, many toolsPower BI, Excel, SSIS, Python and SQL Server can all use it.
  • Free trialTest the driver with your own data before you buy.
  • Live supportHelp during your trial and after purchase.

New purchases may be eligible for refund review within 30 days. See the refund policy.

Talk to an engineer before or during your trial.

1 / 9