For endpoints that require a model ID (model_id), you can retrieve it in our app directly from the model URL.
Our model URLs follow the format below:
https://app.kondado.com.br/models/:model_id
Get Model Status
Description
Returns the status of a given model using its model_id.
Method
GET
Endpoint
/models/:model_id/status
URL Parameters
None
Example Response
{
"success": true,
"data": {
"162": {
"status": "active",
"is_running": false,
"is_active": true,
"kubo_status_type": "operational"
}
}
}
Response Description
The response will be a JSON object where the model ID is used as the key of a nested JSON object containing the fields described below.
status
Status description. Possible values are:
- running: The model is currently running.
- scheduled: The model is queued for execution.
- active: The model is not running and not queued, but is active.
- not_active: The model is not running, not queued, and is disabled.
raw_msg
If the model encounters any issues, this field will contain the error description (for example, if we are unable to connect to your source or destination).
kubo_status_type
Describes the current state of the model. Possible values are:
- not_published: The model is in draft mode.
- rebuilding: The model was recently changed and has not yet been executed with its new configuration.
- operational: The model is stable — it is not in draft mode and all changes have already been executed.
is_running
Boolean indicating whether the Pipeline is currently running (status = running).
is_active
Boolean indicating whether the Pipeline is active (status = active) or disabled (status = not_active).
Check a Model's Execution and Operational Status
Use the Kondado API to retrieve the current status and health of any model by its model_id.
Locate the model_id
Open the model in the Kondado app and copy the ID from the URL, which follows the format https://app.kondado.com.br/models/:model_id. You can also explore the Kondado platform to manage your pipelines.
Call the status endpoint
Make a GET request to /models/:model_id/status. No URL parameters are required.
Interpret the status field
Check the status value: running means execution is in progress; scheduled means queued; active means idle but enabled; not_active means disabled.
Review kubo_status_type
Verify kubo_status_type to confirm operational health: not_published (draft), rebuilding (pending first run with new config), or operational (stable and executed).
Check error details if needed
If issues exist, read raw_msg for the error description—commonly connection problems to your source or destination. Learn more about data integration to troubleshoot connectivity.
Validate booleans
Use is_running and is_active as quick boolean checks to confirm whether the pipeline is currently executing or enabled.