Atune API documentation
Atune Webhooks
Atune does not currently offer a generally available public outbound webhook API. This page is the canonical source for webhook availability so developers and agents do not infer an unsupported endpoint or send credentials to unofficial integrations. Existing payment-provider callbacks are internal service integrations and are not customer webhooks.
Current integration options
Use the Atune web application for account-specific monitor results. Public scripts may use the read-only capabilities and platforms endpoints, while agents may connect to the public MCP server for product discovery. Email digests remain the supported notification channel for customer monitoring workflows.
Planned webhook requirements
Before public webhooks launch, Atune will publish event names and schemas, HTTPS delivery requirements, signature verification, timestamp and replay protection, retry and backoff behavior, idempotency guidance, delivery logs, endpoint rotation, and data-retention rules. No integration should assume these details before they are documented here.
Request webhook access
Teams evaluating event-driven integrations can contact support@atune.cc with the events they need, expected delivery volume, destination security requirements, and retention constraints. Do not send signing secrets or production credentials by email.