Splunk Observability Cloud Python API Docs | dltHub
Build a Splunk Observability Cloud-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Splunk Observability Cloud provides REST APIs for querying and managing metrics, traces, events, dashboards, detectors, integrations, organizations, tokens, and other observability resources. The REST API base URL is https://api.{realm}.observability.splunkcloud.com/v2 and X-SF-TOKEN header containing a user API/session token for REST API requests.
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 add "dlt[hub]" and start loading Splunk Observability Cloud data in under 10 minutes.
What data can I load from Splunk Observability Cloud?
Here are some of the endpoints you can load from Splunk Observability Cloud:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| charts | chart | GET | results | List/search charts; the legacy client identifies this as the chart collection endpoint. |
| dashboards | dashboard | GET | results | List dashboards; offset/limit pagination is documented for dashboard retrieval. |
| dashboard_groups | dashboardgroup | GET | results | List/search dashboard groups; the legacy client accumulates results and uses count. |
| detectors | detector | GET | results | List/search detectors; the legacy client exposes paged detector retrieval. |
| incidents | incident | GET | results | Incident collection endpoint identified by the legacy SignalFx client. |
| data_links | crosslink | GET | results | Data-link collection endpoint identified by the legacy SignalFx client and current API reference. |
| metrics | metric | GET | results | Metric metadata search endpoint; supports query/orderBy/offset/limit in the legacy client. |
| dimensions | dimension | GET | results | Dimension metadata search endpoint; supports query/orderBy/offset/limit in the legacy client. |
| metric_time_series | metrictimeseries | GET | results | Metric-time-series metadata search endpoint. |
| tags | tag | GET | results | Tag collection endpoint identified by the legacy SignalFx client. |
| organizations | organization | GET | results | Organization collection endpoint identified by the legacy SignalFx client and current API reference. |
| events_v2 | event/find | GET | Retrieve-events V2 endpoint; response selector was not exposed by the indexed reference, so it is left blank rather than inferred. |
How do I authenticate with the Splunk Observability Cloud API?
Send the credential in the X-SF-TOKEN request header, without a Bearer prefix. For the REST metadata/configuration API, use a user API/session token; organization access tokens are intended for data-ingest requests. JSON requests commonly also send Content-Type: application/json.
1. Get your credentials
- Sign in to your Splunk Observability Cloud organization. 2. Open the organization/admin settings and navigate to Authentication and security > Authentication tokens (the exact menu label can vary by UI version). 3. Create an organization access token for REST API use, select the minimum required scopes (for dashboard management, API access/read-write permissions as appropriate), and copy the secret when it is shown; it may not be displayed again. Organization access tokens are the correct credential for API requests that send data, while user/session tokens are intended for user-authenticated API operations. 4. For a user/session token instead, retrieve the automatically generated token from the user profile's Info/actions area, or have an administrator create one when elevated permissions are required. 5. Use the token in every request as the X-SF-TOKEN header. Do not put the token in source control; store it in an environment variable or a secrets manager.
2. Add them to .dlt/secrets.toml
[sources.splunk_observability_cloud_source] api_key = "your_splunk_observability_org_or_session_token" api_url = "https://api.us0.observability.splunkcloud.com"
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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 Splunk Observability Cloud 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:
uv run python splunk_observability_cloud_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline splunk_observability_cloud_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset splunk_observability_cloud_data The duckdb destination used duckdb:/splunk_observability_cloud.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 /dashboard and /dashboard/{id}’ from the Splunk Observability Cloud 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 splunk_observability_cloud_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.{realm}.observability.splunkcloud.com/v2", "auth": {"type": "api_key", "api_key": api_token, "name": "X-SF-TOKEN", "location": "header"}, }, "resources": [ {"name": "dashboards", "endpoint": {"path": "dashboard", "data_selector": "results"}}, {"name": "dashboard_groups", "endpoint": {"path": "dashboardgroup", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="splunk_observability_cloud_pipeline", destination="duckdb", dataset_name="splunk_observability_cloud_data", ) load_info = pipeline.run(splunk_observability_cloud_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("splunk_observability_cloud_pipeline").dataset() sessions_df = data.dashboards.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM splunk_observability_cloud_data.dashboards LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("splunk_observability_cloud_pipeline").dataset() data.dashboards.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 Splunk Observability Cloud 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 harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Splunk Observability Cloud?
Request dlt skills, commands, AGENT.md files, and AI-native context.