Signed endpoints
Event filters, extra headers and a signing secret per endpoint, rotated without downtime.
Every event delivered, or a clear reason why not
Deliver your app's events to customers' endpoints, signed, logged and retried until they arrive.
Each domain keeps event types (name, description, sample payload; an unknown type registers itself on its first event), consumers (a customer by the business's own id, or one of its own apps) and their endpoints: public https URLs only, event filters with * wildcards, extra headers, on or off, and a whsec_ signing secret per endpoint, rotated with 24 hours of two signatures. Requests are signed per the Standard Webhooks spec (webhook-id, webhook-timestamp, webhook-signature v1 HMAC-SHA256). POST /api/v1/events (secret key) takes a type, data, an optional consumer and an idempotency key, with a payload limit and a rate limit per domain, and fans out to every matching endpoint. The first try goes at once with an inline 5-second retry, then a cron every minute retries at 5 minutes, 30 minutes, 2, 5 and 10 hours (eight tries), logging each attempt's status, the first 2 KB of the answer, duration and error. An endpoint that keeps failing for the domain's set number of days is turned off, with emails to the team and the consumer. Retry one delivery, replay a message, recover everything failed since a time, or send a test event. Consumers manage their own endpoints and see their delivery log at /portal/<token> in the domain's brand, after an email code or a one-time grant from the API. Verification snippets for Node, Python and PHP on /guide, and Claude to explain a failing endpoint from its recent attempts.
What Webhooks does for you.
Event filters, extra headers and a signing secret per endpoint, rotated without downtime.
Retries with backoff, an attempt log, replay, recovery and auto-disable for endpoints that keep failing.
Each consumer adds endpoints and reads their own delivery log on a branded page.
A suggested path for Webhooks. What you can do depends on your access in the app.
Add event types with a sample payload, or let the first event register its type.
Create a consumer and its endpoints, or send them their portal link.
Call POST /api/v1/events and watch the attempts.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain keeps event types (name, description, sample payload; an unknown type registers itself on its first event), consumers (a customer by the business's own id, or one of its own apps) and their endpoints: public https URLs only, event filters with * wildcards, extra headers, on or off, and a whsec_ signing secret per endpoint, rotated with 24 hours of two signatures. Requests are signed per the Standard Webhooks spec (webhook-id, webhook-timestamp, webhook-signature v1 HMAC-SHA256). POST /api/v1/events (secret key) takes a type, data, an optional consumer and an idempotency key, with a payload limit and a rate limit per domain, and fans out to every matching endpoint. The first try goes at once with an inline 5-second retry, then a cron every minute retries at 5 minutes, 30 minutes, 2, 5 and 10 hours (eight tries), logging each attempt's status, the first 2 KB of the answer, duration and error. An endpoint that keeps failing for the domain's set number of days is turned off, with emails to the team and the consumer. Retry one delivery, replay a message, recover everything failed since a time, or send a test event. Consumers manage their own endpoints and see their delivery log at /portal/<token> in the domain's brand, after an email code or a one-time grant from the API. Verification snippets for Node, Python and PHP on /guide, and Claude to explain a failing endpoint from its recent attempts.
Business automations belong to Workflows; cron jobs belong to Scheduling; the business's own alert webhook stays in each catalog's settings.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
webhooks.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.