Skip to main content

Webhooks & Integrations

Rentstuff can automatically notify external systems of events via webhooks. When something happens in the system, Rentstuff sends an HTTP POST request to your specified URL with the relevant data.

Quick Overview​

Via Settings → Webhooks you register one or more webhook endpoints. Per endpoint you choose which event types are forwarded. On delivery failures, Rentstuff stores a delivery log and automatically disables an endpoint after 20 failed attempts.

Getting Started — Adding a Webhook​

  1. Go to Settings → Webhooks.
  2. Tap + to add a new endpoint.
  3. Enter the URL of the external system (e.g. a Make.com webhook, a Zapier trigger or your own server).
  4. Optionally add a secret. This secret is sent as an X-Webhook-Secret header so you can verify the request genuinely comes from Rentstuff.
  5. Select the event types this endpoint should receive.
  6. Tap Save.

The endpoint is immediately active.

Available Event Types​

EventTrigger
order.createdNew order or quote created
order.confirmedOrder confirmed (from Quote to Confirmed)
order.status_changedAny other order status change
order.cancelledOrder cancelled
quote.accepted_by_customerCustomer accepts a quote in the portal
invoice.createdNew invoice created
invoice.paidInvoice fully paid
invoice.overdueInvoice overdue (payment term expired)
damage_report.openedNew damage report created
damage_report.status_changedStatus change of a damage report
stock_item.damagedDamage report created for a stock item
stock_item.status_changedStatus change of an individual stock item
customer.createdNew customer created
payment.registeredPayment registered on an invoice

Webhook Payload​

Each webhook request has the following structure:

{
"event": "order.confirmed",
"company_id": "abc-123",
"occurred_at": "2026-04-15T14:23:00Z",
"data": {
"id": "order-uuid",
"order_number": "ORD-2026-0042",
"status": "confirmed",
"customer_name": "Example Ltd",
...
}
}

Rentstuff sends a Content-Type: application/json header and expects an HTTP 200 OK response within 10 seconds.

HMAC Signing​

In addition to the optional secret, Rentstuff also offers HMAC signing for webhooks. Each webhook request includes the header:

X-Rentstuff-Signature: sha256=<hmac>

The HMAC is computed over the raw JSON body using the endpoint's secret (SHA-256). Verify the signature on your side to confirm the request is authentic and has not been tampered with:

import hmac, hashlib

def verify(payload_body: bytes, secret: str, signature_header: str) -> bool:
expected = "sha256=" + hmac.new(
secret.encode(), payload_body, hashlib.sha256
).hexdigest()
return hmac.compare_digest(expected, signature_header)
Always verify the signature

Only process webhook requests whose signature is valid. This prevents malicious parties from injecting fake events.

Delivery Log​

Every webhook attempt is logged in the delivery log:

  • Successful: HTTP 2xx received within the timeout
  • Failed: connection error, timeout or HTTP 4xx/5xx response

The delivery log is visible via Settings → Webhooks → [endpoint] → Deliveries. Per attempt you see the date, HTTP status code and the full response body (useful for debugging).

Automatic Disable

After 20 consecutive failed deliveries the webhook endpoint is automatically disabled. You receive a notification in the app about this. Fix the cause of the errors and then manually re-enable the endpoint.

SSO Integrations​

For SSO configuration (SAML or Office365/Azure AD) see Settings → SSO. Both protocols are supported and can be configured per company. SSO only applies to staff logins.

Setting Up SAML​

  1. Go to Settings → SSO → SAML.
  2. Enter the IdP metadata: entity ID, SSO URL, the IdP certificate.
  3. Set the attribute mapping (how SAML attributes are translated to Rentstuff fields).
  4. Activate the SAML integration with the toggle.
  5. Share the SP metadata URL with your IdP: https://api.rentstuff.io/auth/sso/saml/{company_slug}/metadata.

Setting Up Office365​

  1. Go to Settings → SSO → Office365.
  2. Enter your Azure AD tenant ID, client ID and client secret.
  3. Set the allowed email domains.
  4. Activate the integration.
  5. Use the Test connection button to verify the credentials are correct.
Auto-Provisioning

With both SSO methods you can enable "Auto-create". New staff members who log in via SSO but don't yet have a Rentstuff account are then automatically created with the default role.