Blame
|
1 | # Webhooks |
||||||
| 2 | ||||||||
|
3 | Webhooks let AeThex notify external systems when events happen, reducing the need for polling. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Event delivery</h2> |
|||||||
| 7 | <p>Use webhooks when an integration needs to react to changes in near real time.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | Webhooks may be used for project events, identity changes, organization updates, support workflows, build notifications, or integration-specific events as the platform expands. |
||||||
| 11 | ||||||||
| 12 | ## Webhook lifecycle |
|||||||
| 13 | ||||||||
| 14 | 1. Register an endpoint for a project or organization. |
|||||||
| 15 | 2. Select event types. |
|||||||
| 16 | 3. Store and protect the signing secret. |
|||||||
| 17 | 4. Verify signatures on incoming requests. |
|||||||
| 18 | 5. Return success quickly and process work asynchronously. |
|||||||
| 19 | 6. Monitor failures and retries. |
|||||||
| 20 | ||||||||
| 21 | ## Receiver checklist |
|||||||
| 22 | ||||||||
| 23 | - Use HTTPS. |
|||||||
| 24 | - Verify signatures before trusting payloads. |
|||||||
| 25 | - Make handlers idempotent. |
|||||||
| 26 | - Log event IDs for debugging. |
|||||||
| 27 | - Handle retries safely. |
|||||||
| 28 | - Respect [[Rate-Limits]]. |
|||||||
| 29 | ||||||||
| 30 | <div class="docs-grid"> |
|||||||
| 31 | <a class="docs-card" href="/Api-Reference">API Reference</a> |
|||||||
| 32 | <a class="docs-card" href="/Authentication">Authentication</a> |
|||||||
| 33 | <a class="docs-card" href="/Rate-Limits">Rate Limits</a> |
|||||||
| 34 | <a class="docs-card" href="/Security">Security</a> |
|||||||
| 35 | </div> |
|||||||