FAQ¶

Can I use one integration across multiple events?¶

Yes — your single registered integration can be connected to as many events as organizers choose to connect it to. Each connection is a separate authorization with its own installation token, but they all use the same client_id / client_secret.

What if I need to write data back to Revento?¶

The API is read-only. If you have a use case that requires writes, raise it with your account contact.

Can I get a list of all my installations?¶

Yes. GET /developer/integrations/{integration_id}/installations returns every (event, organization) tuple your integration is connected to. See API → endpoints → developer endpoints.

How do I migrate when scopes change?¶

You ship a new integration version that declares the new scope set. Existing connections enter a "re-consent required" state — the previous token works for the old scope set, the new scope is locked behind explicit re-consent from each organizer. There is no silent migration path.

What's the SLA on webhook delivery?¶

Webhooks are best-effort with retry. Seven attempts (initial + 6 retries) with the curve 30s, 2m, 10m, 1h, 6h, 24h, then dead-letter. We don't promise an end-to-end SLA — partner-side outages can push delivery hours out. Inspect the dead-letter queue in your developer console if a webhook never arrived.

What happens if Revento goes down?¶

Your installation tokens stay valid (we don't expire them on outage). Webhook delivery is queued and retried. API calls fail with normal HTTP errors during the outage; resume when we're back.