sisense.com

Sisense REST API Endpoint Index — Linux 2026.1

Every Sisense REST API endpoint on Linux (API v2, v1, v0) on one page: method, path, and a one-line summary. For an interactive explorer with request/response schemas and try-it-out, use the Swagger UI reference (v2 · v1 · v0). The raw specs are listed at /swagger-specs/index.json.

147 endpoints across API v2, v1, v0.

REST API v2 (Linux 2026.1)

58 endpoints across 11 tags (OpenAPI 3). Raw spec: /swagger-specs/linux/latest/v2.openapi.json (stable latest alias) or /swagger-specs/linux/2026.1/v2.openapi.json (this exact version).

B2D Connection

  • GET /api/v2/b2d-connection — Get all Build to Destination Connections
  • POST /api/v2/b2d-connection — Build to Destination connections
  • PATCH /api/v2/b2d-connection — Update Build to Destination connection
  • DELETE /api/v2/b2d-connection/{destination} — Delete Build to Destination Connection

Builds

  • GET /api/v2/builds/{buildId} — Get Build Task by ID
  • DELETE /api/v2/builds/{buildId} — Cancel/Stop a Build Task
  • GET /api/v2/builds/elementdependencies — Get element dependencies

Cluster

  • GET /api/v2/cluster-nodes — List Cluster Nodes
  • GET /api/v2/cluster-nodes/{nodeId} — Get Cluster Node

Connections Management

  • GET /api/v2/connections — Retrieves Managed Connections List
  • POST /api/v2/connections — Create a New Managed Connection
  • GET /api/v2/connections/{connectionId} — Retrieves a Managed Connection
  • PATCH /api/v2/connections/{connectionId} — Update specified Managed Connection
  • DELETE /api/v2/connections/{connectionId} — Delete specified Managed Connection
  • PATCH /api/v2/connections/{connectionId}/shares/update — Update Managed Connection Shares

Data Groups

  • GET /api/v2/data-groups — List Data Groups
  • POST /api/v2/data-groups — Create Data Group
  • GET /api/v2/data-groups/ — List Data Groups
  • POST /api/v2/data-groups/ — Create Data Group
  • GET /api/v2/data-groups/{dataGroupId} — Get Data Group by ID
  • PATCH /api/v2/data-groups/{dataGroupId} — Update Data Group
  • DELETE /api/v2/data-groups/{dataGroupId} — Delete Data Group
  • GET /api/v2/data-groups/{dataGroupId}/ — Get Data Group by ID
  • PATCH /api/v2/data-groups/{dataGroupId}/ — Update Data Group
  • DELETE /api/v2/data-groups/{dataGroupId}/ — Delete Data Group
  • POST /api/v2/data-groups/{dataGroupId}/datamodels — Assign Datamodels to Data Group
  • POST /api/v2/data-groups/{dataGroupId}/datamodels/ — Assign Datamodels to Data Group
  • GET /api/v2/data-groups/default — Get Default Data Group
  • GET /api/v2/data-groups/default/ — Get Default Data Group

Datamodel Imports/Exports

  • GET /api/v2/datamodel-exports/stream/full — Export Datamodel as stream
  • GET /api/v2/datamodel-exports/stream/full/ — Export Datamodel as stream
  • POST /api/v2/datamodel-imports/stream/full — Import full Datamodel as stream

Destination Storage

  • GET /api/v2/storage — storage parameters
  • POST /api/v2/storage — Create storage
  • PATCH /api/v2/storage — Update storage parameters
  • DELETE /api/v2/storage — Delete All Storage Parameters
  • GET /api/v2/storage/{storageType} — storage parameters
  • DELETE /api/v2/storage/{storageType} — Delete Storage

Scheduled Build

  • GET /api/v2/datamodels/{datamodelId}/schedule — get schedule build by cube id
  • POST /api/v2/datamodels/{datamodelId}/schedule — Add build schedule for cube
  • DELETE /api/v2/datamodels/{datamodelId}/schedule — delete schedule

