Outgoing webhooks API reference

Outgoing webhooks let UnSpot notify your systems about events in real time: UnSpot sends an HTTP POST with a JSON payload to a URL you configure. Typical use case: passing parking bookings to a security or gate-control system.

Setting up a webhook

Go to Administration > Integrations > Webhook and create a webhook with a name, target URL, an event, and the offices it applies to. Only events from the selected offices are delivered. A webhook with the same event and URL cannot be created twice.

Events

HTTP (API-type) events:

Additionally, email-type notifications can be configured for: user access requests, user created/deleted, tariff warnings, system sync warnings, expired space rent, and display errors. These are sent to email addresses instead of a URL.

Payload format

All parking events share the same base payload; action tells them apart:

POST <your URL>
Content-Type: application/json

{
  "fullName": "Jane Doe",
  "email": "jane.doe@example.com",
  "vehicleNumber": "AB-123-CD",
  "vehicleModel": "Tesla Model 3",
  "start": "2026-07-08T09:00:00+00:00",
  "end": "2026-07-08T18:00:00+00:00",
  "office": "HQ Berlin",
  "parkingPlace": "P-12",
  "action": "Created",
  "bookingType": "Parking"
}

Delivery, timeouts and retries

• Requests are sent as POST with Content-Type: application/json and a 240-second timeout.
• Respond with any 2xx status to acknowledge delivery.
• Failed deliveries increment a failure counter; delivery is retried by the queue. After 100 consecutive failures the webhook is switched to the failed status and administrators are notified. A successful delivery resets the counter.
• Webhook health is visible in External API > monitoring (webhooks category) and in the Integrations page.

Security recommendations

• Standard webhook requests carry no authentication header — treat the endpoint URL as a secret: use HTTPS and include a random path segment (e.g. https://example.com/hooks/unspot-8f3a91).
• Validate the payload structure and restrict your endpoint to expected fields.
• For the Claris integration, UnSpot sends its own Authorization: Bearer token and an extended payload — enable the Claris option only for that system.

For a practical walkthrough of the parking use case, see Outgoing Webhooks: Parking place booking notifications.