New GET /v1/entities/{entityId}/sync-status endpoint added for reading how an entity is synced with the connected external system — each reported sync state carries an optional last_operation and last_synced_at, plus optional readings_last_event_id, readings_last_operation, and readings_last_synced_at for meter readings
New POST /v1/erp/updates/direct_simulation endpoint added for simulating a direct update payload
Use cases can now be configured for direct updates through a new optional configuration.direct field, and configuration.entities[].fields is no longer required — accepted when creating or updating a use case or an integration, returned wherever use cases are read, and also accepted by POST /v1/erp/updates/mapping_simulation and POST /v2/erp/updates/mapping_simulation
POST /v3/erp/updates/events now accepts an optional correlation_id per event