backups

  • GET /api/v2/backups — List backups
  • POST /api/v2/backups — Start on-demand backup
  • GET /api/v2/backups/{backup_id} — Get backup info
  • DELETE /api/v2/backups/{backup_id} — delete backup
  • POST /api/v2/backups/cancel — cancel ongoing backup process
  • POST /api/v2/backups/restore/{directory} — Start system restore
  • GET /api/v2/backups/schedules — list backup schedules
  • POST /api/v2/backups/schedules — Create backup schedule
  • GET /api/v2/backups/schedules/{schedule_id} — get backup schedule
  • PATCH /api/v2/backups/schedules/{schedule_id} — Update backup schedule
  • DELETE /api/v2/backups/schedules/{schedule_id} — Delete backup schedule

connectors

  • POST /api/v2/connectors/{provider}/table_preview — Returns table preview stream

tests

  • GET /api/v2/tests — Get all tests configurations
  • GET /api/v2/tests/{idOrName} — Get test configuration details
  • PUT /api/v2/tests/{idOrName} — Set test configuration
  • GET /api/v2/tests/results — Get last tests results
  • POST /api/v2/tests/run — Run tests and save / return tests results according to the provided flag

REST API v1 (Linux 2026.1)

52 endpoints across 10 tags (OpenAPI 3). Raw spec: /swagger-specs/linux/latest/v1.openapi.json (stable latest alias) or /swagger-specs/linux/2026.1/v1.openapi.json (this exact version).

build-rest-controller

  • POST /api/v1/elasticubes/next/getContextFromExpression — check auto complete for custom query
  • POST /api/v1/elasticubes/next/runColumnQuery — check column query validation
  • POST /api/v1/elasticubes/next/runTableQuery — check table query validation
  • GET /api/v1/elasticubes/servers/next/{server}/{dataSourceTitle}/isBuilding — Build contract: checks if there is running build for given data source
  • POST /api/v1/elasticubes/servers/next/{server}/build — run build cube
  • POST /api/v1/elasticubes/servers/next/{server}/explain_build — explain build without type
  • POST /api/v1/elasticubes/servers/next/{server}/explain_build/{buildType} — explain build by build type

connections

  • GET /api/v1/connection — Returns a list of connections
  • GET /api/v1/connection/{id} — Returns a connection by its ID
  • DELETE /api/v1/connection/{id} — Removes a connection
  • GET /api/v1/connection/recent — Returns recently used connection objects

connectors

  • GET /api/v1/connectors/{provider}/ui_config — Returns object that describes the UI connection manifest

data-exploration

  • POST /api/v1/data-exploration/refresh — Refresh data exploration
  • POST /api/v1/data-exploration/refresh/datasource — Refresh data exploration by Datasource
  • GET /api/v1/data-exploration/status — Return status of data exploration
  • GET /api/v1/data-exploration/user-influences — Returns user likes

formulas

  • GET /api/v1/formulas — Get multiple formulas
  • POST /api/v1/formulas — Create a new formula
  • GET /api/v1/formulas/{formulaId} — Get a specific formula by id
  • PATCH /api/v1/formulas/{formulaId} — Update an existing formula
  • DELETE /api/v1/formulas/{formulaId} — Delete a formula
  • GET /api/v1/formulas/usage — Get multiple formulas usage data

live-connectors

  • GET /api/v1/live_connectors — Returns the list of available live connector services
  • GET /api/v1/live_connectors/{provider} — Returns object that describes the connection manifest (parameters)
  • POST /api/v1/live_connectors/{provider}/count — Returns count of entries in table
  • POST /api/v1/live_connectors/{provider}/list_databases — Returns list of databases
  • POST /api/v1/live_connectors/{provider}/list_schemas — Returns a list of schemas in a database
  • POST /api/v1/live_connectors/{provider}/list_table_schemas — Returns a list of tables in a database
  • POST /api/v1/live_connectors/{provider}/table_preview — Returns data preview
  • POST /api/v1/live_connectors/{provider}/table_schema_details — Returns a table's schema
  • POST /api/v1/live_connectors/{provider}/test_connection — Returns an object with status = OK after a successful connection

management-rest-controller

  • GET /api/v1/elasticubes/servers/next — Get servers with next ECubes
  • GET /api/v1/elasticubes/servers/next/{server}/{cubeTitle} — Get Ecm Model of a specific elasticube

