Skip to main content
If you provide machines on Vast.ai, host notifications keep you informed about machine health, verification, renter reports, and maintenance. You can receive them by email or through webhooks that feed your own monitoring and incident systems. The notification system is shared across the web console and the API. The console gives you a settings page for choosing events and destinations. The API gives developers access to the same notification types, preferences, and webhook tools.
This page covers host notifications. For renter events such as low balance and instance lifecycle, see Notifications.

​
Where to Find Notification Settings

Open Account Settings and go to Notification Settings. Host events appear only when you provide machines on Vast.ai. The Host group covers:

​
How Delivery Works

Each notification type can be delivered over one or more channels: Some emails are mandatory because they are tied to account access, billing protection, or imminent service disruption. Mandatory email notifications cannot be fully disabled from the settings page.
Email and webhook preferences are set per notification type.

​
Update Host Notifications in the Console

  1. Open Account Settings.
  2. Go to Notification Settings.
  3. Review the Host section.
  4. Turn off email for any optional event you do not want in your inbox.
  5. Select host events that should be sent to a webhook, then create or edit the webhook destination.
  6. Click Save.

​
Route Host Alerts to a Webhook

Webhooks are useful for turning host alerts into actions, such as paging an operator when a hosted machine fails verification or goes offline, or routing host machine alerts into your monitoring stack. A common host action mapping points each host event at its machine in the console, for example: See Notification Webhooks for setup, payloads, signing, retries, and API examples.

​
Notification Type Keys

Notification types are identified by a key with a context prefix. Host events use the host: prefix, such as host:machine_offline. Use the full key when subscribing webhooks or updating preferences. Because a similar event can exist for both renters and hosts, the full key avoids ambiguity. For the complete list of types, display names, and default channel settings, call GET /notification-types/.

​
Good Defaults

If you are hosting machines, keep machine error, verification, report, maintenance, and low-disk alerts enabled. Review the settings periodically, especially after adding hosted machines or connecting a new automation workflow.