Outbound webhooks send a signed HTTPS request to your service when an app in your workspace changes. 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.
- 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.
How it works
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 test event, and your receiver echoes back the code it contains. 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.
What each request looks like
Each request body is a CloudEvents 1.0 JSON document, signed with the Standard Webhooks headers. The data object carries identifiers only, never app content or personal data.
For every event type and its fields, see Event types.
Limits
These limits apply to every workspace.