Webhooks

Use webhooks when you want to send Reonic events into a homegrown system, a BI pipeline, or any endpoint that can receive a signed request. Reonic offers two options: a simple webhook that fires on every new request, and an event-subscription webhook that lets you subscribe to a range of project, offer, and contact events with signed payloads and automatic retries. For no-code automations and for pulling data on demand, see the Zapier and REST API guides.

Who this is for

Admins wiring Reonic events into their own system, a BI pipeline, or any endpoint that can receive a signed request.

Before you start

• You need admin rights in your Reonic workspace.
• A publicly reachable HTTPS endpoint you control, plus the ability to verify a signed request.
• Webhook configuration lives on Settings > API / Developers > Webhooks, not Settings > Company settings > Integrations.

Configure the request webhook

The request webhook sends a message once, when a new request is created.

1. Open Settings > API / Developers > Webhooks.
2. Find the Webhook on request section.
3. Toggle it on.
4. Paste your HTTPS endpoint URL into the URL field.
5. Save. The configuration is active immediately.
6. Copy the shared secret shown on the page and configure your endpoint to verify incoming requests with it.

Reonic now sends a message to your URL each time a request is created.

What the request payload contains

Each request payload carries the details a new lead submitted, including:

• Contact details: first name, last name, email, phone, and a note.
• The address: country, postcode, city, street, and street number.
• The product packages the customer selected, where they chose any (solar, storage, EV charger, heat pump).
• Which systems the customer already has, where they apply (existing solar, heat pump, storage, EV charger, or electric vehicle).
• A unique request ID and a deep link that opens the request back in the Portal.

Pro tip: Test the setup by creating a test request in Reonic and watching your endpoint receive the message. You can also check the delivery on the Webhooks page under Settings > API / Developers.

Note: To pause without disconnecting, clear the URL field. The shared secret is preserved. Re-paste the URL to resume.

Configure event subscriptions

Reach for event subscriptions when you need more than the request-created event, or when you want signed payloads with automatic retries. You register one HTTPS endpoint, subscribe to the events you care about, and Reonic delivers signed JSON whenever one fires.

1. Open Settings > API / Developers > Webhooks and go to the event-subscription section.
2. Enter your HTTPS endpoint URL. It must be publicly reachable.
3. Select the event types you want to receive.
4. Save. Reonic generates a signing secret for your subscription.
5. Copy the signing secret and use it to verify the signature on each incoming message.
6. Use Send test event to fire a sample payload at your endpoint and confirm it arrives.

The events you can subscribe to cover:

• Projects created — for residential and commercial projects.
• Pipeline changes — when a project moves to a different board column or changes deal state.
• Offer signatures — when a residential offer signature is requested, signed, or withdrawn.
• Checklist progress — when a project checklist segment changes completion.
• Contact created.

Note: Offer signature events apply to residential offers. Commercial offers are signed in person rather than through the digital signature flow, so they do not raise an offer-signed event.

How event subscriptions deliver and sign

• Lightweight payloads. Each event payload is a small envelope that carries IDs rather than full records. When you receive one, fetch the current state from the Reonic REST API. The webhook tells you that something changed; the API tells you what it now is.
• Signed deliveries. Reonic signs every delivery, and the message carries the event type, an event ID, a delivery ID, and a timestamp. The event ID stays the same across retries of the same event, so you can use it as your idempotency key.
• Automatic retries. If a delivery fails, Reonic retries it automatically several times over the following days. If every attempt fails, Reonic pauses the subscription and emails your contact. Re-enable it once your endpoint is healthy again.

The delivery log

Event subscriptions keep a self-serve delivery log covering recent deliveries. Open a delivery to see the response, the payload, and a manual Retry action. Use it to confirm deliveries landed and to replay a single event.

Things to know

• The request webhook fires on request creation only. It does not fire on later updates. For more event types, or for signing and retries, use event subscriptions. For state after creation, pull from the Reonic REST API (see the REST API guide).
• Build idempotency on your side. The request webhook does not replay failed deliveries for you, so design your endpoint to handle a delivery it has already seen. Event subscriptions retry for you.
• Webhooks, Zapier, and a connected CRM run in parallel. They are independent. If you have configured all three, every request creation reaches all three destinations.
• Per-call audit trail. Every delivery lands in your integration logs with the integration type, status, and timestamp, visible under Settings > Company settings > Integrations.
• Verify the signature on every message. Validate each delivery against the secret shown on the Webhooks page so you accept only genuine Reonic deliveries.

Need help?

• Step-by-step questions about this flow → contact your Reonic account manager.
• Feature requests or something missing → drop a note to your account manager.
• Bug reports → include a screenshot and the URL where it happened in your support email.

Last updated on August 4, 2026