API Endpoints v2

Sonoran Radio v2 API endpoints with bearer auth, community-scoped URLs, and documented per-endpoint rate limits.

Sonoran Radio v2 moves authentication to the Authorization header and scopes community-specific requests with communityId in the URL for /v2/servers/{communityId}/... routes.

Available v2 Docs

Libraries

Use the official Sonoran SDK libraries if you want package-managed helpers for the v2 API.

Libraries

Authentication

Start here for bearer authentication, required headers, server-scoped routing, and common error formats.

Authentication

Users

User endpoints cover connected users, member approval, moderation, permissions, and channel assignment.

Users

Channels

Channel endpoints cover channel discovery and tone playback operations.

Channels

Community Server

Community server endpoints cover server IP registration, subscription lookup, and in-game speaker location updates.

Community Server

Response Formats

Successful Requests

Successful responses return application/json.

Failed Requests

Authenticated v2 request failures return application/problem+json.

Example:

Common Errors

Status
Cause

400

Validation failed for one or more request values

401

Missing or invalid bearer token

404

communityId is not available to the authenticated API key

404

Requested room, member, or participant was not found

429

Rate limit exceeded for the endpoint

Rate Limits

All authenticated v2 endpoints are rate limited per API key, not per caller IP. Limits vary by endpoint, so each endpoint page includes the published limit for that route.

When a request is rate limited, the gateway returns 429 Too Many Requests.

High-frequency integrations should respect the published per-endpoint limits even if a small internal buffer exists.

Full OpenAPI Collection

OpenAPI v2 Collection (Postman Import)

Last updated

Was this helpful?