Events
Subscribe only to the events your integration needs. The exact list is in the documentation.
Developers · Webhooks
Webhooks: get notified, process exactly once.
When an analysis, article or export changes state, Aive can notify your system. A reliable receiver verifies every notification, processes it once and keeps a record of what it did.
Event types, headers and signature method: the public documentation is authoritative.
Last verified · 26 September 2026
What are Aive webhooks for?
Webhooks spare you from polling the API. Aive sends an HTTP notification to the address you register whenever a job changes state, for example a finished analysis or an article ready for approval. Your system checks the message is authentic, deduplicates it, then triggers the next step. Event types and the exact format are described in the public documentation.
- Event
- A state change notified by Aive, identified by a type and a unique identifier.
- Idempotency
- The property of a handler that produces the same result if it receives the same event twice.
- Retry
- A new delivery attempt when your system has not accepted a notification.
Principles
Four rules for a reliable receiver.
Signatures and secrets
Verify every notification using the documented method. Keep the secret server-side and plan its rotation.
Idempotency
Store the identifier of every processed event. A duplicate is acknowledged, not reprocessed.
Retries
A notification may arrive more than once or late. Your handler must cope with both.
Receiving
From notification to action.
- 01Receive on a dedicated HTTPS addressRegister an address reserved for Aive webhooks, separate from your other entry points.
- 02Verify authenticityReject any message whose signature does not match the shared secret, using the method described in the documentation.
- 03Acknowledge quicklyRespond as soon as verification passes, then process asynchronously so delivery is not held up.
- 04DeduplicateIf the event identifier has already been processed, stop there.
- 05Process and logTrigger the next step, then record the event, the outcome and the timestamp.
Retry policy
The number of attempts and their spacing are those described in the public documentation or defined in the contract. Do not assume them: read the reference.
- Public documentation
- Enterprise contract
Before going live
Is your receiver ready?
Security
- Dedicated HTTPS address
- Signature checked every time
- Secret stored server-side
- Secret rotation planned
Robustness
- Fast acknowledgement
- Asynchronous processing
- Deduplication by event identifier
- Tolerance of duplicates and delays
Traceability
- Log of received events
- Outcome of each handler run
- Alert on repeated failures
- Aive support contact identified
What this page does not describe.
- Event names, headers, payload formats and signature algorithm: these appear only in the public documentation.
- Number and spacing of retries: documented at api.aive.tech or defined in the contract.
- Delivery order is not assumed to be guaranteed: design handling that does not depend on order.
- A webhook reports a state change; it is not editorial approval or publication.
Frequently asked questions
Questions about webhooks.
Which events can I receive?
The exact list of event types and their format is described in the public documentation at api.aive.tech. Subscribe only to those your integration needs.
What if I receive the same event twice?
This is a normal case to plan for. Store the identifier of each processed event; if a duplicate arrives, acknowledge it without running the handler again.
What happens if my system is down?
Notifications that are not accepted may be retried, according to the policy described in the documentation or the contract. Watch your log to spot repeated failures.