Overview
Instead of polling the status endpoint, you can provide acallback_url in your interactive notification request. NextKS will POST the results to your URL when the request finishes.
When callbacks fire
A callback is triggered when:onUserActionmode: All users have respondedonTimeoutmode: The timeout is reached- Either mode: The timeout is reached and some users haven’t responded
Callback payload
NextKS sends aPOST request with Content-Type: application/json:
Callback URL requirements
Your callback URL is validated when you submit the notification:| Requirement | Details |
|---|---|
| Protocol | HTTPS only |
| DNS | Must resolve to a public IP address |
| Reachability | Must respond to a HEAD request within 5 seconds |
| Private IPs | Blocked (10.x, 172.16-31.x, 192.168.x, 127.x, 169.254.x) |
400 error.
Retries
If a callback delivery fails (network error or non-2xx response), NextKS retries automatically:- Up to 3 retry attempts via the background cron job (runs every minute)
- Each attempt is logged with the error message
- Once successful, no further retries are attempted
Handling callbacks
Your endpoint should:- Return a
2xxstatus code to acknowledge receipt - Process the payload asynchronously if needed — NextKS has a 10-second timeout
- Be idempotent — in rare cases, a callback may be delivered more than once