Finding Your Webhook Endpoint URL
What is the Forward URL?
When a webhook arrives at Skooh, we forward it to a URL on your local machine or internal network. This URL points to an endpoint in your application that's designed to receive and process webhooks.
stripe.com → api.skooh.io/hook/abc123 → http://localhost:3000/api/webhooks/stripeWhat are Webhooks?
Webhooks are HTTP callbacks that allow external services to notify your application when events occur. Instead of your application constantly polling an API to check for updates, the external service sends a POST request to a URL you provide whenever something happens.
For example, when a customer makes a payment in Stripe, Stripe sends a webhook to your application with details about the payment. Your application can then process this information, update your database, send confirmation emails, or trigger other business logic.
Webhooks are commonly used for:
- Payment processing (Stripe, PayPal)
- Version control events (GitHub, GitLab)
- E-commerce order updates (Shopify, WooCommerce)
- Communication platforms (Slack, Discord)
- Enterprise software integrations (Salesforce, SAP, Confluence)
Finding Your Endpoint
The best way to find your internal webhook endpoint is to speak with your engineering team or internal software provider. They can tell you the exact URL where your application expects to receive webhooks.
For enterprise software like Confluence, SAP, or Salesforce, check your system's webhook configuration documentation or contact your system administrator. These systems often have specific requirements for webhook endpoints.
Tip: If you're working with Confluence Data Center, Salesforce, or other enterprise platforms, your IT team will know the correct webhook endpoint URL. These systems typically require specific authentication and endpoint formats.
Common Issues
❌ "Connection refused" error
Your application isn't running, or it's running on a different port. Make sure your dev server is started and check the port number.
❌ 404 Not Found
The URL path is wrong. Double-check the exact path in your route definitions. Watch out for trailing slashes—some frameworks require them, others don't.
❌ 405 Method Not Allowed
The endpoint exists but doesn't accept POST requests. Webhooks are always POST requests—make sure your handler accepts them.
❌ 403 Forbidden / CSRF Error
Your framework's CSRF protection is blocking the webhook. Webhook endpoints need to bypass CSRF checks since they come from external services.