API Reference

Server-side APIs for tenant provisioning and operational message delivery.

These examples describe the intended public contract for enterprise backend systems. Production credentials must remain server-side.

Create a tenant application

REST
POST/v1/tenant/app_create
{
  "tenant_name": "Northwind Treasury Operations",
  "region": "us-east-1",
  "isolation_mode": "dedicated_namespace",
  "webhook_url": "https://ops.example.com/hooks/messages"
}

Send an operational message

REST
POST/v1/message/send
{
  "app_id": "app_8V2mQp91",
  "channel_id": "workflow_settlement_alerts",
  "message_type": "workflow_notification",
  "payload": {
    "subject": "Settlement review required",
    "reference_id": "txn_2026_05_19_8841",
    "severity": "high"
  }
}

Authentication Headers

EpollLink APIs use tenant-scoped server credentials for backend-to-platform requests.

X-EPOLL-API-KEY

Public application key issued per tenant

X-EPOLL-API-SECRET

Server-side credential for signed enterprise requests

X-EPOLL-REGION

Optional region hint for globally distributed routing