Skip to main content
Cashback does not enforce request rate limits at the partner endpoint. The service is designed to absorb partner traffic at production rates without throttling.

​
Behavior under burst

  • Each notification is processed concurrently. There is no fixed worker pool to saturate
  • If internal capacity is momentarily strained, notifications are dropped from backrun analysis rather than queued. Your transactions are unaffected; they were never waiting on nexroute
  • No partner request is rejected for rate-limit reasons

​
What this means for integration

  • You don’t need client-side throttling against the Cashback endpoint
  • Sustained extreme bursts may reduce backrun yield on the affected window, but never delay or affect your own dispatch
  • Connection reuse (HTTP keep-alive or persistent WebSocket) is recommended for high-throughput callers to amortize TLS handshakes

​
Anticipated heavy patterns

If you expect sustained traffic that could strain capacity (large-scale TWAP, market-making bursts, scheduled order release), let nexroute know during onboarding so capacity can be pre-provisioned for your endpoint.