Skip to main content

API Changelog

Breaking changes, new features, and significant updates to epilot APIs. Subscribe via RSS

Showing changes to all APIs. This includes APIs for specific platform features, which are not part of the core APIs integrations are built on and change more often. Show core APIs only

September 10, 2026

App API

Changed App hooks can now run on a custom interval: the intervals of a component's hook configuration accept the new custom value, accepted on POST/PATCH /v1/app-configurations/{appId}/versions/{version}/components and returned wherever apps and app configurations are read

Event Catalog API

Breaking PATCH /v1/events/{event_name} accepts new optional enabled, auto_trigger, and success_criteria fields, and its request body must now be an object

Changed Catalog events can now be managed through the API: new POST /v1/events for creating an event, PUT /v1/events/{event_name} for replacing it, DELETE /v1/events/{event_name} for removing it, POST /v1/events/{event_name}:preview for previewing what it would produce, and POST /v1/events/{event_name}:publish for publishing it

Changed Catalog events report new optional api_trigger, event_origin, lineage, mapping, and entity_operation.purpose_filters fields, and automation_trigger_only and automation_trigger_seed_node are no longer read-only โ€” returned by GET /v1/events, GET /v1/events/{event_name}, and PATCH /v1/events/{event_name}

Integration Toolkit API

Deprecated Monitoring statistics follow the same move: POST /v2/integrations/{integrationId}/monitoring/stats and POST /v2/integrations/{integrationId}/monitoring/time-series now report an info_count per bucket and breakdown, while skipped_count is deprecated and will be removed in a future version

Changed Monitoring events are no longer reported as skipped: their level takes the new info value instead, accepted on POST /v2/integrations/{integrationId}/monitoring/events and returned by the monitoring event, associated event, and trace endpoints

September 9, 2026

AI Agents API

Changed Agent executions can now take a file along: POST /v1/agents/{agent_id}/execute and POST /v1/agents/{agent_id}/execute/stream accept a new optional input.attachment

Configuration Hub API

Changed Configuration health findings can now be ignored: new POST /v1/configs/health:ignore endpoint added, and an ignored finding is reported through new optional findings[].ignored, findings[].ignored_at, findings[].ignored_by, and findings[].ignored_reason fields on GET /v1/configs/health

File API

New New POST /v1/files/validations endpoint added for validating a file

Journey Config API

New New endpoints added for publishing a journey configuration and working with its revisions: POST /v1/journey/configuration/{id}/publish for publishing it, GET /v1/journey/configuration/{id}/publish-state for reading whether it is published, GET and POST /v1/journey/configuration/{id}/revisions for listing and creating revisions, and GET /v1/journey/configuration/{id}/revisions/{revision_id} for reading a single revision

Changed A specific revision can now be read through the journey configuration itself: GET /v1/journey/configuration/{id} accepts a new optional revision_id query parameter and reports which revision was served, and POST /v1/journey/configuration/{id}/revisions accepts an optional revision_name

September 8, 2026

App API

Action needed Apps can now ship an external values component: a new ExternalValuesComponent shape is accepted on POST/PATCH /v1/app-configurations/{appId}/versions/{version}/components and returned wherever apps, app configurations, and components are read, so consumers must be prepared for this additional component shape; GET /v1/app accepts the matching EXTERNAL_VALUES value for its componentType query parameter, and app events accept and report it as a source

Environments API

Changed Environments can now hold a link: the type of an environment accepts the new Link value with a matching value shape โ€” accepted on POST /v1/environments and PUT /v1/environments/{key} and returned wherever environments are read

Integration Toolkit API

Breaking Import validation now reports what it looked at and what went wrong in more detail: new optional validation.entity_details, validation.entity_details_truncated, and validation.issues[].subject fields, together with the new issue codes SCHEMA_NOT_FOUND, SCHEMA_NOT_CONDITIONABLE, SCHEMA_DECLARES_NO_CONDITIONS, ATTRIBUTE_NOT_IN_SCHEMA, ATTRIBUTE_NOT_OVERRIDABLE, CONDITION_VALUE_MISSING, IS_CONDITIONAL_NOT_CONSTANT, GROUPING_KEY_NOT_A_COLUMN, GROUPING_KEY_IS_FOLD_COLUMN, TIER_BANDS_CONFLICT, TIER_ROWS_NOT_GROUPED, and VARIANT_VALUE_CONFLICT โ€” returned by all /v2/erp/imports endpoints, where validation.total_rows is no longer always present

Changed Entity mappings can now be applied conditionally through a new optional configuration.entities[].conditional field โ€” accepted when creating or updating a use case or an integration as well as by POST /v1/erp/updates/direct_simulation and the mapping simulation endpoints, and returned wherever use cases and integrations are read

Validation Rules API

