📄️ Event Ingress Overview
In a similar way that Fenergo sends notifications out to clients via polling or webhooks to reflect activity from within our platform, Clients may have activity from within their technical landscape that affect Legal Entity Data and need to reflect that update on the Fenergo System. Clients of course have a range of options in how they push data onto Fenergo. They can use the Data Migration APIs or Direct Connect Entity Data / Journey APIs. Another way to inform Fenergo of external activity is to send a message to our Event Ingress API interface.
📄️ Event Ingress APIs
The Event Ingress API is offered as a standard REST endpoint. It is not a Command / Query implementation as this pattern does not suit the functionality. It is intended to allow clients configure custom event types and then perform a Fire and Forget interaction and have Fenergo perform all the required internal orchestration.
📄️ Rate Limiting Events
Event Ingress previously applied a simple API Rate Limiting strategy of accepting a fixed number of events within a time window, similar to other fine-grained APIs in Fenergo SaaS. This worked for legacy Business Processes (e.g. CreateEntity, UpdateEntity, etc) when events operated on a single entity at a time with a fixed number of internal API calls.
🗃️ DataImport
2 items
🗃️ VerifiedImport
2 items
🗃️ Legacy Events
2 items
🗃️ CreateAlert
1 item