Layer 07 · Integration Layer
Expose your application through one canonical outward path
Expose your application outward through webhooks, public APIs, and typed SDKs. External systems integrate through one canonical path — the same path documented in the registry.
Why this layer
Built into the platform, not bolted on
Every module in this layer solves the same class of problem the same way — regardless of who implements it.
01
APIs generated from schema
REST and RPC endpoints derive from your platform schema — not hand-maintained OpenAPI specs that drift from implementation.
02
Webhooks with platform reliability
Outbound event delivery includes retry logic, signature verification, and per-tenant registries. External integrations inherit platform-grade delivery.
03
One SDK import per capability
Type-safe client and server libraries with strict TypeScript across boundaries. Consumers integrate through documented registry paths — not vendor SDKs.
Canonical implementation
One path for every author
Junior developers, senior engineers, and AI agents produce the same standard output.
How Conflux does it
Integration surfaces mirror the internal registry
What your team uses internally is what external consumers get. Rate limiting, auth, and schema validation enforce at the edge — consistently.
Canonical path
Public API generated and versioned from platform schema
Webhooks sign payloads and retry with dead-letter handling
SDK methods map 1:1 to registry capabilities
OpenAPI specs published automatically on deploy
What you get
Ship partner APIs without maintaining parallel documentation
Deliver webhooks with reliability defaults, not custom retry code
Give integrators the same typed SDK your team uses
Version external surfaces alongside internal schema changes
01 · Integration Layer
Reliable outbound event delivery
Webhook registries per tenant with signature verification, retry logic, and dead-letter handling. External systems integrate through one documented delivery path.
Webhooks · One canonical path
SDK
await conflux.webhooks.dispatch('order.created', payload)CLI
conflux webhooks register https://...
Config
webhooks: retry: exponential
What's possible with Webhooks
01
Outbound event delivery to external systems
02
Retry logic and signature verification built in
03
Webhook registry per tenant and environment
02 · Integration Layer
APIs generated from your schema
REST and RPC endpoints with rate limiting, auth at the edge, and OpenAPI specs published on deploy. External API surface mirrors the internal registry.
Public API · One canonical path
SDK
// auto-generated from schema
CLI
conflux api publish
Config
api: version: v1
What's possible with Public API
01
REST and RPC APIs generated from platform schema
02
Rate limiting and auth enforced at the edge
03
OpenAPI specs published automatically
03 · Integration Layer
One import path per capability
Type-safe client and server libraries with strict TypeScript across all platform boundaries. No vendor SDKs — every capability through @conflux-stack/sdk.
SDK · One canonical path
SDK
import { conflux } from '@conflux-stack/sdk'CLI
conflux init my-app
Config
// conflux.config.ts at project root
What's possible with SDK
01
Type-safe client and server libraries
02
One import path per capability — no vendor SDKs
03
Strict TypeScript across all platform boundaries
Explore
Continue through the platform
Nine layers, one cohesive stack. Browse adjacent layers or return to the full registry.