Can an endpoint be tested before it goes live?
Activation requires one successful test. Your merchants pick a trigger, the platform sends the matching synthetic payload using the exact signing logic of production deliveries, and an HTTP 2xx response confirms the endpoint accepts the request. The result shows the status badge, the full request preview with headers and payload, the response body, and the recent calls with their signatures. The test confirms reachability and acceptance, and business processing inside the receiving system remains yours to validate.
In detail
Yes, and a test is required. Every webhook endpoint starts in Draft, and activation needs one successful test before the endpoint can go live.
Your merchants pick a trigger, and the platform sends the matching synthetic payload to the configured URL, signed with the exact logic used for production deliveries. An HTTP 2xx response confirms that the endpoint accepts the request, and the endpoint can then move to Active.
What the test result shows
- A status badge for the outcome.
- The full request preview, with headers and payload.
- The response body returned by the receiving system.
- The recent calls, with their signatures.
That gives the integrating team everything needed to fix a failing endpoint without opening a ticket: a wrong URL, a firewall rule, a signature check that does not match or a parser that rejects a field.
Once Active, an endpoint can be tested again at any time without interrupting live deliveries, which is useful after a change on the receiving side. The test confirms reachability and acceptance. Business processing inside the receiving system, such as updating an order or posting an accounting entry, remains for the integrating team to validate with its own checks.