---
sourceDocument: Australia API Reference
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/api-reference

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Architecture

# Live Connect architecture {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Live Connect provides secure, read-only access to ServiceNow data for external BI platforms via industry-standard database APIs, while maintaining all existing security policies and role-based restrictions.

## Architecture overview {#sql-api-architecture__section_mfj_wc2_m3c}

Live Connect uses ServiceNow web services to provide a query-only interface. This architecture enables direct connections from ODBC and JDBC-compatible tools to your ServiceNow data without data export or replication.

The diagram shows the high‑level architecture of how the Live Connect connects external BI tools to ServiceNow tables via ODBC and JDBC drivers, while enforcing security and access controls.
Figure 1. Live Connect Architecture diagram

## Key architectural components {#sql-api-architecture__section_pfj_wc2_m3c}

The Live Connect architecture consists of the following key components:

Client applications
:   External BI tools and data analysis platforms such as Pyramid Analytics,Power BI, Tableau, DBeaver, and DBvisualizer that connect using ODBC or JDBC protocols.

ODBC/JDBC drivers
:   Industry-standard database drivers that enable client applications to establish connections and execute SQL queries against ServiceNow data.

ServiceNow Instance

:   Inside the ServiceNow instance, three layers handle the request:

:
    Security layer: In this layer, six controls are applied in sequence:

    1. IP Access Policy
    2. Rate Limit
    3. Auth + Role check
    4. egress_sql ACL
    5. Strict Security Mode
    6. WDF Token Metering

:   REST layer: There are separate dedicated services for each driver (ODBC REST Service and JDBC REST Service). Both services are restricted to SELECT-only queries and rate limited. They are accessible only by the driver
    internally.

:   Database tier: Queries reach the Primary DB first (read-only, used as fallback if no replica), but are preferably routed to a Read Replica. The Read Replica isolates BI workload from the primary database and handles all
    JDBC/ODBC SELECTs.

## How the architecture works {#sql-api-architecture__section_qfj_wc2_m3c}

When you connect your BI tool to ServiceNow through the Live Connect, the following process occurs:

1. Your BI tool establishes a standard database connection using either ODBC or JDBC APIs.
2. The connection request is authenticated against ServiceNow user credentials configured for Live Connect access.
3. After authentication, you can write SQL queries to retrieve data from authorized ServiceNow tables and fields.
4. The Live Connect processes your queries through the security services layer, applying all security controls and access restrictions.
5. Query results are returned in standard tabular format, which your BI tool can visualize, analyze, or export.
{#sql-api-architecture__ol_rfj_wc2_m3c}