Integrations
epilot provides multiple integration paths depending on your use case -- from high-level ERP synchronization to low-level API batching and custom form submissions.
Integration Options​
| Approach | Use case | Entry point |
|---|---|---|
| Integration Toolkit | Standardized ERP integration with mapping, monitoring, and event-driven sync | Best for energy-sector ERP systems (SAP, Wilken, Schleupen) |
| Batch API | Execute multiple API calls in a single request | Best for bulk data operations and middleware with message quotas |
| 3rd Party Journeys | Submit data from external forms and frontends | Best for custom checkout flows and headless integrations |
| Webhooks | Receive real-time event notifications | Best for event-driven architectures |
| Public APIs | Direct API access to all platform capabilities | Best for custom integrations with full control |
Business Events​
epilot emits business events for the things that happen in your organization. Core Events ship with the platform; Custom Events are authored by your organization and projected from your own entity attributes. Both are consumed the same way — through webhooks, automations, or the Event Catalog API.
Rate Limits​
All epilot APIs enforce rate limits to ensure fair usage. Use the Batch API or Integration Toolkit for high-volume operations.
Authentication​
Integration APIs support two authentication methods:
| Method | Use case |
|---|---|
| Access Tokens | Server-to-server integrations with scoped permissions |
| Publishable Tokens | Client-side integrations (e.g., journey embeds, public cart checkout) |
See Authentication for details.