Bluebeam Studio is a cloud collaboration platform that construction and design teams use to run drawing reviews, markups, and document handoffs through Bluebeam Revu. Many organizations need Bluebeam Studio data in Power BI to monitor Session activity, Project status, and review turnaround.

Using the ZappySys ODBC Driver for REST APIs, you can query Bluebeam Studio API data with SQL and load it into Power BI without writing custom connector code. This tutorial shows how to create a Bluebeam ODBC DSN, configure OAuth2 authentication, preview data, connect Power BI, and run practical SQL queries.

Steps

Get Bluebeam API credentials

1. Sign in to the Bluebeam Developer Portal with your BBID credentials. Note that a Studio Prime subscription is required to use an integration built on the Studio API.
2. Register a new App and note the region it is registered under (US, DE, AU, UK, or SE), since this determines the base URL you will use later.
   

   Bluebeam – Create an Application

3. Open the App details page and generate your Client ID and Client Secret — store both values securely.
   

   Bluebeam – Generate client ID and secret

Create a new ODBC DSN using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open ODBC Data Source Administrator.
   
2. In User DSN or System DSN, click Add.
3. Select ZappySys JSON Driver, then click Continue.
   

Configure Bluebeam API connection

1. Enter a Bluebeam Studio endpoint URL using your region’s base URL, in this format:
   https://api.bluebeam.com/publicapi/v1/sessions
2. In Connection Type, select OAUTH and click Configure.
3. Set Credential Type to OAuth2 Authorization Code Grant (Custom).
4. Enter your Client ID and Client Secret.
5. Set the Authorization URL to

   https://api.bluebeam.com/oauth2/authorize

   and the Access Token URL to

   https://api.bluebeam.com/oauth2/token

   using your region’s host.
6. Set Scope to:
   

   full_user 
   jobs 
   offline_access

7. Click Generate Token to complete the one-time browser login with your BBID.
8. Click OK to save OAuth authentication settings.
9. Set HTTP Request Method to GET.
10. Open the HTTP Headers tab and add:
    • Content-Type: application/json
    • client_id: your Bluebeam Client ID

    The client_id header is required on Studio endpoints alongside the Bearer token; the OAuth connection only supplies the Bearer token automatically.

11. Set the JSON Path Filter based on the response shape; example:

    $.Sessions[*]

12. Click Test Connection, then click OK to save the DSN.
    

    Bluebeam – ODBC JSON Driver configuration

Preview Bluebeam data in ODBC Driver

1. Open the Preview tab in the DSN configuration window.
2. Generate a query and click Preview Data.
3. Confirm rows are returned. If not, recheck the region base URL, credentials, scope, and JSON Path Filter.
   

   Bluebeam – ODBC JSON Driver result

Connect Power BI to Bluebeam via ODBC

1. Open Power BI Desktop.
2. Go to Home > Get Data > More….
3. Search for ODBC and click Connect.
   

   Power BI – Get data from ODBC connection

4. Select your Bluebeam DSN from the data source list.
5. Optionally enter a custom SQL query in Advanced options.
   

   Bluebeam – Power BI query example

6. Click OK, review the preview, and click Load
   
   

   Bluebeam – Power BI query result

Query Bluebeam Data with SQL

Use custom SQL queries in the ODBC driver or Power BI to shape data before loading.

Example 1: List Studio Sessions

SELECT
    Id,
    Name,
    Restricted,
    Notification,
    CreatedBy,
    SessionEndDate
FROM _root_

Example 2: Filter Active Sessions

SELECT
    Id,
    Name,
    CreatedDate,
    SessionEndDate
FROM _root_
WHERE SessionEndDate IS NULL
ORDER BY SessionEndDate ASC

Example 3: Sessions Summary by Creator

SELECT
    CreatedDate,
    COUNT(*) AS SessionCount
FROM _root_
GROUP BY CreatedDate
ORDER BY SessionCount DESC

Conclusion

Connecting Bluebeam Studio to Power BI using the ZappySys ODBC Driver gives you a fast, SQL-friendly way to build reporting on Sessions, Projects, and Jobs data. You can centralize collaboration activity, model it in Power BI, and publish dashboards without building a custom OAuth integration, since the offline_access scope keeps the driver authenticated between refreshes.

Explore the full capabilities of the ZappySys ODBC Drivers to integrate Bluebeam Studio and other APIs into your reporting workflow.

The post How to get data from Bluebeam into Power BI appeared first on ZappySys Blog.

Bluebeam Studio is a cloud collaboration platform that construction and design teams use to run drawing reviews, markups, and document handoffs through Bluebeam Revu. Many organizations need Studio Sessions, Projects, and Jobs data in SQL Server for reporting, audit trails, and project tracking.

