Skip to main content
All v1 routes are under /api/public/v1. Responses are JSON meant for integrations: clear field names and no connection secrets or raw connector configuration. What you can call (each line is implemented; see OpenAPI for request/response shapes)
  • Assets: GET .../assets — paginated list; GET .../assets/{assetId} — curated metadata for one asset (including type: human-readable asset type, e.g. Model, Source).
  • Models: GET .../assets/{assetId}/model — published version (same detail as .../versions/{versionId}, or null); .../model/versions — version list (summaries); .../model/versions/{versionId} — one version’s full detail (model assets only; others get 404 on these paths).
  • Runs: POST .../assets/{assetId}/execute — queue a run for a source, model, or orchestration.
  • Jobs: GET .../jobs/{jobId} — status and timing for a job (only if you can read its asset).
API authentication covers bearer tokens and choosing your workspace base URL.

​
Using the playground on each endpoint

Endpoint pages include Mintlify’s Try it panel when the page is wired to the OpenAPI file (see Mintlify API playground). Open an endpoint, set Authorization to your API token, set the server to your workspace URL, then send the request. On small screens you may need to scroll or expand a panel to see it.