Mosce ERP · Help Center
Webhooks

Set up a webhook

How to register a webhook endpoint in Mosce ERP: HTTPS URL, event selection, signing secret and connectivity verification.

Webhooks let Mosce ERP notify your external systems in real time each time a relevant event occurs - an invoice issued, a payment recorded, a backup completed. This article covers registering the first endpoint and verifying that the connection works.

Reading time: ~7 min

When to use this

  • You want to integrate Mosce ERP with an external system (ERP, CRM, automation platform) that needs to receive events in real time.
  • You are going to connect Mosce ERP with an automation tool like n8n, Zapier or Make.
  • You need to trigger custom logic on your server every time an event occurs in Mosce ERP.

Before you start

  • You need the tenant:webhook permission to create and manage webhooks.
  • Webhooks are available starting with the Starter plan. The free plan does not include webhook access.
  • Your endpoint must be a publicly accessible HTTPS URL. URLs with http:// or that resolve to private IP addresses are not accepted.
  • Prepare your receiving server before registering the endpoint - that way you can verify connectivity immediately after registration.
Module / FeatureFreeStarterProfessionalEnterprise
e-CF invoicing (DGII)
Inventory
Batch inventory adjustment-
Point of sale (POS)
Tasks (Kanban)-
Sales commissions-
Double-entry accounting--
Advanced reports--
Outgoing webhooks-
Data tools--
XLSX export--
Backups--
API access--
E-commerce---

Step 1 - Go to the webhooks settings

  1. From the Mosce ERP main menu, go to Settings → Integrations → Webhooks.
  2. Click New webhook.

Step 2 - Configure the endpoint URL

  1. In the Endpoint URL field, enter the HTTPS URL of your receiving server.
  2. Mosce ERP validates that the URL starts with https://. URLs that resolve to private or loopback IPs are rejected for security reasons.
  3. Optionally, add a descriptive name to identify the webhook in the list (for example: "Production - ERP", "Staging - tests").

Step 3 - Select the event types

Mosce ERP has a catalog of more than 40 events organized by category:

CategoryEvent examples
Salesinvoice.created, invoice.paid, invoice.overdue, order.created, quote.accepted
Purchasespurchase_invoice.created, purchase_order.received
Paymentspayment.created, payment.deleted
Inventorystock_movement.created, low_stock.triggered
POSpos_session.opened, pos_session.closed
Customerscustomer.created, customer.updated
Fiscalfiscal_document.submitted, fiscal_document.accepted, fiscal_document.rejected
Backupsbackup.completed, backup.failed
Accountplan.upgraded, usage_limit.reached
Data toolsdata.export.completed, data.import.completed

The Data tools events are delivered when an asynchronous export or import job reaches its final state (completed, failed or cancelled). The payload includes a signed URL valid for 60 minutes: downloadUrl for exports and errorReportUrl for imports with invalid rows. If the URL expires, your integration can regenerate it with a GET to the job endpoint.

Select only the events your system needs. Subscribing to unnecessary events increases the delivery volume without benefit.

Step 4 - Save and copy the secret

When you save the webhook for the first time, Mosce ERP generates a unique signing secret for this endpoint. The secret is shown only once - copy it and save it immediately in your password manager or in your server's environment variables.

The signing secret cannot be recovered after closing the dialog. If you lose it, you will have to rotate it from the webhook management screen. See Security and signature verification.

Step 5 - Verify connectivity

After saving the webhook, use the Test endpoint button to send a test event to your server and verify that the connection works correctly. The result shows the HTTP response code and the latency in milliseconds.

See Test a webhook for the full detail of the test flow.


Modify or delete a webhook

  • Edit: click the webhook in the list and modify the URL, the name or the event subscriptions. Changes apply immediately.
  • Pause: you can temporarily deactivate a webhook without deleting it. Deliveries are skipped while it is paused.
  • Delete: when you delete a webhook, all associated delivery records are deleted as well.

Common errors

SymptomLikely causeSolution
The URL is rejected on saveThe URL uses http:// or resolves to a private IPChange to an https:// URL with a public domain name
The webhook stays in "Disabled" stateConsecutive failed deliveries accumulatedSee Reliability and retries for the re-enable process
I do not receive events even though the webhook is activeThe event is not in the subscription listEdit the webhook and add the corresponding event type
The secret disappearedIt is only shown once when creating or rotatingRotate the secret from the webhook screen and copy the new one immediately

Frequently asked questions

How many webhooks can I have?

The maximum number of webhook endpoints depends on your plan. See Billing and subscription or the pricing page to see your plan's limit.

Can I have the same event on more than one webhook?

Yes. You can have multiple endpoints subscribed to the same event. Mosce ERP delivers the event to all active endpoints subscribed to it.

Do webhook deliveries count toward my monthly quota?

The first delivery attempt of each event counts toward your monthly webhook delivery limit. Automatic retries after a failure are not counted twice. See Usage limits.

What happens if my server is down when an event arrives?

Mosce ERP retries the delivery automatically up to 10 times over 24 hours. See Reliability and retries for the retry schedule.


Last updated: 2026-05-09