API Changelog
Breaking changes, new features, and significant updates to epilot APIs. Subscribe via RSS
2026-09-09 File API
- New
POST /v1/files/validationsendpoint added for validating a file
2026-09-09 Journey Config API
- New endpoints added for publishing a journey configuration and working with its revisions:
POST /v1/journey/configuration/{id}/publishfor publishing it,GET /v1/journey/configuration/{id}/publish-statefor reading whether it is published,GETandPOST /v1/journey/configuration/{id}/revisionsfor listing and creating revisions, andGET /v1/journey/configuration/{id}/revisions/{revision_id}for reading a single revision - A specific revision can now be read through the journey configuration itself:
GET /v1/journey/configuration/{id}accepts a new optionalrevision_idquery parameter and reports which revision was served, andPOST /v1/journey/configuration/{id}/revisionsaccepts an optionalrevision_name
2026-09-08 App API
- Apps can now ship an external values component: a new
ExternalValuesComponentshape is accepted onPOST/PATCH /v1/app-configurations/{appId}/versions/{version}/componentsand returned wherever apps, app configurations, and components are read, so consumers must be prepared for this additional component shape;GET /v1/appaccepts the matchingEXTERNAL_VALUESvalue for itscomponentTypequery parameter, and app events accept and report it as asource
2026-09-08 Environments API
- Environments can now hold a link: the
typeof an environment accepts the newLinkvalue with a matchingvalueshape โ accepted onPOST /v1/environmentsandPUT /v1/environments/{key}and returned wherever environments are read
2026-09-08 Integration Toolkit API
- Entity mappings can now be applied conditionally through a new optional
configuration.entities[].conditionalfield โ accepted when creating or updating a use case or an integration as well as byPOST /v1/erp/updates/direct_simulationand the mapping simulation endpoints, and returned wherever use cases and integrations are read - Import validation now reports what it looked at and what went wrong in more detail: new optional
validation.entity_details,validation.entity_details_truncated, andvalidation.issues[].subjectfields, together with the new issue codesSCHEMA_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, andVARIANT_VALUE_CONFLICTโ returned by all/v2/erp/importsendpoints, wherevalidation.total_rowsis no longer always present (breaking)
2026-09-08 Validation Rules API
- New
DocumentRuleTypevalidation rule type added โ accepted onPOST /v1/validation-rulesandPATCH /v1/validation-rules/{ruleId}and returned wherever rules are read, so consumers must be prepared for this additional rule shape
2026-09-08 Workflows Definition API
- Workflow tasks can now be broken down into subtasks: new optional
subtasksandrequiredfields on flow template tasks, together with an optionaltrigger_modeofautomaticormanualโ accepted onPOST /v2/flows/templatesandPUT /v2/flows/templates/{flowId}and returned wherever flow templates are read - Journey tasks can now require the journey to be submitted before the task completes, through a new optional
journey.journey_submission_requiredfield โ available on the regular, ECP, and installer journey configuration of a task, accepted onPOST/PUT /v1/workflows/definitionsandPOST/PUT /v2/flows/templates, and returned wherever workflow definitions and flow templates are read - New optional
on_failurefield added to flow template tasks, controlling what happens when a task fails
2026-09-08 Workflows Execution API
- Running workflows now report the new task configuration: optional
subtasks,subtask_states,required,trigger_mode, andon_failureon a task, plusjourney.journey_submission_requiredon 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 acceptssubtask_statesand the ECP and installerjourney.journey_submission_required - Tasks that wait for a journey report new optional
journey_submission,journey_gate_waived_at, andcompletion_gates_reset_atfields, and agent tasks a new optionalagent_execution.completion_hold
2026-09-07 Integration Google Maps API
GET /v1/geocode-api/coordinatesnow accepts an optionalcountryquery parameter for restricting the lookup to a single country
2026-09-04 Metering API
POST /v2/metering/readings/prunecan now respond with413when the prune request is too large to be processed
2026-09-03 Email Settings API
- New
AllowedRecipientDomainsSettingemail setting type added, restricting which recipient domains may be sent to โ accepted onPOST /v1/email-settings,POST /v1/email-settings/{id}, andDELETE /v1/email-settings, and returned wherever email settings are read, so consumers must be prepared for this additional setting shape
2026-09-03 Validation Rules API
- Rule condition values can now reference an environment value instead of only a fixed value:
conditions[].value, itsminandmax, theiradjust.value, andapplies_when.valueaccept an environment value, andconditions[].value,min, andmaxadditionally accept an external value โ accepted onPOST /v1/validation-rulesandPATCH /v1/validation-rules/{ruleId}and returned wherever rules are read, so consumers must be prepared for these additional shapes
2026-09-03 Core Events
- New optional
_automation_chainfield 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
2026-09-02 Automation API
- Automation assignment actions can now spread work across a group of candidates:
config.assignment_typeaccepts the newsequentialandeven_distributionvalues, together with new optionalconfig.candidate_group,config.fallback,config.fallback_assignees, andconfig.reset_intervalfields โ accepted onPOST /v1/automation/flowsandPUT /v1/automation/flows/{flow_id}and returned wherever flows and executions are read - Assignment actions additionally accept a new optional
config.workload_filterfor narrowing which existing workload is counted when picking an assignee
2026-09-02 Integration Toolkit API
- Integrations can now carry a new optional
mapsfield, accepted onPOST/PUT /v1/integrations/{integrationId}and their v2 counterparts and returned wherever integrations are read
2026-09-01 Automation API
- The
language_codefield of an automation action's configuration is no longer restricted todeandenโ affectingPOST /v1/automation/flowsandPUT /v1/automation/flows/{flow_id}as well as everywhere flows and executions are read - Automation actions can now be pointed at entities through an entity graph: a new optional
config.graph_contextfield describing the graph and its nodes, where every node can be markedoptionalโ accepted onPOST /v1/automation/flowsandPUT /v1/automation/flows/{flow_id}and returned wherever flows and executions are read
2026-09-01 File API
- The file upload endpoints (
POST /v1/files,POST /v1/files/upload,POST /v1/files/public/upload,POST /v2/files, andPOST /v2/files/upload) can now respond with422when the upload cannot be processed
2026-09-01 Integration Toolkit API
- The entity sync status endpoint moved from
GET /v1/entities/{entityId}/sync-statustoGET /v1/integrations/entities/{entityId}/sync-status; the old path was removed without deprecation (breaking)
2026-09-01 Journey Config API
- New
GET /v1/journey/configuration/{id}/environmentendpoint added for reading the environment of a journey configuration - New
GET /v1/journey/environment-variablesendpoint added for listing the environment variables available to journeys - The
settings.embedOptions.langfield is no longer restricted tode,en, andfrโ affecting the journey configuration create and update endpoints in v1 and v2
2026-09-01 Partner Directory API
- The
languagerequest field ofPOST /v2/partners/{id}/inviteandPOST /v2/partners/{orgId}/usersis no longer restricted todeanden
2026-09-01 Meter Counter Entity
- New
ma_lo_idattribute added to themeter_counterentity, carrying the Marktlokation ID of a register
2026-08-31 Blueprint Manifest API
POST /v2/blueprint-manifest/jobs/{job_id}:continueno longer accepts theresources_to_ignoreandsync_notesrequest fields; the request body now takes the same installation options as the install endpoints (breaking)- Blueprint installations can now ask for a fresh authentication: jobs report a new
REAUTH_REQUIREDstatus wherever jobs and manifests are read, andPOST /v3/blueprint-manifest/blueprint:installaccepts a new optionalsession_credentialsfield - The
languagerequest field ofPOST /v1/blueprint-manifest/jobs/{job_id}:exportManifestis no longer restricted todeanden
2026-08-31 Environments API
- Environment values are no longer text-only: the
typeof an environment accepts the newText,Number,Boolean,Map, andJSONvalues, and itsvalueis no longer always a string but takes the shape matching the type โ affectingPOST /v1/environmentsandPUT /v1/environments/{key}as well as everywhere environments are read (breaking) PUT /v1/environments/{key}can now respond with409when the environment conflicts with the current state
2026-08-28 App API
- App hooks can now run yearly: the
intervalsof a component's hook configuration accept the newP1Yvalue, accepted onPOST/PATCH /v1/app-configurations/{appId}/versions/{version}/componentsand returned wherever apps and app configurations are read
2026-08-28 Automation API
- Automation flows can now be triggered by relation changes: trigger operation types accept the new
relationsAdded,relationsRemoved,relationsDeleted,relationsSoftDeleted, andrelationsRestoredvalues onPOST /v1/automation/flowsandPUT /v1/automation/flows/{flow_id}, and executions report them intrigger_event.operation_type - Automation actions can now wait for a journey submission through new optional
config.journey_idandconfig.wait_for_journey_submissionfields, accepted when creating or updating a flow and returned wherever flows and executions are read; a waiting execution additionally reports aworkflow_wait_context - Executions started from a workflow now report who triggered it through a new optional
workflow_context.trigger_user_idfield, accepted onPOST /v1/automation/executionsand returned wherever executions are read