Computed Tables API

Programmatic access to Computed Tables uses the generic Container endpoints on the Qualytics REST API. The requests below cover creation, update, deletion, validation, and history. Requests share the same base URL and Bearer token authentication as the rest of the platform API.

• Base URL. Your deployment's platform host (for example, https://<your-tenant>.qualytics.io/api).
• Auth. Bearer token in the Authorization header. See Access Tokens to create one.

Payload Shape

The Computed Table is a specialization of the generic Container payload. Common fields:

Create

Endpoint: POST /containers

Permission: Editor team permission on the datastore, or Author creating a Computed Table they will own.

curl -X POST "https://<your-tenant>.qualytics.io/api/containers" \
  -H "Authorization: Bearer $QUALYTICS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "container_type": "computed_table",
    "datastore_id": 12,
    "name": "customer_order_statistics",
    "query": "SELECT o.customer_id, COUNT(*) AS order_count, SUM(o.total) AS total_amount FROM public.orders o WHERE o.status = '\''placed'\'' GROUP BY o.customer_id",
    "description": "Order counts and totals per customer for placed orders.",
    "owner_id": 42
  }'

Returns the created Container object with its assigned id. Qualytics runs a basic profile that samples up to 1000 records per partition immediately after save.

Update

Endpoint: PUT /containers/{id}

Permission: Editor team permission on the datastore, or Author owner of the Computed Table.

curl -X PUT "https://<your-tenant>.qualytics.io/api/containers/34" \
  -H "Authorization: Bearer $QUALYTICS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "container_type": "computed_table",
    "name": "customer_order_statistics",
    "query": "SELECT o.customer_id, COUNT(*) AS order_count, SUM(o.total) AS total_amount FROM public.orders o WHERE o.status = '\''placed'\'' AND o.year = 2026 GROUP BY o.customer_id",
    "description": "Order counts and totals per customer for placed orders in the current year.",
    "owner_id": 42
  }'

The datastore_id cannot be changed. Changing owner_id (reassigning ownership) requires the Editor team permission; Authors can edit Computed Tables they own but cannot reassign them.

If the new query drops a field that has attached quality checks or anomalies, the update returns 409 Conflict with a dropped_fields payload. Add force_drop_fields: true to the body to save anyway; the affected fields are marked as missing while their checks and anomalies are preserved.

Editing the query causes Qualytics to re-profile the Computed Table immediately after save: a synchronous slim profile refreshes field statistics right away, and a full asynchronous profile follows.

Delete

Endpoint: DELETE /containers/{id}

Permission: Editor team permission on the datastore, or Author owner of the Computed Table.

curl -X DELETE "https://<your-tenant>.qualytics.io/api/containers/34" \
  -H "Authorization: Bearer $QUALYTICS_TOKEN"

Returns 204 No Content on success. The container, its quality checks, anomalies, profile history, and scan history are removed. The delete is blocked with 409 Conflict when quality checks in other containers reference this Computed Table (for example, an existsIn or dataDiff check pointing at it); delete or repoint those checks first.

Validate a Query Before Save

Endpoint: POST /containers/validate

Permission: Editor team permission on the datastore, or Author when the caller will be the owner of the Computed Table (Hybrid Gate). Validate uses the same permission check as Create in the controlplane.

Validates the SQL without persisting anything. The request body carries the same payload you would send to Create or Update, wrapped in a container object:

curl -X POST "https://<your-tenant>.qualytics.io/api/containers/validate" \
  -H "Authorization: Bearer $QUALYTICS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "container": {
      "container_type": "computed_table",
      "datastore_id": 12,
      "name": "customer_order_statistics",
      "query": "SELECT o.customer_id, COUNT(*) AS order_count FROM public.orders o GROUP BY o.customer_id"
    }
  }'

Returns 204 No Content on success. On failure, the response body carries a detail field with the underlying error message from the warehouse.

History

Endpoint: GET /containers/{id}/history

Permission: Reporter team permission on the datastore or above.

Returns the version history for the container, including the query text and metadata as they were at each revision. Use this to review previous versions of the SQL or attribute changes to specific users.

Read

Endpoint: GET /containers/{id} for a single container, GET /containers?container_type=computed_table&datastore={id} to list Computed Tables inside a datastore.

Permission: Reporter team permission on the datastore or above.

Error Responses