Workday Integration · Schema
Integration Event
Represents an integration event record within the Workday Integrations system, tracking the execution status and details of integration runs.
EnterpriseERPFinanceHCMIntegrationPayroll
Properties
| Name | Type | Description |
|---|---|---|
| id | string | The unique Workday identifier for the integration event |
| descriptor | string | The display name of the integration event |
| integrationSystem | object | The integration system that was executed |
| status | string | The execution status of the integration |
| startDateTime | string | The date and time the integration started |
| endDateTime | stringnull | The date and time the integration completed |
| recordsProcessed | integer | The number of records successfully processed |
| recordsFailed | integer | The number of records that failed processing |
| initiatedBy | object | The user or system that initiated the integration |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://schemas.workday.com/integrationEvent",
"title": "Integration Event",
"description": "Represents an integration event record within the Workday Integrations system, tracking the execution status and details of integration runs.",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "The unique Workday identifier for the integration event"
},
"descriptor": {
"type": "string",
"description": "The display name of the integration event"
},
"integrationSystem": {
"$ref": "#/$defs/ResourceReference",
"description": "The integration system that was executed"
},
"status": {
"type": "string",
"enum": ["Completed", "Failed", "In_Progress", "Cancelled"],
"description": "The execution status of the integration"
},
"startDateTime": {
"type": "string",
"format": "date-time",
"description": "The date and time the integration started"
},
"endDateTime": {
"type": ["string", "null"],
"format": "date-time",
"description": "The date and time the integration completed"
},
"recordsProcessed": {
"type": "integer",
"description": "The number of records successfully processed"
},
"recordsFailed": {
"type": "integer",
"description": "The number of records that failed processing"
},
"initiatedBy": {
"$ref": "#/$defs/ResourceReference",
"description": "The user or system that initiated the integration"
}
},
"required": ["id", "integrationSystem", "status"],
"$defs": {
"ResourceReference": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"descriptor": {
"type": "string"
},
"href": {
"type": "string",
"format": "uri"
}
},
"required": ["id"]
}
}
}
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/workday-integration-integration-event"
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.