Event webhooks send selected Moxie activity to an HTTPS endpoint using JSON over an HTTP POST request.
Create and secure a webhook
Enable Custom API or expand an existing Custom API key.
Choose the authentication method your receiver expects: None, Basic, Bearer, or a custom header.
Select Add webhook, choose the Moxie event, and enter an HTTPS endpoint.
Save the webhook and test the business action that emits the event.
Create a dedicated key for each application or environment so access can be revoked independently.
Handle deliveries
Moxie sends X-Event-Origin: withmoxie.com and the selected type in X-Event-Type. Your receiver should validate authentication, return success promptly, tolerate duplicate delivery, and process longer work asynchronously.
Select an existing webhook in Moxie to inspect recent request and response payloads. A 4xx response disables the webhook so repeated invalid requests do not continue; HTTP 410 removes an endpoint that reports it is gone. Correct the endpoint or authentication before enabling it again.
For the current event catalog, payload schemas, and examples, use the generated Webhooks & Events documentation.