Webhooks

How webhooks work

SilentSources sends a signed HTTP POST to your HTTPS endpoint when something happens (payment completed, application submitted, ticket updated, etc.).

Payload shape

Bodies are JSON. A typical event looks like:

• —id — unique event id
• —type — e.g. payment.completed, application.submitted
• —created_at — ISO timestamp
• —data — event-specific object

Verifying signatures

Use the webhook secret from your developer access to verify the signature header before trusting the payload. Reject requests with invalid signatures.

Retries

Failed deliveries (non-2xx) are retried with backoff. Make handlers idempotent using the event id so duplicates are safe.

Common events

Depending on the product:

• —payment.completed / payment.failed
• —application.submitted / application.reviewed
• —support.ticket.created / support.ticket.closed
• —discord.member.linked