Public Hook Pages
Public hook pages let each FastHook endpoint have a shareable public page with sanitized request examples, payload structure, and integration notes.
A public hook page is useful when developers, partners, or support teams need a stable reference for how a webhook endpoint should be called. Instead of copying request examples into scattered docs, you can share one page with the endpoint URL, expected payload shape, and a realistic test request.
Public hook pages also help during onboarding and debugging. They give teams a lightweight way to explain an integration without exposing the full dashboard or internal operational tooling.
stripe
Stripe Billing Events
Public Stripe webhook example endpoint with realistic invoice and payment events.
https://hook-xxxxxx.fasthook.io/
github
GitHub Push and PR Events
GitHub webhook payload example for push and pull_request automation pipelines.
https://hook-xxxxxx.fasthook.io/
generic
Generic Webhook Testing Endpoint
Generic webhook request example endpoint for testing custom providers and local integrations.
https://hook-xxxxxx.fasthook.io/
How to use public hook pages
Use a public hook page when you need to document a webhook integration, share a safe testing example with a customer, or hand another team the exact endpoint contract they should call. The combination of endpoint, sample request, and payload context makes integration work less error-prone.
Public hook pages work especially well for Stripe, GitHub, internal event producers, and one-off partner integrations where a short, human-readable reference page is more useful than a full API spec.