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

October 21, 2026

Kanban API

New Action needed Share boards through grants โ€” Kanban boards can be shared through structured grants. shared_with can now contain grant objects in addition to strings.

API details
  • shared_with items accept and return grant objects
  • A new optional shared_with_format query parameter on GET /v1/kanban/boards and GET, PATCH, and PUT /v1/kanban/board/{boardId} controls the returned format

New Organization-wide board access โ€” Boards can define access for the whole organization and report the caller's own access.

API details
  • New optional org_access field, accepted when creating or updating a board
  • New optional my_access field wherever boards are read

New Group by flow template โ€” Boards and flow queries can group by flow template. Be prepared for the new flow_template_id value when reading boards.

API details
  • config.group_by.field on POST /v1/kanban/board and PUT /v1/kanban/board/{boardId}
  • group_by.field on POST /v1/kanban/query/flows:execute

Portal User Entity

New Portal roles for portal users โ€” Portal users can be assigned a portal role through a new role field. When it is empty, the portal's default role applies.

October 20, 2026

AI Agents API

Changed Knowledge source endpoints removed โ€” The knowledge source endpoints were removed without deprecation.

API details
  • POST /v1/knowledge/file-uploads
  • GET /v1/knowledge/sources
  • GET and DELETE /v1/knowledge/sources/{source_id}

Changed Longer agent execution timeouts โ€” timeout_ms on POST /v1/agents/{agent_id}/execute and POST /v1/agents/{agent_id}/execute/stream allows up to 600000 milliseconds (previously 300000) and no longer has a default of 30000.

Minor Execution results report why they stopped through a new optional result.stop_reason field

App API, External Values API

New value context requirement for hooks โ€” App hooks can declare a new value context requirement type. Be prepared for it when reading app components and hooks.

API details
  • configuration.hooks[].contexts on app components
  • hooks[].contexts on hooks returned by GET /v1/external-values

Changed Longer hook timeouts โ€” The maximum timeout_ms for app hooks was increased from 5000 to 20000 milliseconds.

Customer Portal API

New Notification preferences for portal users โ€” Read and update a portal user's notification preferences.

API details
  • GET and PUT /v2/portal/user/notification-preferences

New Notify when an entity is added โ€” Portal notification triggers can fire when an entity is added, and can be limited to specific targets.

API details
  • New entity_added value for notification_triggers[].trigger_type
  • New optional notification_triggers[].target_ids field

Identity API

New Sector identifier โ€” GET /v1/identity/sector-identifier/{client_id} returns the sector identifier of a client.

Integration Toolkit API

Deprecated v1 monitoring endpoints โ€” Use the /v2 counterparts instead.

API details
  • POST /v1/integrations/{integrationId}/monitoring/inbound-events, outbound-events, stats, and timeseries

Journey Config API

Breaking blueprint_customization removed โ€” Journey configurations no longer accept or return blueprint_customization.

API details
  • No longer accepted when creating or updating a journey configuration or revision in v1 and v2
  • No longer returned wherever journey configurations are read

New Journey template variables โ€” List the template variables available to journeys.

API details
  • GET /v1/journey/template-variables
  • v1 journey configurations now carry their templating context wherever they are read

Phone Integration API

New Manage phone agents โ€” Add, list and remove phone agents, and read the status of the phone integration.

API details
  • GET and POST /v1/manager/agents and DELETE /v1/manager/agents/{user_id}
  • GET /v1/manager/status

New Live monitoring, call reporting and routing โ€” Monitor live agent and queue activity, report on calls, and configure an agent's call routing.

API details
  • GET /v1/manager/live, GET /v1/manager/agents/live, GET /v1/manager/queues, GET /v1/manager/queues/{queue_id}, and GET /v1/manager/reporting/calls
  • PUT /v1/manager/agents/{provider_agent_id}/routing and POST /v1/manager/agents/{provider_agent_id}/routing:preview

New Agent presence โ€” Set an agent's presence and list agent presences.

API details
  • PUT /v1/manager/agents/{provider_agent_id}/presence and GET /v1/manager/presences

Sharing API

New List sharing configurations โ€” GET /v1/sharing/configurations:list lists sharing configurations.

Snapshot API

New Skipped org snapshots โ€” Scheduled org snapshots can now be skipped. Be prepared for the new skipped status.

API details
  • last_status on GET and PUT /v1/org-snapshot-schedule can return skipped, together with a new optional last_status_reason field

Minor DELETE /v1/snapshots/{id} can respond with 409 when a conflicting operation is in progress

October 19, 2026