In this tutorial, you will learn how to connect to the Bluebeam Studio API using SQL Server Integration Services (SSIS) with the ZappySys SSIS PowerPack. This approach helps you build repeatable ETL pipelines without writing custom OAuth or API integration code.

Steps

Get Bluebeam API credentials

1. Sign in to the Bluebeam Developer Portal with your BBID credentials.
2. Register a new App and note the region it is registered under (US, DE, AU, UK, or SE), since this determines the base URL you will use later.
   

   Bluebeam – Create an Application

3. Open the App details page and generate your Client ID and Client Secret — store both values securely. You will need the Client ID again later for a required request header.
   

   Bluebeam – Generate client ID and secret

Create an HTTP connection in SSIS

1. Create or open your SSIS project and package.
2. In Connection Managers, right-click and select New Connection….
3. Select ZS-OAUTH from the SSIS connectors list.
   

   Create a new SSIS OAuth API Connection Manager

4. Set OAuth version to OAuth2
5. Set OAuth Grant type to Authorization Code Grant.
6. Enter your Client ID and Client Secret from the previous step.
7. Set the Authorization URL to

   https://api.bluebeam.com/oauth2/authorize

   and the Access Token URL to

   https://api.bluebeam.com/oauth2/token

   using your region’s host.
8. Set Scope to:
   

   full_user 
   jobs 
   offline_access

9. Click Generate Token and click OK to save the connection.
   

   Bluebeam – OAuth connection

Create and configure JSON Source

1. Drag a Data Flow Task into Control Flow and open it.
2. In Data Flow, drag and drop the ZS JSON Source.
3. Open the JSON Source editor and enable Use credentials.
4. Select the Bluebeam HTTP connection you created earlier.
5. Set the API URL using your region’s base URL. Example to list Studio Sessions:
   

   https://api.bluebeam.com/publicapi/v1/sessions

6. Set the HTTP Request Method to GET.
7. Add the following HTTP Headers:
   • Content-Type: application/json
   • client_id: your Bluebeam Client ID

   Bluebeam rejects the request with only the Bearer token from the OAuth connection; the client_id header must be added manually here, since it identifies the App making the call.

8. Set the JSON Path Filter based on the response shape; example:

   $.Sessions[*]

9. Click Preview to confirm rows are returned, then click OK to save the configuration.
   

   Bluebeam – the JSON Source configuration

Configure Destination component

1. Add an Upsert Destination (or another destination of your choice, such as a Trash destination or JSON/CSV/XML destination).
2. Connect the output arrow from JSON Source to the destination component.
3. Configure your SQL Server connection and target table.
4. Select the options you want to use: Insert and/or Update.
5. Map the source columns to destination columns in the Mappings section.
   

   Bluebeam – Upsert destination

6. Click OK and execute the package.
7. Validate that Bluebeam Studio rows have been loaded into your SQL Server table.
   

   Bluebeam – Upsert Destination example

Conclusion

You now have a working SSIS integration to extract Bluebeam Studio data using ZappySys SSIS PowerPack and the Bluebeam Studio API. With this pattern, you can automate extraction of Sessions, Projects, and Jobs data into SQL Server for reporting and project tracking, since the OAuth2 refresh token keeps the connection authenticated without repeated manual logins.

Explore the full capabilities of the ZappySys SSIS PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include transformations, data validation, error handling, and scheduling through SQL Server Agent.

The post SSIS Tutorial: How to get data from Bluebeam appeared first on ZappySys Blog.

ShipStation is a leading shipping and order management platform used by eCommerce businesses to manage orders, shipments, and fulfillment across multiple sales channels. Many organizations need ShipStation data in Power BI to monitor fulfillment performance, shipping costs, and order trends.

Using the ZappySys ODBC Driver for REST APIs, you can query ShipStation API data with SQL and load it into Power BI without writing custom connector code. This tutorial shows how to create a ShipStation ODBC DSN, configure API authentication, preview data, connect Power BI, and run practical SQL queries.

Steps

Get ShipStation API credentials

1. Sign in to your ShipStation account.
2. Go to Account Settings → API Settings.
   

   ShipStation – Settings

3. Generate your API Key and API Secret — store both values securely.
   

   ShipStation – Generate token

Create a new ODBC DSN using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open ODBC Data Source Administrator.
   
2. In User DSN or System DSN, click Add.
3. Select ZappySys JSON Driver, then click Continue.
   

Configure ShipStation API connection

1. Enter a ShipStation endpoint URL in this format:
   https://ssapi.shipstation.com/orders
2. In Connection Type, select HTTP and click Configure.
3. Set Credential Type to Basic Auth (Username/Password).
4. Set Username to your ShipStation API Key.
5. Set Password to your ShipStation API Secret.
6. Click OK to save HTTP authentication settings.
   

   ShipStation – ODBC HTTP connection

