"folder": null indicates the root workspace folder
GET /datamodels/{id}
{{baseURL}}/datamodels/{id}
The endpoint returns the full documentation of your model: every configuration of every tool present on the canvas including custom annotations. The response looks like this:
That model looks like this on the canvas. As you can see, the response is equivalent to a JSON-based representation of the model. You can use this endpoint for documentation without having to write and update documentation or for testing purposes (for instance by tracking Combine, Stack or Filter input vs. output dataset)
GET /{assetType}/{id}/execute
{{baseURL}}/{assetType}/{ID}/execution
Get connection ID from the GET /connections endpoint. Run/updates the connection.
AssetType is either connections or datamodels whereby your URL could look like this for a connection:
test.less.tech/api/public/connections/54/execute
Returns a job status message on in which you can see that the container_status (i.e. job status) is set to Pending whereby it is added to your job queue:
Check the status of a job. Can for instance be used to create your own orchestration workflows.
{task_id} refers to the id returned in the GET /{assetType}/{id}/execute response. With the example from above the URL would be structured like this:
{{baseURL}}/connections/status/1206
It returns the status of a specific job at the time of calling the endpoint. In other words, it is an asynchronous call (no promise structure while the asset runs/updates). The response looks identical to the previous call:
Note that as the asset runs/updates, the container_status and the run_code will change. The container_status can be either: pending (in queue), running (updating) or stopped (finished). The run_code can either by 200 (success) or 500 (error).
