Create a relay project and Herosite will generate a callback URL like https://herosite.win/webhook/your-project. Meta verifies that URL once, Herosite validates signatures, stores the receipt in the shared event database, and forwards the raw payload to up to five configured destinations.
This page lives at /webhook, so the homepage card can point here exactly as requested.
Yes. Herosite currently forwards the same payload to every destination configured on that relay project.
Not in this product yet. Conditional routing is not implemented in the MVP.
No. There is no mapping table in this version. Configuration is project-wide.
Meta verifies Herosite’s callback URL with the verify token you enter for the project. Destination URLs are not part of Meta’s GET verification.
Yes. Herosite validates incoming signatures with the project’s App Secret and forwards the original request headers except transport headers that must be regenerated.
No. Herosite forwards the raw request body unchanged.
This MVP records failures in logs but does not implement automatic retries or manual replay yet.
The dashboard shows webhook receipts, payload preview, destination URLs, response status codes, and failure messages.
The MVP stores webhook receipts in the shared event database and keeps a short payload preview in local log files for debugging.
Use it only if both platforms are allowed to receive the same payload and safely ignore unrelated events. Strict isolation needs a routing product, not this relay.
Create an account, open the dashboard, create a relay project, and manage billing through the Stripe buttons in the same dashboard.
Herosite is still a raw relay product. It does not inspect phone_number_id to split traffic. That must happen in downstream apps, or you need a different routed product.
Callback URL format
https://herosite.win/webhook/<project-slug>
Also accepts https://herosite.win/webhook/<project-slug>/webhook.