Properties
| Name | Type | Description |
|---|---|---|
| id | string | The unique identifier for the job. |
| mode | string | The mode of the job. |
| type | string | The type of the job. |
| status | integer | The status code of the job. 0 = Active/Queued, 1 = Complete, 2 = Cancelled. |
| progress | integer | The progress of the job as a percentage. |
| createdAt | string | The date and time the job was created. |
| startedAt | string | The date and time the job started running. |
| endedAt | string | The date and time the job finished. |
| finishCode | integer | The completion code. 0 = success, 1 = error, 2 = cancelled. |
| title | string | A description of what the job is doing. |
| subtitle | string | Additional detail about the job. |
| statusNotes | object | |
| extractRefreshJob | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "Job",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "The unique identifier for the job."
},
"mode": {
"type": "string",
"description": "The mode of the job."
},
"type": {
"type": "string",
"description": "The type of the job."
},
"status": {
"type": "integer",
"description": "The status code of the job. 0 = Active/Queued, 1 = Complete, 2 = Cancelled."
},
"progress": {
"type": "integer",
"description": "The progress of the job as a percentage."
},
"createdAt": {
"type": "string",
"description": "The date and time the job was created."
},
"startedAt": {
"type": "string",
"description": "The date and time the job started running."
},
"endedAt": {
"type": "string",
"description": "The date and time the job finished."
},
"finishCode": {
"type": "integer",
"description": "The completion code. 0 = success, 1 = error, 2 = cancelled."
},
"title": {
"type": "string",
"description": "A description of what the job is doing."
},
"subtitle": {
"type": "string",
"description": "Additional detail about the job."
},
"statusNotes": {
"type": "object"
},
"extractRefreshJob": {
"type": "object"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/tableau-rest-job"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.