IntegrationEngine — Symfony Bundle

The Problem

Every integration ends up as an isolated case

Different formats, inconsistent auth, duplicated cache logic. Code fragments and every new API means starting from scratch.

Duplicated auth

Tokens and cache reimplemented in every integration.

No common contract

Every HTTP client has its own structure.

Hard to test

HTTP coupled to domain. Impossible to isolate.

No consistency

Every developer solves it their own way.

Zero visibility

No traceability, no unified logs, no shared context.

How It Works

One flow for all your integrations

A single entry point. Each step has a clear responsibility.

Registry→

IntegrationEngine→

Action→

Auth→

HTTP→

Mapper→

Response DTO

Dynamic auth with cache

OAuth, sessions, API keys. The engine resolves and caches them automatically.

Path context

/orders/{id} resolved at call time. Explicit failure if param is missing.

Three-layer headers

YAML → auth → call layer. Each layer overrides the previous. No magic.

Typed responses

Each action defines its own Response DTO with a guaranteed contract.

Fully extensible

Client, cache and config source replaceable with one line in YAML.

Scaffolding included

make:integration generates Mapper, Response DTO and YAML in seconds.

The Call Site

One line. Always the same.

No magic strings — everything through contracts.

        
        
        
      
// No authentication
$registry->get(
    AcmeIntegration::NAME
)->send(
    GetUsersAction::getName()
);
// With route params — /users/{id}
$registry->get(
    AcmeIntegration::NAME
)->send(
    GetUserAction::getName(),
    context: DefaultActionContext::create(['id' => 42])
);
// With body and custom headers
$registry->get(
    AcmeIntegration::NAME
)->send(
    CreateOrderAction::getName(),
    body:    $body,
    headers: new CorrelationHeaders($id)
);

Layered Design

The bundle suggests. Doesn't enforce.

Three levels that emerge naturally. Use what you need.

Class	Responsibility	Scope
CreateChargeAction	Only declares the method, path and response DTO. No HTTP logic.	Concrete action
StripeAction	Auth, base path and common Stripe headers. Reused by all its actions.	Integration
AbstractAction	Base contract provided by the engine. Extensible without touching the core.	Bundle

The make:integration command creates the config, classes and YAML in one step.

Stop writing the same HTTP client over and over