Fast Acknowledgment
Immediate response with a secure channel ID. No open connection holding, fundamentally eliminating gateway timeouts on slow generations.
Rest Webhooks
Async Webhooks Pattern
Fire-and-forget background processing. Request is submitted once and results are delivered simultaneously to dual webhooks.
1
Recommended
Event-driven async
Real-time updates via WebSocket. Backend callbacks for processing. Best for interactive apps.
Learn more2
Async (Dual-Delivery)
Fire and forget. Results delivered simultaneously to your webhook and browser. Best for reliable background ops.
Learn more3
Sync
Simple request/response. Blocks until complete. Best for quick operations.
Learn moreAsync dual-delivery flow
Simpler flow · Simultaneous results to webhook and WebSocket
1
Your backend
API request
2
ModelRiver
Orchestration
3
AI providers
Completion
4
Your webhook
HTTP callback
5
User's browser
WebSocket push
Architecture
Why dual-delivery async?
Deliver robust integrations easily. By leveraging two asynchronous channels simultaneously, you guarantee data integrity across arbitrary node disconnects.
Background Execution
AI runs asynchronously in isolated worker pools. Your backend remains lightning fast and completely insulated from thread exhaustion.
Automatic Fallback
Seamless multi-provider failover baked deeply into the pipeline. Achieve five-nines orchestration without altering any of your client architecture.
Instant Delivery
Real-time WebSocket conduits autonomously push the final streaming payloads directly back to the active client layer.