Customer Portal API

New Portal copilot access โ€” Check access to the portal copilot and control its visibility.

API details
  • New GET /v2/portal/copilot/access endpoint
  • New optional feature_settings.portal_copilot_visibility field, accepted when creating or updating portal configurations and returned wherever they are read

Pricing API

Breaking fields is no longer accepted on POST /v1/public/catalog

Changed The required warnings field was removed from the POST /v2/public/catalog response

Notification Template Entity

Changed Notification templates can now have a separate title and message for the end-customer portal through new portal_title and portal_message fields, which fall back to the regular title and message when empty

October 16, 2026

Automation API

Changed Assignment actions can now require skills from their assignees through new optional actions[].config.required_skills and actions[].config.required_skills_match_mode fields โ€” accepted on POST /v1/automation/flows and PUT /v1/automation/flows/{flow_id} and returned wherever flows and executions are read

Design Builder API

New New POST /v1/designs/generate endpoint was added for generating a design

Integration Toolkit API

Action needed Import validation can now report the new issue codes UNIQUE_ID_NOT_IN_SCHEMA and VALID_FROM_NOT_MAPPED, and issue attributes carry a new optional entity detail โ€” returned by all /v2/erp/imports endpoints, so consumers must be prepared for these additional issue codes

Workflows Definition API

Action needed Task conditions in flow templates can now reference flow runtime and flow trait values through the new flow_runtime value for source.origin and flow_trait value for source.origin_type, so consumers reading flow templates must be prepared for these additional values

October 15, 2026

Entity API

Action needed failure_code on POST /v1/entity:import and GET /v1/entity:import:latest can now return new values such as dry_run_required, dry_run_expired, dry_run_mismatch, import_too_large, and token_expired, so consumers must be prepared for these additional failure codes

New New GET /v1/entity:importHistory endpoint was added for listing past entity imports, and imports now report their progress through new optional phase, started_at, heartbeat_at, finished_at, and issues fields

New New GET /v1/entity/{slug}/{id}/summary endpoint was added for reading a summary of an entity

Changed Entity schemas can now require a comment on changes through a new optional require_change_comment field โ€” accepted on PUT /v1/entity/schemas/{slug} and returned wherever entity schemas are read

GenAI API

Breaking GET /v1/genai/thread/{threadId}/info, GET and POST /v1/genai/entity/{slug}/{entity_id}/summary, and POST /v1/genai/portal/getDesign endpoints were removed without deprecation

Message API

New New GET /v1/message/threads/{id}/summary endpoint was added for reading a summary of a message thread

Pricing API

Breaking Variant conditions on POST /v1/conditional-pricing/{slug}/entities/{entity_id}/variants:list and POST /v1/conditional-pricing/{slug}/entities/{entity_id}/variants:tree now use the new ContextConditionValue and PostalCodeFilter shapes; the previous PostalCodeCity and ConditionPredicate shapes are no longer accepted in conditions

Core Entities

Changed Coupon, Price, Product, and Tax entities can now carry footnotes through a new footnotes field

October 14, 2026

Entity API

New New GET /v1/entity:wipeJobs endpoint was added for listing entity wipe jobs

Changed POST /v1/entity:wipeAllEntities now accepts at most 90 schemas per request (breaking) and can respond with 409 when a wipe is already in progress

Integration Toolkit API

Action needed code on monitoring events, associated events, and trace spans is no longer always a string, so consumers must handle other value types

Action needed ERP update submissions on the /v1, /v2, and /v3 erp/updates/events endpoints now return a new optional correlation_close field, v3 events and correlations report omitted entities through a new optional entities_omitted field, and monitoring events, associated events, and trace spans can now report the new PROCESSING_STATE_LIMIT code, so consumers must be prepared for this additional value

New New GET /v3/erp/updates/events, GET /v3/erp/updates/events/{event_id}, and GET /v3/erp/updates/correlations endpoints were added for tracking submitted ERP update events and their correlations, including whether a correlation is complete and its errors_total

New New POST /v2/integrations/{integrationId}/monitoring/runs/completion endpoint was added for reporting the completion of a monitoring run

Changed ERP updates can now be processed interactively: POST /v3/erp/updates/events accepts new optional interactive, events[].interactive, and correlation_complete fields, use cases accept a new optional configuration.interactive field, and the /v1, /v2, and /v3 erp/updates/events endpoints now return a correlation_id together with each result's interactive flag and lane

Changed group_id and events[].group_id on POST /v3/erp/updates/events must now be non-empty and contain only printable characters without spaces