curl --request GET \
--url https://studio.edgeimpulse.com/v1/api/organizations/{organizationId}/whitelabel/organizations/{innerOrganizationId}/jobs \
--header 'x-api-key: <api-key>'{
"success": true,
"jobs": [
{
"id": 123,
"category": "<string>",
"categoryKey": "<string>",
"key": "<string>",
"created": "2023-11-07T05:31:56Z",
"jobNotificationUids": [
123
],
"started": "2023-11-07T05:31:56Z",
"finished": "2023-11-07T05:31:56Z",
"finishedSuccessful": true,
"additionalInfo": "<string>",
"computeTime": 123,
"createdByUser": {
"id": 123,
"name": "<string>",
"username": "<string>",
"photo": "<string>"
},
"categoryCount": 123,
"metadata": {}
}
],
"totalJobCount": 123,
"error": "<string>"
}White label admin only API to get the list of all jobs for a organization.
curl --request GET \
--url https://studio.edgeimpulse.com/v1/api/organizations/{organizationId}/whitelabel/organizations/{innerOrganizationId}/jobs \
--header 'x-api-key: <api-key>'{
"success": true,
"jobs": [
{
"id": 123,
"category": "<string>",
"categoryKey": "<string>",
"key": "<string>",
"created": "2023-11-07T05:31:56Z",
"jobNotificationUids": [
123
],
"started": "2023-11-07T05:31:56Z",
"finished": "2023-11-07T05:31:56Z",
"finishedSuccessful": true,
"additionalInfo": "<string>",
"computeTime": 123,
"createdByUser": {
"id": 123,
"name": "<string>",
"username": "<string>",
"photo": "<string>"
},
"categoryCount": 123,
"metadata": {}
}
],
"totalJobCount": 123,
"error": "<string>"
}Organization ID
Organization ID within the context of a white label
Maximum number of results
Offset in results, can be used in conjunction with LimitResultsParameter to implement paging.
OK
Whether the operation succeeded
Active jobs
Show child attributes
Job id, use this to refer back to the job. The web socket API also uses this ID.
User-friendly category (e.g. "Training model")
Machine-readable category (e.g. "learn-train-studio-wrapper")
External job identifier, this can be used to categorize jobs, and recover job status. E.g. set this to 'keras-192' for a Keras learning block with ID 192. When a user refreshes the page you can check whether a job is active for this ID and re-attach.
When the job was created.
The IDs of users who should be notified when a job is finished.
When the job was started.
When the job was finished.
Whether the job finished successfully.
Additional metadata associated with this job.
Job duration time in seconds from start to finished, measured by k8s job watcher.
Some job categories keep a counter on the job number, e.g. in synthetic data, so we know what the 1st, 2nd etc. job was in the UI.
Structured job metadata
Optional error description (set if 'success' was false)
Was this page helpful?