Hi SimplyBook.me team,
I would like to clarify the webhook behaviour when staff manually confirm payment of an existing remaining-balance invoice.
Example scenario — hypothetical amounts:
- A booking has a total price of 100.
- The customer pays a deposit of 40, and the booking is confirmed.
- SimplyBook.me creates a separate remaining-balance invoice for 60, which remains unpaid.
- Later, staff open that existing balance invoice under Payment Transactions → Receive payment, select Cash or Wire transfer, and confirm receipt.
The goal is to notify an external system when step 4 occurs, so it can retrieve the invoice through the API and update its payment records.
Could you please clarify:
- Does this action trigger the
new_invoiceREST webhook, subscribed to throughPOST /admin/webhooks, even though the balance invoice already existed? - Does it trigger the legacy booking
changecallback or the RESTchange_bookingevent? - If an invoice webhook is sent, does it identify the balance invoice, rather than the original deposit invoice? A sample payload using dummy data would be helpful.
- When the notification arrives, are
payment_received, the payment method and payment timestamp already updated inGET /admin/invoices/{id}, or might a short delay be necessary? - Is the behaviour the same for manual Cash and Wire transfer confirmations?
- If these events do not cover this scenario, is there another officially supported webhook available directly to an external backend, or is polling recommended?
The documentation describes “New Invoice” as firing when an invoice is created and paid. This question specifically concerns manually settling an existing balance invoice after the deposit has already been paid, rather than the initial booking confirmation or deposit payment.
Please distinguish between SimplyBook.me REST webhooks, the legacy booking callback, and any separate SBPay.me/Zapier events.
This is a general API behaviour question; no account-specific investigation is requested.
Thank you!