Skip to main content

Webhooks for integrations, generated reports kept for 30 days and "Paid for" in the wallet

· 4 min read
Venelin Iliev
Venelin Iliev
Founder & CTO @ Reservation.Studio

Webhooks for integrations, generated reports kept for 30 days and "Paid for" in the wallet

Under "Integrations" you add a webhook address, and your external system receives the events about appointments and clients the moment they happen. Generated reports are kept for 30 days, and the wallet shows what each deposit and payment was for.

✨ In brief​

  • Webhooks: an address for your integration, a choice of events, a test event, the sending history and a button to send again.
  • Generated reports: files are kept for 30 days and then deleted automatically.
  • Wallet: a "Paid for" column in "Deposit History" and "Recent payments".
  • Invoices: the line for a deposit says whether it is for a plan or for notifications.

Webhooks for your integration​

A webhook lets an external system, for example a CRM or your own app, learn about a change in Reservation.Studio the moment it happens, instead of asking all the time. It needs a subscription that includes "External Connectivity".

How to add an address​

  1. Open "Integrations", choose "Settings" on the "Webhooks" card, then "New webhook address".
  2. Fill in "Name" and "Address (URL)" and choose at least one event under "Events".
  3. In "Email for notifications" enter who should get a message if the address is stopped.
  4. Choose "Create" and copy the "Webhook secret". It is shown only once: the integration uses it to check that the events come from Reservation.Studio.

Which events are sent​

  • Appointments: "Appointment created", "Appointment changed", "Appointment deleted" and "Appointment restored".
  • Participants: "Client joined", "Client status changed" and "Client removed".
  • Clients: "Client created" and "Client changed".

An event says what happened and for which record. The integration reads the full data from the API with an API key.

Test, history and a new secret​

  • "Send test event" in the row menu shows what the server of the integration answered.
  • "Sending history" shows every sending. When an event did not arrive, its details have "Send again".
  • "Generate new secret" in the row menu creates a new secret and shows it once. The current secret stops at once, so put the new one into the integration.

When an address is stopped​

The address is stopped automatically when the server answers that the address no longer exists (410 Gone), or when every sending to it fails for 3 days. A message goes to "Email for notifications", or, if that field is empty, to the employee who created the address.

In detail, with the headers and the signature for the developer: Webhooks.

How long generated reports are kept​

Above the list in "Download generated reports" it says: "Generated files are kept for 30 days, then deleted automatically." After that period the file and its row in the list disappear.

note

Download the files you need before they are 30 days old. If you need a deleted report, request it again from the report you generated it from.

In detail: Download generated reports.

Wallet: what each payment was for​

  • "Deposit History" has a "Paid for" column with a "Subscription" or "Notifications" label.
  • "Recent payments" shows "Number", "Date & Time", "Paid for", "Quantity" and "Price".
  • In "Deposit History", a deposit with no recorded purpose shows a dash.

The line on the invoice​

The invoice for a deposit says what it was for, for example "Tariff plan — wallet top-up of 3 November 2026" or "Wallet top-up for notifications of 3 November 2026". When no purpose is recorded, the line is "Wallet top-up of 3 November 2026". This is how invoices issued from now on read. Invoices already issued do not change.

In detail: Wallet and Invoices.