Rate Limits

​

Limits

​

Per API key

​

Per organization (tenant)

​

Other limits

{
  "status": "error",
  "details": "Per-key rate limit exceeded (10 burst / 2 per second)"
}

​

Idempotency

curl -X POST https://app.nextks.com/api/notify \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: deploy-v2.4.1-notify-20260213" \
  -d '{ ... }'

const response = await fetch('https://app.nextks.com/api/notify', {
  method: 'POST',
  headers: {
    'X-API-Key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
    'Idempotency-Key': 'deploy-v2.4.1-notify-20260213',
  },
  body: JSON.stringify({ /* ... */ }),
})

import requests

response = requests.post(
    "https://app.nextks.com/api/notify",
    headers={
        "X-API-Key": "YOUR_API_KEY",
        "Idempotency-Key": "deploy-v2.4.1-notify-20260213",
    },
    json={ ... },
)

• If the same key is sent within 24 hours, the cached response is returned without re-processing
• Keys are scoped per organization — different orgs can use the same key without conflict
• Keys older than 24 hours are automatically cleaned up

​

Best practices

• Batch recipients — Send to multiple users in a single request instead of making separate calls per user
• Respect Retry-After — Wait the indicated number of seconds before retrying
• Use idempotency keys — Include an Idempotency-Key header when retrying failed requests to prevent duplicates
• Use callbacks — For interactive notifications, use callback_url instead of polling the status endpoint repeatedly
• Cache responses — Status endpoint results can be cached for a few seconds to avoid unnecessary calls