7. Set HTTP Request Method to GET.
8. Add the following HTTP Header:
   • Accept: application/json
9. Set JSON Path Filter based on the endpoint. Each ShipStation endpoint wraps its array under a named key:
   • Orders: $.orders[*]
   • Shipments: $.shipments[*]
   • Products: $.products[*]
   • Customers: $.customers[*]
10. Click Test Connection, then click OK to save the DSN.
    

    ShipStation – ODBC JSON driver configuration

Preview ShipStation data in ODBC Driver

1. Open the Preview tab in the DSN configuration window.
2. Generate a query and click Preview Data.
3. Confirm rows are returned. If not, recheck the endpoint URL, credentials, and JSON Path Filter.
   

   ShipStation – ODBC JSON driver result

Connect Power BI to ShipStation via ODBC

1. Open Power BI Desktop.
2. Go to Home > Get Data > More….
3. Search for ODBC and click Connect.
   

   Power BI – Get data from ODBC connection

4. Select your Spotify DSN from the data source list.
5. Optionally enter a custom SQL query in Advanced options.
   

   ShipStation – Power BI SQL example

6. Click OK, review the preview, and click Load
   
   

   ShipStation – Power BI result

Query ShipStation Data with SQL

Use custom SQL queries in the ODBC driver or Power BI to shape data before loading.

Example 1: List Orders

SELECT
    orderId,
    orderNumber,
    orderStatus,
    orderDate,
    orderTotal,
    amountPaid,
    shippingAmount,
    taxAmount,
    customerEmail,
    customerUsername,
    paymentMethod,
    carrierCode,
    serviceCode,
    [billTo.name]    AS billTo_name,
    [billTo.city]    AS billTo_city,
    [billTo.country] AS billTo_country,
    [shipTo.name]    AS shipTo_name,
    [shipTo.city]    AS shipTo_city,
    [shipTo.country] AS shipTo_country,
    [weight.value]   AS weight_value,
    [weight.units]   AS weight_units,
    createDate,
    modifyDate,
    shipByDate
FROM _root_

Example 2: Filter Awaiting Shipment Orders

SELECT
    orderId,
    orderNumber,
    orderStatus,
    orderTotal,
    customerEmail,
    shipByDate
FROM _root_
WHERE orderStatus = 'awaiting_shipment'
ORDER BY shipByDate ASC

Example 3: Orders Summary by Status

SELECT
    orderStatus,
    COUNT(*) AS OrderCount,
    SUM(orderTotal) AS TotalAmount,
    SUM(shippingAmount) AS TotalShipping
FROM _root_
GROUP BY orderStatus
ORDER BY OrderCount DESC

Conclusion

Connecting ShipStation to Power BI using the ZappySys ODBC Driver gives you a fast, SQL-friendly way to build fulfillment and logistics analytics from ShipStation API data. You can centralize order, shipment, and customer data, model it in Power BI, and publish dashboards without building custom connectors.

Explore the full capabilities of the ZappySys ODBC Drivers to integrate ShipStation and other APIs into your reporting workflow.

The post How to get data from ShipStation into Power BI appeared first on ZappySys Blog.

ShipStation is a leading shipping and order management platform used by eCommerce businesses to manage orders, shipments, and fulfillment across multiple sales channels. Many organizations need ShipStation data in SQL Server for reporting, logistics analytics, and fulfillment performance tracking.

In this tutorial, you will learn how to connect to the ShipStation REST API using SQL Server Integration Services (SSIS) with the ZappySys SSIS PowerPack. This approach helps you build repeatable ETL pipelines without writing custom API integration code.

Steps

Get ShipStation API Credentials

1. Sign in to your ShipStation account.
2. Go to Account Settings → API Settings.
   

   ShipStation – Settings

3. Generate your API Key and API Secret — store both values securely.
   

   ShipStation – Generate token

Create an HTTP Connection in SSIS

1. Create or open your SSIS project and package.
2. In Connection Managers, right-click and select New Connection….
3. Select ZS-HTTP from the SSIS connectors list.
   

   Create a new HTTP connection.

4. Set Credentials Type to Basic Auth.
5. Enter your API Key in the Username field and your API Secret in the Password field.
6. Click OK to save the connection.
   

   ShipStation – HTTP connection

Create and Configure JSON Source

1. Drag a Data Flow Task into Control Flow and open it.
   

   Drag and drop Data Flow

2. In Data Flow, drag and drop the ZS JSON Source.
   

   SSIS JSON Source – Drag and Drop

3. Open the JSON Source editor and enable Use credentials.
4. Select the ShipStation HTTP connection you created earlier.
5. Set the API URL. Example to extract orders:

   https://ssapi.shipstation.com/orders

6. Set the HTTP Request Method to GET.
7. Add the following HTTP Header:
   • Accept: application/json