Action needed New New DocumentRuleType validation rule type added โ€” accepted on POST /v1/validation-rules and PATCH /v1/validation-rules/{ruleId} and returned wherever rules are read, so consumers must be prepared for this additional rule shape

Workflows Definition API

New New optional on_failure field added to flow template tasks, controlling what happens when a task fails

Changed Workflow tasks can now be broken down into subtasks: new optional subtasks and required fields on flow template tasks, together with an optional trigger_mode of automatic or manual โ€” accepted on POST /v2/flows/templates and PUT /v2/flows/templates/{flowId} and returned wherever flow templates are read

Changed Journey tasks can now require the journey to be submitted before the task completes, through a new optional journey.journey_submission_required field โ€” available on the regular, ECP, and installer journey configuration of a task, accepted on POST/PUT /v1/workflows/definitions and POST/PUT /v2/flows/templates, and returned wherever workflow definitions and flow templates are read

Workflows Execution API

Changed Running workflows now report the new task configuration: optional subtasks, subtask_states, required, trigger_mode, and on_failure on a task, plus journey.journey_submission_required on the regular, ECP, and installer journey of a step or task โ€” returned wherever executions, steps, and tasks are read; PATCH /v2/flows/executions/{execution_id}/tasks/{task_id} additionally accepts subtask_states and the ECP and installer journey.journey_submission_required

Changed Tasks that wait for a journey report new optional journey_submission, journey_gate_waived_at, and completion_gates_reset_at fields, and agent tasks a new optional agent_execution.completion_hold

September 7, 2026

Integration Google Maps API

Changed GET /v1/geocode-api/coordinates now accepts an optional country query parameter for restricting the lookup to a single country

September 4, 2026

Metering API

Changed POST /v2/metering/readings/prune can now respond with 413 when the prune request is too large to be processed

September 3, 2026

Email Settings API

Action needed New New AllowedRecipientDomainsSetting email setting type added, restricting which recipient domains may be sent to โ€” accepted on POST /v1/email-settings, POST /v1/email-settings/{id}, and DELETE /v1/email-settings, and returned wherever email settings are read, so consumers must be prepared for this additional setting shape

Validation Rules API

Action needed Rule condition values can now reference an environment value instead of only a fixed value: conditions[].value, its min and max, their adjust.value, and applies_when.value accept an environment value, and conditions[].value, min, and max additionally accept an external value โ€” accepted on POST /v1/validation-rules and PATCH /v1/validation-rules/{ruleId} and returned wherever rules are read, so consumers must be prepared for these additional shapes

Core Events

New New optional _automation_chain field added to all built-in event payloads, listing the automations that led to the event (up to 100 entries) so consumers can detect and break automation loops; it can also be set when triggering an event through the Event Catalog API and is then carried over to the published event and to every event derived from the resulting entity operation

September 2, 2026

Automation API

Changed Automation assignment actions can now spread work across a group of candidates: config.assignment_type accepts the new sequential and even_distribution values, together with new optional config.candidate_group, config.fallback, config.fallback_assignees, and config.reset_interval fields โ€” accepted on POST /v1/automation/flows and PUT /v1/automation/flows/{flow_id} and returned wherever flows and executions are read

Changed Assignment actions additionally accept a new optional config.workload_filter for narrowing which existing workload is counted when picking an assignee

Integration Toolkit API

Changed Integrations can now carry a new optional maps field, accepted on POST/PUT /v1/integrations/{integrationId} and their v2 counterparts and returned wherever integrations are read

September 1, 2026

Automation API

Changed The language_code field of an automation action's configuration is no longer restricted to de and en โ€” affecting POST /v1/automation/flows and PUT /v1/automation/flows/{flow_id} as well as everywhere flows and executions are read

Changed Automation actions can now be pointed at entities through an entity graph: a new optional config.graph_context field describing the graph and its nodes, where every node can be marked optional โ€” accepted on POST /v1/automation/flows and PUT /v1/automation/flows/{flow_id} and returned wherever flows and executions are read

File API

Changed The file upload endpoints (POST /v1/files, POST /v1/files/upload, POST /v1/files/public/upload, POST /v2/files, and POST /v2/files/upload) can now respond with 422 when the upload cannot be processed

Integration Toolkit API

Changed The entity sync status endpoint moved from GET /v1/entities/{entityId}/sync-status to GET /v1/integrations/entities/{entityId}/sync-status; the old path was removed without deprecation

Journey Config API

New New GET /v1/journey/configuration/{id}/environment endpoint added for reading the environment of a journey configuration

New New GET /v1/journey/environment-variables endpoint added for listing the environment variables available to journeys

Changed The settings.embedOptions.lang field is no longer restricted to de, en, and fr โ€” affecting the journey configuration create and update endpoints in v1 and v2

Partner Directory API

Changed The language request field of POST /v2/partners/{id}/invite and POST /v2/partners/{orgId}/users is no longer restricted to de and en