Creating a Webhook Endpoint

Record360 can push notifications to your system whenever an event happens in ours — a new inspection is created, or a task is completed. Subscribing to a webhook lets your integration use an event-based architecture, which is typically simpler and cheaper than polling our API on a schedule. You don't need to constantly check for updates; sit back, relax, and let the data come to you.

Previously, webhooks were configured on your behalf by Record360 support. You can now create and manage webhook endpoints yourself, directly from the Dashboard, through the new Integration Marketplace and its Custom Integrations management experience.

This guide walks through creating a webhook endpoint in the Dashboard. For the full event and payload reference, see Subscribing to Inspection or Task Events.

Before you begin

Before creating a webhook, stand up an endpoint on your side that Record360 can call. Your endpoint should:

• Accept HTTPS POST requests with a Content-Type of application/json.
• Present a valid SSL certificate.
• Return a timely 2xx response to acknowledge receipt.
• Handle high volume gracefully. Inspection volumes are based on your organization's activity and can be large, so enforce a rate limit and return a correct 429 response if you need Record360 to back off.
• Tolerate new schemas. Different workflows produce different checklist fields, and new fields may be added over time. Webhooks follow the same backwards compatibility and versioning policies as the Integration API, so build your consumer to ignore new or unknown fields rather than break on them.

Open the Custom Integrations management page

1. Sign in to the Record360 Dashboard.
2. Select Integrations in the main menu.
3. Under System integrations, select the Custom Integrations card. The card shows your current number of API keys and webhooks, along with recent activity.
4. On the Custom Integrations page, select the Webhooks tab. (API Keys are managed from the neighboring API Keys tab.)

Create a webhook

1. On the Webhooks tab, select New Webhook in the upper right.

   

2. Complete the fields in the create modal (see Webhook fields below).

3. Select Create Webhook.

Your new endpoint appears immediately in the webhooks table and begins receiving event notifications for the event you subscribed to.

Webhook fields

Authentication options & custom headers

Record360 can authenticate to your endpoint using the scheme you configure. To make adding authentication easy, we offer a few preset schemas in addition to any custom headers.

• None — No authentication header is added.
• Basic — Enter a username and password. Record360 base64-encodes them into the Authorization header.
• Bearer token — Enter a token. Record360 sends it as Authorization: Bearer <token>. (no need to add Bearer.)
• API Key — Enter a custom key-value pair, sent as a header.

You can combine any authentication option with additional Custom Headers to match your endpoint's requirements.

Edit a webhook

Select Edit from a webhook's three-dot menu to update it. The edit modal exposes the same fields as creation, with two exceptions:

• Event type cannot be changed. The subscribed event is inherent to the endpoint. To subscribe to a different event, create a new webhook.
• Existing authentication and custom-header values are hidden for security. Re-enter a value only if you want to change it.

Delete a webhook

Company Admins can delete a webhook from its three-dot menu. You'll be asked to confirm before the endpoint is removed.

Need help?

Have questions or run into trouble? See Need help? or reach out to Record360 support.