Integrations
Operate external providers, callbacks, API usage, and automation with confidence.
Use this guide to integrate Relet with external systems while protecting reliability and operational safety.
Integration scope
This section covers public integration behavior and operational requirements.
Payment providers
Manage provider readiness, operational checks, and rollout safety.
Webhook callbacks
Operate callback authenticity, idempotency, and retry-safe handling.
RPC API
Use typed API contracts safely across client and server boundaries.
Automation and cron
Run scheduled operations without duplicate execution risk.
Integration operating model
Follow this model when onboarding or changing integrations.
Define integration owner, scope, and expected business outcome.
Configure provider and callback endpoints with controlled rollout.
Validate end-to-end flow on controlled scenarios.
Monitor delivery, retries, and downstream state transitions.
Reliability expectations
Apply these expectations across all integration workflows.
- Every asynchronous event flow must be duplicate-safe.
- Every integration has clear failure and retry handling behavior.
- Every release includes post-change monitoring checks.
- Every major incident has a documented prevention action.
Next steps
- Start with Payment providers.
- Harden event safety with Webhook callbacks.
- Align support response with Troubleshooting.
Last updated on