Skip to main content

API Changelog

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

2026-09-17 Email Template API

  • The variable_parameters.language request field of POST /v1/email-template/templates:replace and POST /v1/email-template/templates:replaceAsync is no longer restricted to de and en

2026-09-16 Entity API

  • GET /v1/entity:autocomplete now accepts an optional from query parameter

2026-09-16 File API

  • GET /v1/files/public/{id}/preview now accepts an optional keep_original query parameter

2026-09-16 Workflows Execution API

  • Task conditions can now be evaluated against the trigger that started the workflow: tasks[].conditions[].statements[].source.origin_type returns the new trigger_source value, and tasks gained a new optional automation_config.input_context.trigger_id naming that trigger โ€” accepted on POST /v2/flows/executions, POST /v2/flows/executions/{execution_id}/tasks, and PATCH /v2/flows/executions/{execution_id}/tasks/{task_id} and returned wherever flow executions are read
  • Flow executions now report the triggers set up for them through a new optional configured_triggers, and the trigger that started an execution can be named through a new optional trigger.trigger_id โ€” accepted on POST /v2/flows/executions and returned wherever flow executions are read

2026-09-15 Automation API

  • Automation flows can now be triggered by Event Catalog events: a new event catalog trigger shape is accepted on POST /v1/automation/flows and PUT /v1/automation/flows/{flow_id} and returned wherever flows are read, GET /v1/automation/flows accepts a new optional trigger_event_name query parameter for finding the flows a catalog event triggers, and executions report the catalog event as their trigger_event โ€” so consumers must be prepared for these additional trigger and trigger event shapes
  • Conditions can now be evaluated against the event that started the automation: conditions[].statements[].source.originType accepts and returns the new event value
  • Automations can now loop over the files uploaded in a journey: loops[].source_type accepts and returns the new journey-file-upload value, together with a new optional loops[].filter_tags for narrowing which files are looped over

2026-09-15 Entity API

  • Schema conditions no longer carry values; which values a condition matches is now described by a new optional options instead โ€” affecting PUT /v1/entity/schemas/{slug} and everywhere schemas are read (breaking)
  • Capabilities can now declare which fields they manage through a new optional managed_fields field โ€” accepted on POST /v1/entity/schemas/capabilities, PUT /v1/entity/schemas/capabilities/{composite_id}, and PUT /v1/entity/schemas/{slug}, and returned wherever schemas and capabilities are read
  • New optional ui_config.custom_tabs field added to entity schemas, accepted on PUT /v1/entity/schemas/{slug} and returned by the schema read, list and versions endpoints

2026-09-15 Pricing API

  • Line items can now carry the inputs an external fee was calculated from, through a new optional external_fees_metadata.inputs field on a line item and on its item components โ€” accepted on POST /v1/order, PUT /v1/order/{id}, POST /v1/pricing:compute, and POST /v1/public/cart:checkout
  • POST /v1/public/integration/{integrationId}/compute-price now accepts an optional city for the address the price is computed for, and reports the inputs the computation was based on

2026-09-15 User API

  • The language request field of POST /v2/users/invite, POST /v2/users/invite:resendEmail, and POST /v2/users/public/signup is no longer restricted to de and en
  • GET /v2/users/public/checkToken now reports which login methods are available through a new optional login_methods field

2026-09-15 Workflows Definition API

  • Task conditions can now be evaluated against the trigger that started the workflow: tasks[].conditions[].statements[].source.origin_type accepts and returns the new trigger_source value, and tasks gained a new optional automation_config.input_context.trigger_id naming that trigger โ€” accepted on POST /v2/flows/templates and PUT /v2/flows/templates/{flowId} and returned wherever flow templates are read

2026-09-15 Asset Entity

  • New _purpose attribute added to the asset entity, carrying the list of purpose ids an asset is assigned to

2026-09-14 AI Agents API

  • Agents can now be made available on a website: availability accepts the new website value, together with a new optional domain naming the website the agent answers on โ€” both accepted on POST /v1/agents and PUT /v1/agents/{agent_id} and returned wherever agents are read, and website is also accepted by the availability query parameter of GET /v1/agents
  • PUT /v1/agents/{agent_id} can now respond with 404 when the agent does not exist and 409 when the update conflicts with the current state

2026-09-14 App API

  • PATCH /v1/app/{appId} can now respond with 400 when the request cannot be processed

