Rate limits
The rate_limits resource controls per-second and per-minute SIP packet rates at the SBC — for registrations, INVITEs, and total packet volume. It is NOT a REST/HTTP API rate limiter.
rate_limits controls SIP packet rates at the Session Border
Controller, not REST API throughput. If you're looking for HTTP API
throttling guidance, see the note at the bottom of this page — Vinix
has not published API rate limits yet.
The rate_limits resource caps incoming SIP packets per second and per
minute for an account, a device, or the cluster.
Document shape
{
"data": {
"account": {
"per_minute": { "registrations": 100, "invites": 100, "total_packets": 1000 },
"per_second": { "registrations": 5, "invites": 5, "total_packets": 20 }
},
"device": {
"per_minute": { "registrations": 10, "invites": 10, "total_packets": 100 },
"per_second": { "registrations": 2, "invites": 4, "total_packets": 10 }
}
}
}- The
accountsection caps SIP packets for the entire account (realm). - The
devicesection caps SIP packets for every device under the account that doesn't have a device-level override. - Both sections accept
registrations,invites, andtotal_packetskeys underper_minuteandper_second.
Operations
| Method | Path | Purpose |
|---|---|---|
| GET | /accounts/{id}/rate_limits | Read account-level limits |
| POST | /accounts/{id}/rate_limits | Update account-level limits |
| DELETE | /accounts/{id}/rate_limits | Remove account-level limits |
| GET | /accounts/{id}/devices/{device_id}/rate_limits | Read device-level limits |
| POST | /accounts/{id}/devices/{device_id}/rate_limits | Update device-level limits |
| DELETE | /accounts/{id}/devices/{device_id}/rate_limits | Remove device-level limits |
Cluster-wide limits are configured at the infrastructure layer and are not exposed via the public API.
Full reference: Core API → Diagnostics → Rate Limits.
What about HTTP API rate limits?
Vinix has not published REST/HTTP API rate-limit numbers. Operators set HTTP-level limits at the load balancer or reverse-proxy layer; defaults are not advertised.
If you're planning a high-volume integration, contact [email protected] for current operational limits before going to production.