8. Set JSON Path Filter based on the endpoint. Each ShipStation endpoint wraps its array under a named key — for example:
   • Orders: $.orders[*]
   • Shipments: $.shipments[*]
   • Products: $.products[*]
   • Customers: $.customers[*]
9. Click Preview to confirm rows are returned, then click OK.
   

   ShipStation – JSON Source configuration

Configure Destination Component

1. Add an Upsert Destination (or another destination of your choice, such as a Trash destination or JSON/CSV/XML destination).
2. Connect the output arrow from JSON Source to the destination component.
3. Configure your SQL Server connection and target table.
4. Select the options you want to use: Insert and/or Update.
5. Map the source columns to destination columns in the Mappings section.
   

   ShipStation – Upsert destination

6. Click OK and execute the package.
7. Validate that ShipStation rows have been loaded into your SQL Server table.
   

   ShipStation – Upsert Destination example

Conclusion

You now have a working SSIS integration to extract ShipStation data using ZappySys SSIS PowerPack and the ShipStation REST API. With this pattern, you can automate extraction of orders, shipments, products, and customer data into SQL Server for reporting and fulfillment analytics.

Explore the full capabilities of the ZappySys SSIS PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include transformations, data validation, error handling, and scheduling through SQL Server Agent.

The post SSIS Tutorial: How to get data from ShipStation appeared first on ZappySys Blog.

Hivebrite is a community management platform used for memberships, events, directories, and engagement workflows. Many organizations store operational data in Hivebrite and need to migrate it to Power BI for reporting, analytics, and business intelligence.

In this tutorial, you will learn how to read Hivebrite API data directly from Power BI by using the ZappySys JSON Driver (part of ODBC PowerPack). You will configure OAuth2 authentication, handle pagination, preview the data inside the driver, and then load it into a Power BI model — without writing a custom API client.

Steps

Prepare Hivebrite API access

1. Sign in to your Hivebrite admin area and go to Integrations → External Integrations.
2. Click Create a Service App and give it a name.
   • Copy the Client ID (UUID) and Client Secret shown at creation — the secret is displayed only once and cannot be retrieved afterward.
3. Identify your Authorization Host based on the zone that hosts your community:
   • US: auth.us.hivebrite.com
   • EU: auth.eu.hivebrite.com
   • APAC: auth.apac.hivebrite.com
   • CH: auth.ch.hivebrite.com
4. Note your community API host — it is your own subdomain, for example https://{your-community}.hivebrite.com.
5. Confirm which entities you need to extract (for example: members, events, groups, or donations).

Create a new ODBC DSN using the ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open ODBC Data Source Administrator.
   
2. In User DSN or System DSN, click Add.
3. Select ZappySys JSON Driver and click Continue.
   

Configure the Connection and API Settings

1. Set the Data Source Path or URL to the endpoint you want to read. Example for members:
   

   https://{your-community}.hivebrite.com/admin/v4/members

2. In the driver window, set Connection Type to HTTP and click Configure.
3. Set Credential Type to OAuth.
4. Fill in the OAuth settings:
   • OAuth Provider: Custom
   • OAuth Version: OAuth2
   • Grant Type: Client Credentials Grant
   • Client ID: your Hivebrite Client ID (UUID)
   • Client Secret: your Hivebrite Client Secret
   • Access Token URL: https://auth.{zone}.hivebrite.com/oauth2/token
   • Scopes / Permissions: leave empty
     

     Hivebrite – ODBC OAuth connection configuration

5. Go to the Grant Options tab and add the following under Extra attributes for the token request:
   

   audience=partner

6. Click OK to save the configuration.
   

   Hivebrite – ODBC OAuth connection configuration advanced.

7. Set HTTP Request Method to GET.
8. Add the request header:
   • Accept: application/json
9. Set the Array Filter (JSON Path) to $.data[*] — Hivebrite wraps collection responses in an data array. If you leave the filter empty, the driver will return a single row containing the envelope instead of one row per record.
10. Click Test Connection, then OK to save the DSN.
    

    Hivebrite – ODBC JSON Driver configuration

Preview Hivebrite data in the ODBC driver

1. Go to the Preview tab.
2. Adjust the generated query if needed, then click Preview Data.
3. Confirm that you get one row per Hivebrite record and that the columns are flattened as expected. Validate here before moving to Power BI — troubleshooting is much faster inside the driver.
   

   Hivebrite – ODBC JSON Driver result

Connect Power BI to Hivebrite via ODBC

1. Open Power BI Desktop.
2. Go to Home > Get Data > More….
3. Search for ODBC and click Connect.
   

   Power BI – Get data from ODBC connection

4. Select your Spotify DSN from the data source list.
5. Optionally enter a custom SQL query in Advanced options.
   

   Hivebrite – Power BI query

