Zscaler (OneAPI)

🚀 Quickstart

Connect to Zscaler OneAPI with Nango and see data flow in 2 minutes.

Create the integration

In Nango (free signup), go to Integrations -> Configure New Integration -> Zscaler (OneAPI).

Authorize Zscaler

Go to Connections -> Add Test Connection -> Authorize, then enter your vanity domain, Zscaler cloud, ZPA customer ID, and the client ID and client secret of a ZIdentity API client. Later, you’ll let your users do the same directly from your app.

Call the Zscaler API

Let’s make your first request to the Zscaler Internet Access (ZIA) API to get the configuration activation status. Replace the placeholders below with your Environment API key, integration ID, and connection ID:

cURL
Node

curl "https://api.nango.dev/proxy/zia/api/v1/status" \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>"

Install Nango’s backend SDK with npm i @nangohq/node. Then run:

import { Nango } from '@nangohq/node';

const nango = new Nango({ apiKey: '<NANGO-API-KEY>' });

const res = await nango.get({
    endpoint: '/zia/api/v1/status',
    providerConfigKey: '<INTEGRATION-ID>',
    connectionId: '<CONNECTION-ID>'
});

console.log(res.data);

Paths are relative to your API host, such as https://api.zsapi.net on the production cloud. ZIA paths start with /zia/api/v1, and Zscaler Private Access (ZPA) paths start with /zpa/mgmtconfig/v1/admin/customers/<CUSTOMER-ID>. Nango gets an access token with your client credentials and renews it before it expires.Or fetch credentials with the Node SDK or API.✅ You’re connected! Check the Logs tab in Nango to inspect requests.

Implement Nango in your app

Follow our quickstart to integrate Nango in your app.

API gotchas

Your Zscaler tenant must be on ZIdentity to use OneAPI. Tenants that still use the legacy per-product APIs aren’t supported.

This integration supports the production, beta, and government (FedRAMP) clouds. Each cloud has its own authentication domain and API host, which users pick when they connect. Zscaler doesn’t offer a self-hosted OneAPI.

ZPA paths include your ZPA customer ID, which is saved in the connection config as customerId.

An API client only gets the scopes you assign on its Resources tab in ZIdentity. A 401 or 403 usually means a scope is missing.

Overview

1,000+ APIs & Integrations

🚀 Quickstart

📚 Zscaler (OneAPI) integration guides

API gotchas

🧩 Pre-built syncs & actions for Zscaler (OneAPI)

​🚀 Quickstart

​📚 Zscaler (OneAPI) integration guides

​API gotchas

​🧩 Pre-built syncs & actions for Zscaler (OneAPI)

🚀 Quickstart

📚 Zscaler (OneAPI) integration guides

API gotchas

🧩 Pre-built syncs & actions for Zscaler (OneAPI)