Skip to main content
  • Delivery is usually within seconds of the event being recorded. A few events are held briefly before their message is built, so their details are complete:
    • about 60 seconds: partner.created, account.signed_up;
    • about 90 seconds: agent.created, account.first_agent_created, org.first_agent_created;
    • about 2 minutes: account.first_call_received, account.first_real_call_received, org.first_call_received, org.first_real_call_received, agent.first_call_received.
  • Telzino is alerted internally if delivery lags more than 5 minutes.
  • Any non-2xx, timeout (10 s) or connection error is retried with exponential backoff (1 minute doubling to 1 hour, with jitter) for 24 hours. 429 and 503 with Retry-After wait as long as you ask, between 1 minute and 1 hour.
  • Redirects are not followed. URLs must be https on a public host.
  • Messages can arrive out of order; use occurred_at.
  • Monitoring events are sent only to the endpoint whose event settings they met, not to every endpoint that would otherwise receive them.

Endpoint health

A short outage never disables an endpoint. When you enable an endpoint that has held deliveries, choose resume (send them) or discard. Delivery logs are kept for the retention period Telzino sets for the platform, 30 days by default.