6. Click OK, review the preview, and click Load
   
   

   Hivebrite – Power BI result

Query Hivebrite data with SQL

Example 1: Select specific columns

SELECT
    id,
    first_name,
    last_name,
    email,
    status,
    created_at,
    updated_at
FROM _root_

Example 2: Filter and sort

SELECT
    id,
    first_name,
    last_name,
    email,
    status,
    created_at
FROM _root_
WHERE status = 'active'
ORDER BY created_at DESC

Example 3: Count members by status

SELECT
    status,
    COUNT(*) AS MemberCount
FROM _root_
GROUP BY status

Conclusion

Connecting Hivebrite to Power BI with the ZappySys JSON Driver gives you a repeatable, no-code path from your community platform to your analytics stack. With OAuth2 client credentials handled by the driver, pagination configured once, and server-side filters pushed into the API, you can build reports on members, events, and engagement that refresh on a schedule.

Explore the full capabilities of the ZappySys ODBC PowerPack to combine Hivebrite data with your CRM, finance, or marketing sources and build a unified view of your community operations.

The post How to get data from Hivebrite into Power BI appeared first on ZappySys Blog.

Spotify Web API exposes rich data for artists, albums, tracks, playlists, and categories. If you want to build dashboards from this data, you can connect Spotify to Power BI through an ODBC layer and query API responses using SQL.

In this tutorial, you will learn how to configure the ZappySys ODBC Driver for REST APIs for Spotify, test the connection, and load Spotify data into Power BI.

Steps

Create a Spotify Developer App

