Virtual numbers & entry points
Twilio numbers, units, and how buzzers reach Intry.
Overview
Intry’s “access point” for voice entry is the combination of a VirtualNumber (Twilio E.164) assigned to a Unit. When a visitor dials or the intercom hits Twilio, Core resolves the number → unit → residents.
Virtual number admin API
| Method | Path | Description |
|---|---|---|
GET | /api/admin/virtual-numbers | List numbers |
POST | /api/admin/virtual-numbers | Provision / attach |
PUT | /api/admin/virtual-numbers/:id | Update metadata |
DELETE | /api/admin/virtual-numbers/:id | Remove mapping |
POST | /api/admin/virtual-numbers/:id/release | Release back to pool |
Fields
| Field | Purpose |
|---|---|
e164 | Canonical phone string (+15551234567) |
twilioSid | Twilio resource SID |
status | Operational state (active, etc.) |
quarantineUntil | Cool-down before reuse |
Linking to units
Unit.virtualNumberId binds the buzzer path. Changing numbers mid-lease requires coordination so Twilio routing and resident apps stay consistent.
Twilio webhooks
Inbound voice and status callbacks hit /twilio/* on Core — not the admin API. Configure those URLs in Twilio console per environment.