Users may notice that after a schema update or data model change, outbound integrations such as Webhooks or Integration Hub event flows stop delivering updates or begin omitting certain fields. This typically happens because outbound events depend on predefined schema definitions that do not automatically refresh when the underlying entity model is updated. As a result, once the schema changes, the configured webhook or integration may reference outdated field mappings or drop unmapped attributes until the schema is manually refreshed and re-published.
Solved
Why did my outbound API or webhook integration stop sending updates after a recent schema or data model change in Fenergo?
Best answer by jawadkhan
If you are using Webhooks or Integration Hub outbound events, they rely on a configured schema definition that does not automatically refresh when the entity model changes.
After schema updates, your webhook may silently stop delivering or drop unmapped fields.
To Resolve
- Retrieve the latest OpenAPI schema from the API Catalogue and update your webhook or integration mappings.
- Use the PUT /webhooks/v1/webhooks/{id} endpoint to refresh event type definitions or URLs. ⁷
- Re-publish the configuration through Integration Hub.
- Validate delivery by sending a test event (e.g. entitydata:created) and confirming the corresponding success notification.
Best Practice: After each major API release, refresh your event definitions from the API Catalogue to prevent “ghost mappings” (fields that exist in configuration but not in schema).
If you are using Webhooks or Integration Hub outbound events, they rely on a configured schema definition that does not automatically refresh when the entity model changes.
After schema updates, your webhook may silently stop delivering or drop unmapped fields.
To Resolve
- Retrieve the latest OpenAPI schema from the API Catalogue and update your webhook or integration mappings.
- Use the PUT /webhooks/v1/webhooks/{id} endpoint to refresh event type definitions or URLs. ⁷
- Re-publish the configuration through Integration Hub.
- Validate delivery by sending a test event (e.g. entitydata:created) and confirming the corresponding success notification.
Best Practice: After each major API release, refresh your event definitions from the API Catalogue to prevent “ghost mappings” (fields that exist in configuration but not in schema).
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.