Test a webhook

Before waiting for a real event, Mosce ERP lets you send a test payload to your endpoint and see the result synchronously: HTTP response code, latency and any error message. This article covers the test flow and how to use the delivery history to diagnose problems.

Reading time: ~4 min

When to use this

• You just registered a webhook and want to confirm that your server receives events correctly.
• You changed the endpoint URL or the server and want to verify the new configuration.
• A webhook failed and you want to diagnose what is happening without waiting for the next real event.

Before you start

• You already have a webhook configured with an HTTPS URL. See Set up a webhook.
• Your receiving server is active and listening on the registered URL.
• You need the tenant:webhook permission.

Step by step - send a test

Step 1 - Open the webhook

1. Go to Settings → Integrations → Webhooks.
2. Click the webhook you want to test.

Step 2 - Use the "Test endpoint" button

1. On the webhook detail screen, click Test endpoint.
2. Mosce ERP immediately sends a test payload to your URL and waits for the response.
3. The result appears on screen in less than 10 seconds.

Step 3 - Interpret the result

The test result shows:

Successful result: code 200 (or any 2xx) with low latency. Your endpoint is correctly configured.

Failed result: review the common errors section below.

The test payload

The test event has type webhook.test and a minimal payload:

{
  "type": "webhook.test",
  "timestamp": "2026-05-09T14:30:00Z",
  "data": {
    "message": "This is a test event from Mosce ERP"
  }
}

The payload includes the same headers as a real event, including X-Helix-Signature with the correct signature. You can verify the signature on your server during the test - if verification fails for the test event, it will also fail for real events. See Security and signature verification.

Your server must respond with HTTP 2xx for the test to be marked as successful. If your server rejects the test event (for example, because it filters by event type), return 200 anyway and handle the logic internally.

Delivery history

The delivery history shows the latest deliveries of this webhook, with the status and details of each attempt.

To view the history:

1. Open the webhook from Settings → Integrations → Webhooks.
2. Click Delivery history.

The history shows the last 10 deliveries by default. You can filter by state (pending, delivered, failed, exhausted) to find the deliveries you need to review.

For each delivery in the history you can see:

• The event type.
• The timestamp of each attempt.
• The response code of each attempt.
• A Resend button to retry the delivery manually.

Common errors

Frequently asked questions

Does the test consume my monthly delivery quota?

No. Test events (webhook.test) are not counted toward your monthly webhook delivery limit.

Can I choose which event type is sent in the test?

No. The test event type is fixed (webhook.test). To test the behavior with a specific event type (e.g. invoice.created), create a real document in your account and observe the delivery in the history.

Does the test payload include real data from my account?

No. The test payload is synthetic and does not contain real data from invoices, customers or other records in your account.

How often can I use the test button?

There is no explicit limit on tests per day. However, tests are recorded in the history and count toward the endpoint's availability analysis.

Related

• Set up a webhook
• Security and signature verification
• Reliability and retries

Last updated: 2026-05-09