API Changelog
Breaking changes, new features, and significant updates to epilot APIs. Subscribe via RSS
2026-09-17 Email Template API
- The
variable_parameters.languagerequest field ofPOST /v1/email-template/templates:replaceandPOST /v1/email-template/templates:replaceAsyncis no longer restricted todeanden
2026-09-16 Entity API
GET /v1/entity:autocompletenow accepts an optionalfromquery parameter
2026-09-16 File API
GET /v1/files/public/{id}/previewnow accepts an optionalkeep_originalquery 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_typereturns the newtrigger_sourcevalue, and tasks gained a new optionalautomation_config.input_context.trigger_idnaming that trigger โ accepted onPOST /v2/flows/executions,POST /v2/flows/executions/{execution_id}/tasks, andPATCH /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 optionaltrigger.trigger_idโ accepted onPOST /v2/flows/executionsand 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/flowsandPUT /v1/automation/flows/{flow_id}and returned wherever flows are read,GET /v1/automation/flowsaccepts a new optionaltrigger_event_namequery parameter for finding the flows a catalog event triggers, and executions report the catalog event as theirtrigger_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.originTypeaccepts and returns the neweventvalue - Automations can now loop over the files uploaded in a journey:
loops[].source_typeaccepts and returns the newjourney-file-uploadvalue, together with a new optionalloops[].filter_tagsfor 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 optionaloptionsinstead โ affectingPUT /v1/entity/schemas/{slug}and everywhere schemas are read (breaking) - Capabilities can now declare which fields they manage through a new optional
managed_fieldsfield โ accepted onPOST /v1/entity/schemas/capabilities,PUT /v1/entity/schemas/capabilities/{composite_id}, andPUT /v1/entity/schemas/{slug}, and returned wherever schemas and capabilities are read - New optional
ui_config.custom_tabsfield added to entity schemas, accepted onPUT /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.inputsfield on a line item and on its item components โ accepted onPOST /v1/order,PUT /v1/order/{id},POST /v1/pricing:compute, andPOST /v1/public/cart:checkout POST /v1/public/integration/{integrationId}/compute-pricenow accepts an optionalcityfor the address the price is computed for, and reports theinputsthe computation was based on
2026-09-15 User API
- The
languagerequest field ofPOST /v2/users/invite,POST /v2/users/invite:resendEmail, andPOST /v2/users/public/signupis no longer restricted todeanden GET /v2/users/public/checkTokennow reports which login methods are available through a new optionallogin_methodsfield
2026-09-15 Workflows Definition API
- Task conditions can now be evaluated against the trigger that started the workflow:
tasks[].conditions[].statements[].source.origin_typeaccepts and returns the newtrigger_sourcevalue, and tasks gained a new optionalautomation_config.input_context.trigger_idnaming that trigger โ accepted onPOST /v2/flows/templatesandPUT /v2/flows/templates/{flowId}and returned wherever flow templates are read
2026-09-15 Asset Entity
- New
_purposeattribute added to theassetentity, 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:
availabilityaccepts the newwebsitevalue, together with a new optionaldomainnaming the website the agent answers on โ both accepted onPOST /v1/agentsandPUT /v1/agents/{agent_id}and returned wherever agents are read, andwebsiteis also accepted by theavailabilityquery parameter ofGET /v1/agents PUT /v1/agents/{agent_id}can now respond with404when the agent does not exist and409when the update conflicts with the current state
2026-09-14 App API
PATCH /v1/app/{appId}can now respond with400when the request cannot be processed
2026-09-14 Blueprint Manifest API
- Blueprint validation was removed:
POST /v2/blueprint-manifest/blueprints/{blueprint_id}/validatewas removed after deprecation,POST /v2/blueprint-manifest/blueprints/{blueprint_id}:exportno longer accepts thevalidaterequest field, and thevalidatejob type is no longer returned byGET /v2/blueprint-manifest/jobs,GET /v2/blueprint-manifest/jobs/{job_id}, andPOST /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_prefillfield โ available on the regular, ECP, and installer journey configuration of a task, accepted onPOST/PUT /v1/workflows/definitions,POST /v2/flows/templates, andPUT /v2/flows/templates/{flowId}, and returned wherever workflow definitions and flow templates are read - Flow templates gained new optional
stagesfor grouping their tasks into stages,portal_titlesfor the titles shown in the customer portal,stages[].portal_descriptionsfor the descriptions shown there, andedges[].end_typeโ accepted onPOST /v2/flows/templatesandPUT /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_labelfield โ available on the regular, ECP, and installer journey configuration of a task, accepted onPOST/PUT /v1/workflows/definitions,POST /v2/flows/templates, andPUT /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_prefillfield โ available on the regular, ECP, and installer journey configuration of a task, accepted onPATCH /v2/flows/executions/{execution_id}/tasks/{task_id}and returned wherever workflow and flow executions are read, together with a new optionaljourney_prefillon the task itself - Flow executions gained new optional
stagesfor grouping their tasks into stages, with each task reporting the stage it belongs to through a new optionalstage_id, and a new optionaledges[].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, andstages[].portal_descriptionsfields โ returned wherever flow executions are read, includingPOST /v2/flows/executions:portal-searchandPOST /v2/flows/executions:portal-search-batch - Journey tasks now carry the label shown on their portal button, through a new optional
journey.portal_button_labelfield โ available on the regular, ECP, and installer journey configuration of a task, accepted onPATCH /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, andconfig.skill_match_modefields โ accepted onPOST /v1/automation/flowsandPUT /v1/automation/flows/{flow_id}and returned wherever flows and executions are read
2026-09-11 Dashboard API
- New
GET /v1/dashboard/dashboards/quotaendpoint added for reading the dashboard quota of an organization POST /v1/dashboard/dashboards,PATCH /v1/dashboard/dashboards/{id}, andPUT /v1/dashboard/dashboards/{id}can now respond with403
2026-09-11 Environments API
- Environments can now hold a list of values: the
typeof an environment accepts the newListvalue with a matchingvalueshape, and the type of the entries is reported through a new optionalitem_typeโ accepted onPOST /v1/environmentsandPUT /v1/environments/{key}and returned wherever environments are read
2026-09-11 Workflows Execution API
POST /v2/flows/executionscan now respond with503when 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-tokensaccepts a new set of contact identification parameters, the newcontact_identificationvalue is returned astoken_typewherever access tokens are read and accepted by thetoken_typequery parameter ofGET /v1/access-tokens, and such tokens report new optionalcontact_idandallowed_operationsfields - New
GET /v1/access-tokens/contact-identification/.well-known/jwks.jsonandGET /v1/access-tokens/contact-identification/.well-known/openid-configurationendpoints added for verifying contact identification tokens
2026-09-10 App API
- App hooks can now run on a custom interval: the
intervalsof a component's hook configuration accept the newcustomvalue, accepted onPOST/PATCH /v1/app-configurations/{appId}/versions/{version}/componentsand 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/eventsfor creating an event,PUT /v1/events/{event_name}for replacing it,DELETE /v1/events/{event_name}for removing it,POST /v1/events/{event_name}:previewfor previewing what it would produce, andPOST /v1/events/{event_name}:publishfor publishing it - Catalog events report new optional
api_trigger,event_origin,lineage,mapping, andentity_operation.purpose_filtersfields, andautomation_trigger_onlyandautomation_trigger_seed_nodeare no longer read-only โ returned byGET /v1/events,GET /v1/events/{event_name}, andPATCH /v1/events/{event_name} PATCH /v1/events/{event_name}accepts new optionalenabled,auto_trigger, andsuccess_criteriafields, and its request body must now be an object (breaking)
2026-09-10 Integration Toolkit API
- Monitoring events are no longer reported as
skipped: theirleveltakes the newinfovalue instead, accepted onPOST /v2/integrations/{integrationId}/monitoring/eventsand returned by the monitoring event, associated event, and trace endpoints (breaking) - Monitoring statistics follow the same move:
POST /v2/integrations/{integrationId}/monitoring/statsandPOST /v2/integrations/{integrationId}/monitoring/time-seriesnow report aninfo_countper bucket and breakdown, whileskipped_countis 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}/executeandPOST /v1/agents/{agent_id}/execute/streamaccept a new optionalinput.attachment
2026-09-09 Configuration Hub API
- Configuration health findings can now be ignored: new
POST /v1/configs/health:ignoreendpoint added, and an ignored finding is reported through new optionalfindings[].ignored,findings[].ignored_at,findings[].ignored_by, andfindings[].ignored_reasonfields onGET /v1/configs/health