Skip to main content
API: one endpoint. The Node SDK over gRPC, the browser over grpc-web, and plain HTTP on /api/records and /api/regions all reach api.fonoster.ai, or your install's address. API: one endpoint. The Node SDK over gRPC, the browser over grpc-web, and plain HTTP on /api/records and /api/regions all reach api.fonoster.ai, or your install's address. Fonoster’s API is gRPC. Every resource you manage (applications, numbers, trunks, domains, SIP agents, calls, webhooks, providers, secrets, API keys and workspaces) is a gRPC service in a fonoster.<resource>.v1beta2 package. Browsers reach the same services through grpc-web, on the same endpoint: api.fonoster.ai on Fonoster Cloud, or your install’s address when you self-host. A few features are plain HTTP routes on that endpoint instead, such as call records under /api/records (search, recordings, erasure and retention) and regions under /api/regions. Every request names the workspace with its access key ID (WO…) and carries an access token from an API key. You don’t need to call any of this directly. Use the Node SDK: it wraps every gRPC service and HTTP route, signs in with your API key and renews the token for you.

@fonoster/sdk on npm

Install the SDK for Node.js and the browser.

Node SDK reference

Every client class and method, with its parameters and results.