Skip to main content
Create or update a noise threshold, then verify that its event reaches your application.

Set Up Noise Thresholds

For Minut, list existing thresholds first. If builtin_quiet_hours already exists, update it instead of creating another quiet-hours threshold. Create a threshold using the Create a Noise Threshold endpoint. For example: Request:
The JavaScript SDK returns the created noise threshold. The HTTP response also includes an action attempt. See the current response schema and confirm the threshold with List Noise Thresholds. The example sets a 70-decibel threshold from 20:00 to 06:00 in America/Los_Angeles, including daylight saving changes. Once you have created a threshold, connect it to a webhook to log events.

Best Practices

  • For Minut devices, you can configure two thresholds—one for quiet hours and one for the rest of the day.
  • For NoiseAware devices, you can configure as many thresholds as you want, provided that they do not overlap during daytime hours.

Set Up Webhooks

You can set up webhooks in the Seam Console.
  1. In the left-hand navigation pane of Seam Console, click Webhooks.
  2. On the Webhooks page, click + Add Webhook. On the Webhooks page in the Seam Console, click + Add Webhook.
  3. In the Create Webhook dialog:
    1. Type your URL.
    2. Select the event types for which you want to receive events.
    3. Click Create.
The Seam Console displays the URL and secret for the newly-created webhook. To test your webhook, click Test your webhook.

Monitor Events

Subscribe to noise_sensor.noise_threshold_triggered. The signed event includes event_id, workspace_id, device_id and occurred_at; read it from the verified webhook payload. Do not treat an entry in the event list alone as proof that your application received it. For a detailed reference of event parameters, see Events. For a receiver that verifies signatures and stores one alert per event across restarts, continue with Receive and store an alert. In a sandbox workspace, simulate a threshold event to test the receiving path. This does not test acoustic detection on a physical sensor.