---
title: "Config"
method: GET
path: "/data-explorer/config"
---

# Config

`GET /data-explorer/config`

## Request

- Base URL: `https://api.traversal.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.traversal.com/data-explorer/config`
- Auth: none declared

## Query parameters

- `organization_id` string, uuid, nullable

## Response `200`

Successful Response

- ExplorerConfigResponse: Available explorer sources for the selected organization. Each list is derived from integration instances, not hardcoded customer aliases, so adding another Confluence site or Splunk cluster shows up automatically. Dataset rows (Splunk indexes) stay server-side; the UI addresses the cluster, and SPL names the index.
  - `confluence` ExplorerInstance[], required
    - `id` string, uuid, required
    - `label` string, required
  - `jira` ExplorerInstance[], required
    - `id` string, uuid, required
    - `label` string, required
  - `splunk` ExplorerInstance[], required
    - `id` string, uuid, required
    - `label` string, required

## Other responses

- `422`: Validation Error

## Changes

> 66 revisions in range; 9 not diffed.

- **2026-08-27** `5b3d8e378765`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/traversal/apis/traversal-api/changes/data-explorer/config/get.md)

---

[API](https://skmtc.dev/traversal/apis/traversal-api.md) - [All operations](https://skmtc.dev/traversal/apis/traversal-api/llms.txt) - [OpenAPI document](https://skmtc.dev/traversal/apis/traversal-api/revisions/31e1a8b7cf89?raw)