notebook-router-controller

  • GET /api/v1/notebooks
  • POST /api/v1/notebooks
  • PUT /api/v1/notebooks
  • PATCH /api/v1/notebooks
  • DELETE /api/v1/notebooks
  • HEAD /api/v1/notebooks
  • OPTIONS /api/v1/notebooks
  • GET /api/v1/notebooks/**
  • POST /api/v1/notebooks/**
  • PUT /api/v1/notebooks/**
  • PATCH /api/v1/notebooks/**
  • DELETE /api/v1/notebooks/**
  • HEAD /api/v1/notebooks/**
  • OPTIONS /api/v1/notebooks/**

suggestion

  • POST /api/v1/suggestions — Return suggestions for an entity
  • POST /api/v1/suggestions/refresh — Refresh suggestions data and ranking
  • POST /api/v1/suggestions/refresh/datasource — Refresh suggestions data and ranking by Datasource
  • GET /api/v1/suggestions/status — Return status of suggestions

translator-utils-rest-controller

  • GET /api/v1/settings/translation — Returns translation settings

REST API v0 (Linux 2026.1)

37 endpoints across 2 tags (OpenAPI 3). Raw spec: /swagger-specs/linux/latest/v0.openapi.json (stable latest alias) or /swagger-specs/linux/2026.1/v0.openapi.json (this exact version).

management-rest-controller

  • GET /api/datasources — Gets all datasources
  • DELETE /api/elasticubes/{server}/{cubeName}/delete — Delete Cube by name
  • POST /api/elasticubes/{server}/{dataSourceId}/detach — Detach Cube
  • POST /api/elasticubes/{server}/{instanceId}/detachInstanceId — Detach Cube
  • POST /api/elasticubes/{server}/attach — Attach Cube
  • POST /api/elasticubes/{server}/availableDatasourcesInfo — info available Datasources
  • POST /api/elasticubes/{server}/info — info Cubes
  • GET /api/elasticubes/sample — Attach Sample
  • GET /api/elasticubes/servers — Get servers with ECubes
  • GET /api/elasticubes/servers/{server} — Get cubes
  • GET /api/elasticubes/servers/{server}/identity — Get server identity
  • GET /api/elasticubes/servers/{server}/simple — Get database simple

query-rest-controller

  • POST /api/datasources/{cubeName}/jaql — execute query
  • POST /api/datasources/{cubeName}/jaql/csv — Execute query
  • POST /api/datasources/{cubeName}/jaql/explain — Explain query
  • POST /api/datasources/{cubeName}/jaql/sql
  • GET /api/datasources/{cubeName}/sql — Execute sql
  • POST /api/datasources/{cubeName}/sql — Execute sql
  • GET /api/datasources/{dataSourceFullName}/{tableName}/connectedTables — Get connected tables
  • POST /api/datasources/{fullName}/calculated-dimension/parse — Parse calculated dimension
  • POST /api/datasources/{fullName}/parse — Parse jaql
  • POST /api/datasources/{liveFullName}/fields/search — Get fields
  • POST /api/datasources/{server}/{cubeName}/cancel_queries — Cancel queries
  • POST /api/datasources/{server}/{title}/fields/search — Get fields
  • POST /api/datasources/{server}/elasticubes/{cubeName}/preview — Execute sql for preview
  • POST /api/datasources/{server}/elasticubes/{cubeName}/sql — Execute sql
  • GET /api/datasources/{title} — Cancel all queries
  • GET /api/datasources/{title}/fields — Get fields
  • POST /api/datasources/{title}/fields/searchByDisplayName — Retrieve fields by their display name. If a display name is defined for a field, the search will not use its identity name
  • POST /api/elasticubes/{server}/{cubeName}/cancelAllQueries — Cancel all queries
  • POST /api/elasticubes/{server}/{dataSourceId}/stopDataSourceId — Stop cube by dataSourceId name
  • POST /api/elasticubes/{server}/{instanceId}/startInstanceId — Start Cube
  • POST /api/elasticubes/{server}/{instanceId}/stopInstanceId — Stop cube ny instance id
  • POST /api/elasticubes/{server}/{title}/restart — Restart cube by cube name
  • POST /api/elasticubes/{server}/{title}/start — Start Cube
  • POST /api/elasticubes/{server}/{title}/stop — Stop cube by cube name
  • GET /api/elasticubes/servers/{server}/{title}/lastBuildTime
Last Updated: