Skip to main content

Data sources

The connections the portal's data comes from — an API described by OpenAPI, an MCP server, a read-only database or a Kobana product from the catalog. The dashboard calls them Connectors. There is no generic create: each kind has its own (openapi create, mcp create, database create, catalog create), and test create tries a connection before saving it. sync queues the sync of every entity the source feeds, schedule sets how often it runs and spec replaces the OpenAPI spec.

CommandHTTPDescription
data-sources listGET /v1/data_sourcesList data sources
data-sources getGET /v1/data_sources/{id}Get a data source
data-sources updatePATCH /v1/data_sources/{id}Update a data source
data-sources deleteDELETE /v1/data_sources/{id}Delete a data source
data-sources authorizePOST /v1/data_sources/{id}/authorizeAuthorize an MCP data source
data-sources schedulePUT /v1/data_sources/{id}/scheduleSchedule the sync of a data source
data-sources specPUT /v1/data_sources/{id}/specReplace the spec of a data source
data-sources syncPOST /v1/data_sources/{id}/syncSync a data source
data-sources catalog listGET /v1/data_sources/catalogList Kobana catalog products
data-sources catalog createPOST /v1/data_sources/catalogConnect a Kobana product
data-sources database createPOST /v1/data_sources/databaseCreate a database data source
data-sources logs listGET /v1/data_sources/{id}/logsList the request log of a data source
data-sources logs getGET /v1/data_sources/{id}/logs/{log_id}Get a request of a data source
data-sources mcp createPOST /v1/data_sources/mcpCreate an MCP data source
data-sources openapi createPOST /v1/data_sources/openapiCreate an OpenAPI data source
data-sources openapi analyze createPOST /v1/data_sources/openapi/analyzeAnalyze an OpenAPI spec
data-sources operations updatePATCH /v1/data_sources/{id}/operations/{operation_id}Enable or disable an operation of a data source
data-sources test createPOST /v1/data_sources/testTest a connection before saving

Examples​

--params carries query, path and header parameters (id, page, filters, X-Workspace-Id); --json carries the request body; --fields limits which fields come back — worth using on every list/get to save context. See Global flags for the full reference.

# List data sources
kobana dashboards data-sources list \
  --fields "id,name,kind,status,last_synced_at"

# Get a data source
kobana dashboards data-sources get --params '{"id": "DATA_SOURCE_ID"}'

# List Kobana catalog products
kobana dashboards data-sources catalog list

# Connect a Kobana product
kobana dashboards data-sources catalog create \
  --json '{"product": "billing", "environment": "production", "token": "TOKEN_DO_PRODUTO"}'

# Create an MCP data source
kobana dashboards data-sources mcp create \
  --json '{"name": "CRM", "url": "https://mcp.example.com/mcp", "transport": "http"}'

# Sync a data source
kobana dashboards data-sources sync \
  --params '{"id": "DATA_SOURCE_ID"}' \
  --dry-run

# Schedule the sync of a data source
kobana dashboards data-sources schedule \
  --params '{"id": "DATA_SOURCE_ID"}' \
  --json '{"cron": "0 */6 * * *", "timezone": "America/Sao_Paulo"}'

Next steps​