Exalate Python API Docs | dltHub
Build a Exalate-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Exalate API Reference Documentation details REST API usage for integration. To make REST API calls, use the HTTP client in script rules. Monitor Exalate REST APIs for performance tracking. The REST API base URL is https://<your-instance>.exalate.cloud and Requests to your Exalate instance and monitoring endpoint require instance credentials; calls to external systems (ServiceNow, Zendesk, Salesforce) require those systems' credentials and return lists under keys such as 'result' or 'records'..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Exalate data in under 10 minutes.
What data can I load from Exalate?
Here are some of the endpoints you can load from Exalate:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| monitoring | (instance monitoring endpoint) e.g. https://.exalate.cloud/<monitoring_path> | GET | (varies) | Exalate REST API monitoring endpoint provided per customer (request via support). |
| servicenow_incidents | /api/now/v1/table/incident?sysparm_query=... | GET | result | ServiceNow table query example returned by HTTP client (list under "result"). |
| zendesk_ticket_comments | /api/v2/tickets/{id}/comments | GET | comments | Zendesk example response when called from Exalate HTTP client (comments list under "comments"). |
| salesforce_sobjects | /services/data/v54.0/sobjects/ContentDocument/{id} | GET | (top-level object) | Salesforce object example returned as single object (no list). |
| salesforce_query_records | /services/data/v54.0/sobjects/.../casecomments | GET | records | Salesforce list responses returned with "records" key. |
| azure_workitems | /{project}/_apis/wit/workitems/{id}?api-version=5.1 | GET | (top-level object) | Azure DevOps work item example returned as single object. |
How do I authenticate with the Exalate API?
API access is performed against your Exalate instance and requires instance credentials. Calls to external systems (ServiceNow, Salesforce, Zendesk) require the respective system's credentials.
1. Get your credentials
- Log into your Exalate instance as an admin (https://.exalate.cloud). 2) Open the Admin / Monitoring or API settings page and request or create API/monitor credentials per the monitoring/API guide. 3) For integrations that call external systems from Exalate (ServiceNow, Zendesk, Salesforce), obtain credentials or API tokens from those external systems and store them in Exalate script rules or connection configuration. 4) If you need an Exalate‑provided monitoring endpoint, contact Exalate support as described in the REST API Monitoring Guide to request a customer monitor endpoint and credentials.
2. Add them to .dlt/secrets.toml
[sources.exalate_source] instance_credentials = "user:password_or_token_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Exalate API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python exalate_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline exalate_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset exalate_data The duckdb destination used duckdb:/exalate.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline exalate_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads servicenow_incidents and zendesk_ticket_comments from the Exalate API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def exalate_source(instance_credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<your-instance>.exalate.cloud", "auth": { "type": "http_basic_or_token", "password_or_token": instance_credentials, }, }, "resources": [ {"name": "servicenow_incidents", "endpoint": {"path": "api/now/v1/table/incident?sysparm_query={query}", "data_selector": "result"}}, {"name": "zendesk_ticket_comments", "endpoint": {"path": "api/v2/tickets/{ticket_id}/comments", "data_selector": "comments"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="exalate_pipeline", destination="duckdb", dataset_name="exalate_data", ) load_info = pipeline.run(exalate_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("exalate_pipeline").dataset() sessions_df = data.servicenow_incidents.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM exalate_data.servicenow_incidents LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("exalate_pipeline").dataset() data.servicenow_incidents.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Exalate data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Exalate?
Request dlt skills, commands, AGENT.md files, and AI-native context.