API reference

Waveline API reference

The API uses Bearer authentication at https://api.waveline.tel. Start with the quickstart to create a scoped API key.

This reference is generated from the Waveline OpenAPI contract. Download the OpenAPI specification for use with your API client or code generator.

Check each operation's authentication and permission requirements. In particular, GET /v1/members is not available to REST API keys or service connections. Teammate lookup is available through Waveline’s supported assistant connection; do not send an assistant token to the REST API. See API access and permissions before choosing credentials.

Endpoints

Connection, inboxes, and teammates

Contacts

Calls and recordings

Conversations, messages, and attachments

Phone numbers and analytics

Webhook subscriptions and deliveries

Models

All request and response models, including contacts, scoped calls, messages, webhook events, and media.

Authentication

WorkspaceApiKey: wl_live_ or wl_test_ followed by 64 lowercase hex characters. Use separate keys per integration and environment.

OAuthAccessToken: 15-minute OAuth access token obtained using authorization code + S256 PKCE. Discover endpoints at /.well-known/oauth-authorization-server. New connections and rotating refresh tokens have no scheduled expiration. Access tokens still expire after 15 minutes and must be refreshed. Revocation and current connection access remain enforced. Tokens are bound to the resource authorized during consent.

Keep credentials on your server. New API keys created in Waveline have no expiration date. Delete or revoke a connection to stop access. OAuth tokens for an assistant connection are bound to its authorized resource; they are not interchangeable with REST API credentials.

Guides

Access and permissions · Sending messages and billing · Webhooks · Errors and limits

Previous
Quickstart