1. Open the Spotify Developer Dashboard and sign in with any free or premium Spotify account.
2. Click Create app, then enter an app name, description, and a redirect URL (for example: http://127.0.0.1:3000).
   

   Spotify – Create app

3. Open app Settings and copy your Client ID and Client Secret.
4. Store these credentials securely.

Create a New ODBC DSN Using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open ODBC Data Source Administrator.
   
2. In User DSN or System DSN, click Add.
3. Select ZappySys JSON Driver and click Continue.
   

Configure the Connection and API Settings

1. Enter a Spotify endpoint URL. Example:
   

   https://api.spotify.com/v1/search?q=genre:pop&type=artist&limit=50

2. In Connection Type, select OAuth and click Configure.
3. Set Credential Type to OAuth2 / Client Credentials Grant and fill in the following values:
   • Client ID: Your Spotify Client ID
   • Client Secret: Your Spotify Client Secret
   • Access Token URL: https://accounts.spotify.com/api/token
   • Scopes/Permissions: (leave empty)
4. Click OK to save HTTP authentication settings.
   

   Spotify ODBC OAuth connection

5. Set HTTP Request Method to GET.
6. Add the following HTTP Header:
   • Accept: application/json
7. Set JSON Path Filter to:
   

   $.artists.items[*]

8. Click Test Connection, then click OK to save the DSN.
   

   Spotify – ODBC JSON driver configuration

Preview Spotify Data in ODBC Driver

1. Open the Preview tab in the DSN configuration window.
2. Generate a query and click Preview Data.
3. Confirm rows are returned. If not, recheck credentials, endpoint URL, and JSON Path Filter.
   

   Spotify – ODBC preview data

Connect Power BI to Spotify via ODBC

1. Open Power BI Desktop.
2. Go to Home > Get Data > More….
3. Search for ODBC and click Connect.
   

   Power BI – Get data from ODBC connection

4. Select your Spotify DSN from the data source list.
5. Optionally enter a custom SQL query in Advanced options.
   

   Power BI – Enter query Spotify

6. Click OK, review the preview, and click Load.
   

   Power BI – Spotify Result

7. In the Navigator, select fields or tables you want to import into your model.

Query Spotify Data with SQL

Use custom SQL queries in the ODBC driver or Power BI to shape data before loading.

Example 1: List All Artists

SELECT
    id,
    name,
    type,
    popularity,
    followers_total,
    uri
FROM _root_

Example 2: Filter Highly Popular Artists

SELECT
    id,
    name,
    popularity,
    followers_total
FROM _root_
WHERE popularity >= 80
ORDER BY popularity DESC

Example 3: Artists with Large Followings

SELECT
    id,
    name,
    followers_total,
    popularity
FROM _root_
WHERE followers_total >= 1000000
ORDER BY followers_total DESC

Example 4: Search by Genre

SELECT
    id,
    name,
    genres,
    popularity
FROM _root_
WHERE genres LIKE '%pop%'
ORDER BY popularity DESC

Conclusion

Connecting Spotify to Power BI using the ZappySys ODBC Driver gives you a fast way to analyze music catalog trends and artist metrics with SQL and dashboards. Once your DSN is configured, you can reuse the same pattern for tracks, albums, playlists, categories, and market-specific reporting.

Explore more connectors and API integrations with the ZappySys ODBC Drivers.

The post How to get data from Spotify into Power BI appeared first on ZappySys Blog.

Introduction

Spotify provides rich music and podcast metadata through its Web API, including artists, albums, tracks, playlists, and categories. Many data teams need this data in SQL Server for analytics, trend reporting, and catalog enrichment.

In this tutorial, you will learn how to connect Spotify API data to SQL Server Integration Services (SSIS) by using ZappySys SSIS PowerPack. This approach helps you automate extraction and loading without building a custom API client.

Steps

Create a Spotify Developer App

1. Go to the Spotify Developer Dashboard and sign in with any free or premium Spotify account.
   

   Spotify – Create app

2. Click Create app, give it a name, description, and a Redirect URI (for example http://127.0.0.1:3000).
3. Go to the app Settings page and copy your Client ID and Client Secret.
4. Store both values securely and avoid hard-coding secrets directly in package components.

Create an OAuth2 Connection in SSIS

1. Create or open your SSIS project and package.
2. In Connection Managers, right-click and choose New Connection….
3. Select ZS-OAUTH from the SSIS connectors list.
   

   Create a new SSIS OAuth API Connection Manager

4. Set the following values:
   • OAuth Provider: Custom
   • OAuth Version: OAuth2
   • OAuth Grant Type: Client Credentials Grant
   • Client ID: Your Spotify Client ID
   • Client Secret: Your Spotify Client Secret
   • Access Token URL: https://accounts.spotify.com/api/token
   • Scopes/Permissions: (leave empty)
5. Click Test Connection to confirm a token is issued successfully, then click OK.
   

   Spotify – OAuth connection

Create and Configure JSON Source

1. Add a Data Flow Task in Control Flow and open it.
   

   Drag and drop Data flow

2. In Data Flow, drag and drop ZS JSON Source.
   

   SSIS JSON Source – Drag and Drop

3. Open the JSON Source editor and enable Use credentials.
4. Select the Spotify OAuth2 connection you created.
5. Set the API URL to a Spotify endpoint. Example to search artists by genre:
   

   https://api.spotify.com/v1/search?q=genre:pop&type=artist&limit=50

6. Set HTTP Request Method to GET.
7. Add the following HTTP Header:
   • Accept: application/json
8. Set JSON Path Filter based on the endpoint. For the search artists endpoint:
   

   $.artists.items[*]

9. Click Preview to confirm rows are returned, then click OK.
   

   Spotify – JSON source

Configure Destination and Load into SQL Server

1. Add an Upsert destination (or another destination of your choice, such as a Trash destination or JSON/CSV/XML destination).
2. Connect the output arrow from JSON Source to the destination component.
3. Configure your SQL Server connection and target table.
4. Check the options you want to use: Insert or/and Update.
5. Map the source columns to destination columns in the Mappings section.
   

   Spotify – Upsert destination

6. Click OK and execute the package.
7. Validate that Spotify rows have been loaded into your SQL Server table.
   

   Spotify – Upsert Destination example

Conclusion

You now have a practical SSIS pattern to extract Spotify Web API data and load it into SQL Server by using ZappySys SSIS PowerPack. With OAuth2 Client Credentials authentication, pagination handling, and proper column mapping, you can operationalize Spotify catalog data for BI and reporting use cases.

Explore the full capabilities of the ZappySys SSIS PowerPack to extend this pipeline with transformations, audits, error handling, and SQL Server Agent scheduling.

The post SSIS Tutorial: How to get data from Spotify appeared first on ZappySys Blog.

Introduction

Hivebrite is a community management platform used for memberships, events, directories, and engagement workflows. Many teams need Hivebrite data in SQL Server for reporting, segmentation, and operational analytics.

In this tutorial, you will learn how to connect Hivebrite API data to SQL Server Integration Services (SSIS) by using ZappySys SSIS PowerPack. You can then automate extraction and loading without writing a custom API client.

Steps

Prepare Hivebrite API access

1. Sign in to your Hivebrite admin area and go to Integrations → External Integrations.
2. Click Create a Service App and give it a name.
   • Copy the Client ID (UUID) and Client Secret shown at creation — the secret is displayed only once and cannot be retrieved afterward.
3. Identify your Authorization Host based on the zone that hosts your community:
   • US: auth.us.hivebrite.com
   • EU: auth.eu.hivebrite.com
   • APAC: auth.apac.hivebrite.com
   • CH: auth.ch.hivebrite.com

Create an OAuth2 connection in SSIS

1. Create or open your SSIS project and package.
2. In Connection Managers, right-click and select New Connection….
3. Select ZS-OAUTH from the SSIS connectors list.
   

   Create a new SSIS OAuth API Connection Manager.

4. Set the following values:
   • OAuth Provider: Custom
   • OAuth Version: OAuth2
   • OAuth Grant Type: Client Credentials Grant
   • Client ID: Your Hivebrite Client ID (UUID)
   • Client Secret: Your Hivebrite Client Secret
   • Access Token URL: https://auth.{zone}.hivebrite.com/oauth2/token
   • Scopes/Permissions: (leave empty)
     

     Hivebrite – OAuth connection configuration

5. Go to the OAuth2 Grant Options tab and add the following to the Extra attributes for the token request parameter:
   

   audience=partner

6. Then click OK to save the configuration.
   

   Hivebrite – OAuth connection advanced configuration

Create and configure JSON Source

1. Drag a Data Flow Task into Control Flow and open it.
   

   Drag and drop Data Flow

2. In Data Flow, drag and drop ZS JSON Source.
   

   SSIS JSON Source – Drag and Drop

3. Open the JSON Source editor and enable Use credentials.
4. Select the Hivebrite OAuth2 connection you created.
5. Set the API URL using your community’s API host. Example to extract members:
   

   https://{your-community}.hivebrite.com/admin/v4/members

6. Set HTTP Request Method to GET.
7. Add the following HTTP Header:
   • Accept: application/json
8. Set JSON Path Filter to $.data[*] — Hivebrite wraps all collection responses under an data array.
9. Click Preview to confirm rows are returned, then click OK.
   

   Hivebrite – JSON source example

Configure destination component

1. Add an Upsert destination (or another destination of your choice, such as a Trash destination or JSON/CSV/XML destination).
2. Connect the output arrow from JSON Source to the destination component.
3. Configure your SQL Server connection and target table.
4. Check the options you want to use: Insert or/and Update.
5. Map the source columns to destination columns in the Mappings section.
   

   Hivebrite – Upsert destination

6. Click OK and execute the package.
7. Validate that Hivebrite rows have been loaded into your SQL Server table.
   

   Hivebrite – Upsert Destination example

Conclusion

You now have a repeatable SSIS pattern to extract Hivebrite API data and load it into SQL Server by using ZappySys SSIS PowerPack. With OAuth2 Client Credentials authentication, proper pagination, and column mapping, you can operationalize Hivebrite data for BI and reporting workflows.

Explore the full capabilities of the ZappySys SSIS PowerPack to extend this setup with advanced transformations, retry logic, auditing, and scheduling through SQL Server Agent.

The post SSIS Tutorial: How to get data from Hivebrite appeared first on ZappySys Blog.

Cin7 is a connected inventory and order management platform used by growing businesses to synchronise products, stock, orders, and customer data across sales channels. Many organisations need Cin7 data in Power BI to monitor inventory health, order trends, and fulfilment performance.

Using the ZappySys ODBC Driver for REST APIs, you can query Cin7 REST API data with SQL and load it into Power BI without writing custom connector code.

This tutorial shows how to create a Cin7 ODBC DSN, configure API authentication, preview data, connect Power BI, and run practical SQL queries.

Steps

Get Cin7 API Credentials

1. Sign in to your Cin7 account.
2. Open Settings → Integrations & API → API v1 in your Cin7 admin portal.
   • Note your API Username shown on the page.
   • Click Add New API Connection, give it a name (e.g. ZappySys), and copy the generated API Key.
   

   Cin7 – Generate new API connection

3. Store both values securely — the API Username and API Key together act as your login credentials.
   

   Cin7 – API credentials

4. Note your API base URL: https://api.cin7.com/api.

Create a New ODBC DSN Using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open ODBC Data Source Administrator.
   
2. In User DSN or System DSN, click Add.
3. Select ZappySys JSON Driver, then click Continue.
   

Configure Cin7 API Connection

1. Enter a Cin7 endpoint URL in this format:
   https://api.cin7.com/api/v1/Products
2. In Connection Type, select HTTP and click Configure.
3. Set Credential Type to Basic Auth (Username/Password).
4. Set Username to your Cin7 API Username.
5. Set Password to your Cin7 API Key.
6. Click OK to save HTTP authentication settings.
   

   Cin7 – ODBC HTTP connection configuration

7. Set HTTP Request Method to GET.
8. Set JSON Path Filter to $.Products[*] for the Products endpoint.
9. Click Test Connection, then click OK to save the DSN.
   

   Cin7 – JSON Driver configuration

Preview Cin7 Data in ODBC Driver

1. Open the Preview tab in the DSN configuration window.
2. Generate a query and click Preview Data.
3. Confirm rows are returned. If not, recheck endpoint URL, credentials, and JSON Path Filter.
   

   Cin7 – JSON Driver result

Connect Power BI to Cin7 via ODBC

1. Open Power BI Desktop.
2. Go to Home > Get Data > More….
3. Search for ODBC and click Connect.
   

   Power BI – Get data from ODBC connection

4. Select your Cin7 DSN from the data source list.
5. Optionally enter a custom SQL query in Advanced options.
   

   Cin7 – Power BI select driver

6. Click OK, review the preview, and click Load.
   

   Cin7 – Power BI result

7. In the Navigator, select fields or tables you want to import into your model.

Query Cin7 Data with SQL

Use custom SQL queries in the ODBC driver or Power BI to shape data before loading.

Example 1: List Products

SELECT
    ID,
    StyleCode,
    Name,
    Category,
    Brand,
    IsActive,
    ModifiedDate
FROM Products

Example 2: Active Products Only

SELECT
    ID,
    StyleCode,
    Name,
    IsActive
FROM Products
WHERE IsActive=true

Example 3: Recently Modified Products (Last 30 Days)

SELECT
    ID,
    StyleCode,
    Name,
    ModifiedDate
FROM Products
WHERE ModifiedDate >= <<today-10d,FUN_TO_DATE>>

Conclusion

Connecting Cin7 to Power BI using the ZappySys ODBC Driver gives you a fast, SQL-friendly way to build inventory and sales analytics from Cin7 API data. You can centralise operational data, model it in Power BI, and publish dashboards without building custom connectors.

Explore the full capabilities of the ZappySys ODBC Drivers to integrate Cin7 and other APIs into your reporting workflow.

The post How to get data from Cin7 into Power BI appeared first on ZappySys Blog.

Cin7 is a connected inventory and order management platform used by growing businesses to synchronise products, stock, orders, and customer data across multiple sales channels. Many organisations need Cin7 data in SQL Server for reporting, demand planning, fulfilment tracking, and analytics.

In this tutorial, you will learn how to connect to Cin7 REST APIs using SQL Server Integration Services (SSIS) with the ZappySys SSIS PowerPack. This approach helps you build repeatable ETL pipelines without writing custom API integration code.

Steps

Get Cin7 API Credentials

1. Sign in to your Cin7 account.
2. Open Settings → Integrations & API → API v1 in your Cin7 admin portal.
   • Note your API Username shown on the page.
   • Click Add New API Connection, give it a name (e.g. ZappySys), and copy the generated API Key.
   

   Cin7 – Generate new API connection

3. Store both values securely — the API Username and API Key together act as your login credentials.
   

   Cin7 – API credentials

Get Cin7 Base URL and Endpoint Path

1. Identify the REST endpoint you want to query (for example, products, customers, or sales orders).
2. Keep your API base URL and endpoint path ready for SSIS configuration.
3. Example:
   https://api.cin7.com/api/v1/Products

Create an HTTP Connection in SSIS

1. Create or open your SSIS project and package.
2. In Connection Managers, right-click and select New Connection….
3. Select ZS-HTTP from the SSIS connectors list.
4. Set Credentials Type to Basic Auth.
5. Enter your API Username in the Username field and your API Key in the Password field
6. Click OK to save the connection.
   

   Cin7-HTTP connection

Create and Configure JSON Source

1. Drag a Data Flow Task into Control Flow and open it.
2. In Data Flow, drag and drop the ZS JSON Source.
3. Open the JSON Source editor and enable Use credentials.
4. Select the Cin7 HTTP connection you created earlier.
5. Set the API URL. Example to extract products:
   

   https://api.cin7.com/api/v1/products

6. Set HTTP Request Method to GET.
7. Add the following HTTP Header:
   1. Accept: application/json
8. Set JSON Path Filter based on the endpoint (for example, $.Products[*] for the Products endpoint).
9. Click Preview to confirm rows are returned, then click OK.
   

   Cin7 – JSON Source configuration

Configure Destination Component

1. Add an Upsert destination (or another destination of your choice, such as a Trash destination or JSON/CSV/XML destination).
2. Connect the output arrow from JSON Source to the destination component.
3. Configure your SQL Server connection and target table.
4. Check the options you want to use: Insert or/and Update.
5. Map the source columns to destination columns in the Mappings section.
   

   Cin7 – Upsert destination

6. Click OK and execute the package.
7. Validate that Cin7 rows have been loaded into your SQL Server table.
   

   Cin7 – Upsert Destination example

Conclusion

You now have a working SSIS integration to extract Cin7 data using ZappySys SSIS PowerPack and Cin7 REST APIs. With this pattern, you can automate extraction of inventory, product, and order data into SQL Server for reporting and analytics.

Explore the full capabilities of the ZappySys SSIS PowerPack to optimise your data integration tasks. By applying this pattern, you can extend your solution to include transformations, data validation, error handling, and scheduling through SQL Server Agent.

The post SSIS Tutorial: How to get data from Cin7 appeared first on ZappySys Blog.