Notifications let you decide which Vast.ai events you want to be told about, and where those messages go. A renter may only need low-balance and instance lifecycle alerts by email. An automated platform can subscribe to the same events through webhooks and route them into its own incident, billing, or orchestration system.
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 renter notifications. If you also provide machines on Vast.ai, see Host Notifications for host machine, verification, and maintenance events. Where to Find Notification Settings
Open Account Settings and go to Notification Settings.
The page groups events by the part of Vast.ai they affect:
| Group | What it covers |
|---|
| Account | Email verification, password resets, email changes, team invitations, and similar account events |
| Billing | Low balance, payment receipts, billing failures, and other payment events |
| Instance | Instance creation, startup, stops, resumes, outbid events, offline/online state, contract end dates, downtime, and disk warnings |
How Delivery Works
Each notification type can be delivered over one or more channels:
| Channel | Use it for |
|---|
| Email | Human-readable messages for events you want in your inbox |
| Webhooks | Machine-readable HTTP events for your own systems |
Email and webhook preferences are set per notification type.
Update Notifications in the Console
- Open Account Settings.
- Go to Notification Settings.
- Review each Account, Billing, and Instance section.
- Turn off email for any optional event you do not want in your inbox.
- For low-balance notifications, set the credit threshold that should trigger the warning.
- Select events that should be sent to a webhook, then create or edit the webhook destination.
- Click Save.
Set your low-balance threshold below your autobilling threshold. That gives you an early warning if an automatic charge fails before your balance reaches zero.
Webhooks
Webhooks are part of the notification system. They use the same event catalog and preferences as email notifications, but deliver events to an HTTPS endpoint that you operate.
Use webhooks when you want to:
- Trigger cleanup or orchestration when an instance changes state.
- Mirror billing or account events into your own tools.
- Build an audit trail outside the Vast console.
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. Renter events use the client: prefix, such as client:low_credit or client:outbid.
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/.
Programmatic Access
Building your own notification settings UI or automation? The full set of notification, preference, and webhook endpoints is documented in the Notifications API.
Good Defaults
Start with this setup:
| If you are… | Recommended setup |
|---|
| Renting GPU instances manually | Keep low balance, outbid, downtime, and contract end date emails enabled |
| Running automated workloads | Add a webhook for instance lifecycle, downtime, outbid, and billing events |
| Building your own platform on Vast.ai | Use notification type keys, verify webhook signatures, and deduplicate by event_id |
