Integrations API

Connect Avvyr to external systems — ERP, accounting, marketing, shipping, and more

The Avvyr Integrations API is an event-driven platform for moving data between external systems and Avvyr — with transaction tracking, automatic retries, and full observability through a visual dashboard.

Two directions

The platform supports two directions of data flow, each with different capabilities:

Inbound — external systems → Avvyr

Push data into Avvyr from any external system. This is fully open: use the Custom Inbound API to send inventory updates, orders, products, prices, or customers from any system that can make an HTTP call.

External System → POST /integrations/custom/inbound → Queue → Worker → Avvyr

Outbound — Avvyr → external systems

When something happens in Avvyr (an order is placed, inventory changes, a receipt is generated), the platform publishes a domain event. That event is routed to pre-built connectors (Klaviyo, OmniConnect, Business Central, etc.) that transform and deliver the data to the external service.

Avvyr Platform → Domain Event → Dispatcher → Pre-built Connector → External Service

Outbound delivery through the Integrations API is only available via pre-built connectors. If you need to react to Avvyr events in your own system, use the Events API instead — it lets you subscribe to domain events and receive webhooks at your own HTTP endpoints with configurable auth and retries.

Every transaction — inbound and outbound — is tracked as an IntegrationEvent with full lifecycle visibility: queued → processing → success | failed. Failed events can be retried automatically or manually resubmitted.

Key capabilities

Pre-built connectors — outbound integrations for popular services (Klaviyo, Business Central, Fortnox, etc.)
Custom inbound API — generic REST endpoint for pushing data into Avvyr from any external system
Event tracking — every transaction is logged with status, payloads, and communication history
Automatic retries — exponential backoff with configurable retry counts per event type
Manual resubmission — retry any failed event with one click in the dashboard
Dead-letter handling — events that exhaust retries are captured and surfaced for investigation

Looking for outbound events? The Events API lets you subscribe to domain events (order created, product updated, etc.) and receive webhooks at your own endpoints.

Next steps

Why the Integrations API? — when to use it and how it compares to the Management API
Who is it for? — use cases and target audiences
Pre-built Integrations — available connectors and what they sync
Custom Inbound API — push data into Avvyr from any system
Event Lifecycle — how events flow through the platform
Management API Endpoints — configure and monitor integrations via API

Event Reference

All available domain events with descriptions

Why Use It?

How the Integrations API compares to calling the Management API directly — and when each approach makes sense