Developers

Available

Webhooks

A planned webhook overview; webhook delivery is not active.

Webhooks can notify external systems about events, but they require strong signing, replay protection, privacy rules, and delivery controls.

What this means

Webhook payloads must never leak private family, DNA, media, or source content.
Webhook delivery needs signature verification, retry policy, and audit boundaries.
Planned webhook concepts must not be mistaken for active production behavior.

How AINMAX supports this

Current page explains webhook safety requirements as future planning.
Security and API pages provide context for signed integrations.
No event delivery system is activated by Resources content.

What is available now

Static Webhooks resource page.
Safety-oriented webhook planning notes.
No webhook registration, delivery, retry, or secret management UI.

What is planned

Webhook event catalog only after accepted backend implementation.
Signature and replay-protection policy.
Testing tools and delivery logs if future webhook support is approved.

Privacy / safety note

This page does not activate webhooks, event delivery, federation callbacks, secrets, or external data sharing.