What this screen is for
Each supported service is listed with the exact URL it should send to, the HTTP method, and the events it will deliver - for example delivery status updates for e-invoices, or payment and refund outcomes from a payment provider. A copy button puts the address on your clipboard, and a documentation link opens the provider own reference.
When to use it
Come here while setting up an external service, and paste the URL into that service dashboard. Until that step is done the service has nowhere to report back to, so statuses in this app stay at whatever they were when the request was first sent, with no error to explain it.
What you see on this screen
Five entries, each a card with its name, what it does, the URL to paste, a copy button and a documentation link.
Storecove PEPPOL receives delivery status updates for PEPPOL e-invoices sent through the Storecove access point, carrying document_submitted, document_delivered, document_failed and document_received.
Razorpay Payments receives payment status updates, carrying payment.captured, payment.failed and refund.created.
Stripe Payments receives payment and subscription events, carrying payment_intent.succeeded, invoice.paid and customer.subscription.updated.
Google Calendar receives calendar change notifications, carrying calendar.events.changed and calendar.events.deleted.
Third Party Integrations is a single dynamic endpoint for connected integrations, where the provider code is part of the address - tally, whatsapp, zapier, slack and so on.
A Security Information panel states how incoming calls are handled: endpoints use signature verification where the provider supports it, webhook secrets are stored securely and never appear in a URL, every incoming request is logged for audit, and rate limiting is applied.
Filters and actions
There is no search, filter or export - the list is fixed. Each card offers Copy URL and Docs, and the dynamic integrations card adds a Configure link into the integrations screen.
Related
- Payment Gateways - the payment side of these callbacks
- Third Party Integrations - the outbound direction
- API Keys - credentials for calling in the other way