Blog
Blog: epilot integration in practice
Articles for IT leads at utilities, municipal utilities and grid operators who run epilot and need to connect surrounding systems.
- 11 min read
An epilot integration project at a grid operator
How an epilot integration project at a grid operator runs, from the intro call to quote, interfaces and operation, plus answers for procurement and legal teams.
Read article - 10 min read
Connecting ERP, billing and third-party systems to epilot
epilot integration explained: when the Integration Toolkit, Batch API, webhooks or public APIs fit, and when dedicated middleware connects your other systems.
Read article - 12 min read
epilot API: providing data from other systems via REST
How the epilot API and a dedicated REST API bring data from CRMs and databases into epilot: pull vs push, OpenAPI contracts, rate limits, caching and GDPR.
Read article - 10 min read
Mappers between epilot and third-party systems with Quarkus
A Quarkus mapper for epilot: how it receives webhooks, converts data for third-party systems, calls them via REST and handles failures in operation.
Read article - 11 min read
Processing epilot webhooks securely
How to process an epilot webhook securely: verify the signature, check the timestamp, respond fast, handle retries and replays, and make processing idempotent.
Read article - 11 min read
Running epilot integrations: monitoring, errors, maintenance
epilot integration maintenance after go-live: monitoring mappers, handling errors with replay, rate limits, updates, and who looks after interfaces long term.
Read article - 9 min read
When is low-code in epilot no longer enough?
epilot low-code goes a long way. How grid operators and utilities spot when third-party systems, data transformations or events need classic development.
Read article - 9 min read
Who owns the integration code?
The code of an epilot interface belongs to the client. What grid operators should know about repositories, handover, maintenance contracts and independence.
Read article