Get signed HTTPS requests from Base44 when an app in your workspace changes or the AI finishes working on a message, without polling for it.
Outbound webhooks send a signed HTTPS request to your service when an app in your workspace changes, or when the AI starts or finishes working on a message. Instead of polling for new or updated apps, your system hears about each change as it happens, including deletes.Use outbound webhooks to:
Keep your own records in sync when apps are created, published, taken offline, moved to trash or restored.
Start your own workflows when an app goes live.
Know when the AI has finished working on a message you sent, without polling.
Build a platform on Base44 that reacts to what your customers do in their workspaces.
Outbound webhooks are available on the Business and Enterprise plans.
You register an HTTPS URL, called an endpoint, and choose the events it receives. Base44 then sends each matching event to that URL as a JSON POST.
Register an endpoint. In your workspace settings, or with a workspace API key. See Setting up endpoints.
Activate it. Base44 sends a signed webhook.test.v1 event, and your receiver returns its data.challenge value. When you register with the API, this happens in the same call. Until then the endpoint stays Pending and receives nothing.
Verify each request. Every request is signed with your workspace’s Ed25519 key. See Verifying requests.
Handle retries. Delivery is at least once, so the same event can arrive more than once. See Delivery and retries.
Each request body is a CloudEvents 1.0 JSON document, signed with the Standard Webhooks headers. The data object carries identifiers, timestamps and fixed status values only, never app content or personal data.