2026-09-14 Blueprint Manifest API

  • Blueprint validation was removed: POST /v2/blueprint-manifest/blueprints/{blueprint_id}/validate was removed after deprecation, POST /v2/blueprint-manifest/blueprints/{blueprint_id}:export no longer accepts the validate request field, and the validate job type is no longer returned by GET /v2/blueprint-manifest/jobs, GET /v2/blueprint-manifest/jobs/{job_id}, and POST /v2/blueprint-manifest/jobs/{job_id}:cancel (breaking)

2026-09-14 Workflows Definition API

  • Journey tasks can now have their journey prefilled by AI, through a new optional journey.ai_prefill field โ€” available on the regular, ECP, and installer journey configuration of a task, accepted on POST/PUT /v1/workflows/definitions, POST /v2/flows/templates, and PUT /v2/flows/templates/{flowId}, and returned wherever workflow definitions and flow templates are read
  • Flow templates gained new optional stages for grouping their tasks into stages, portal_titles for the titles shown in the customer portal, stages[].portal_descriptions for the descriptions shown there, and edges[].end_type โ€” accepted on POST /v2/flows/templates and PUT /v2/flows/templates/{flowId} and returned wherever flow templates are read
  • Journey tasks can now set the label shown on their portal button, through a new optional journey.portal_button_label field โ€” available on the regular, ECP, and installer journey configuration of a task, accepted on POST/PUT /v1/workflows/definitions, POST /v2/flows/templates, and PUT /v2/flows/templates/{flowId}, and returned wherever workflow definitions and flow templates are read

2026-09-14 Workflows Execution API

  • Journey tasks can now have their journey prefilled by AI, through a new optional journey.ai_prefill field โ€” available on the regular, ECP, and installer journey configuration of a task, accepted on PATCH /v2/flows/executions/{execution_id}/tasks/{task_id} and returned wherever workflow and flow executions are read, together with a new optional journey_prefill on the task itself
  • Flow executions gained new optional stages for grouping their tasks into stages, with each task reporting the stage it belongs to through a new optional stage_id, and a new optional edges[].end_type โ€” returned wherever flow executions are read
  • Flow executions and their stages now report the titles and descriptions shown in the customer portal through new optional portal_titles, stages[].portal_names, and stages[].portal_descriptions fields โ€” returned wherever flow executions are read, including POST /v2/flows/executions:portal-search and POST /v2/flows/executions:portal-search-batch
  • Journey tasks now carry the label shown on their portal button, through a new optional journey.portal_button_label field โ€” available on the regular, ECP, and installer journey configuration of a task, accepted on PATCH /v2/flows/executions/{execution_id}/tasks/{task_id} and returned wherever workflow and flow executions are read

2026-09-11 Automation API

  • Automation assignment actions can now pick an assignee by skill: new optional config.match_user_skills, config.required_skill_categories, and config.skill_match_mode fields โ€” accepted on POST /v1/automation/flows and PUT /v1/automation/flows/{flow_id} and returned wherever flows and executions are read

2026-09-11 Dashboard API

  • New GET /v1/dashboard/dashboards/quota endpoint added for reading the dashboard quota of an organization
  • POST /v1/dashboard/dashboards, PATCH /v1/dashboard/dashboards/{id}, and PUT /v1/dashboard/dashboards/{id} can now respond with 403

2026-09-11 Environments API

  • Environments can now hold a list of values: the type of an environment accepts the new List value with a matching value shape, and the type of the entries is reported through a new optional item_type โ€” accepted on POST /v1/environments and PUT /v1/environments/{key} and returned wherever environments are read

2026-09-11 Workflows Execution API

  • POST /v2/flows/executions can now respond with 503 when a workflow execution cannot be started at the moment

2026-09-10 Access Token API

  • Access tokens can now identify a contact: POST /v1/access-tokens accepts a new set of contact identification parameters, the new contact_identification value is returned as token_type wherever access tokens are read and accepted by the token_type query parameter of GET /v1/access-tokens, and such tokens report new optional contact_id and allowed_operations fields
  • New GET /v1/access-tokens/contact-identification/.well-known/jwks.json and GET /v1/access-tokens/contact-identification/.well-known/openid-configuration endpoints added for verifying contact identification tokens

2026-09-10 App API

  • 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

2026-09-10 Event Catalog API

  • 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
  • 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}
  • PATCH /v1/events/{event_name} accepts new optional enabled, auto_trigger, and success_criteria fields, and its request body must now be an object (breaking)

2026-09-10 Integration Toolkit API

  • 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 (breaking)
  • 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

2026-09-09 AI Agents API

  • 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

2026-09-09 Configuration Hub API

  • 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