GraphQL playground

This is not a sandbox. Mutations can send real SMS messages and consume credits.

Start with “1. List workspaces”, copy an id into workspaceId in “2. List devices”, then use the phone’s id as input.deviceId in “3. Send SMS”. Replace the sample IDs and recipient number in Variables. You execute each example yourself.

For this flow, select the integration’s granted smspipe/devices.read and smspipe/messages.write scopes; add smspipe/messages.read to check status. Token generation defaults to read-only scopes — explicitly select sending.

Already know your workspace and phone? In the portal, click the “Workspace ID” box below the workspace switcher or in the workspace list, and the “Device ID” box in the device list or detail page. These boxes copy the full GraphQL ID even when the display is shortened.

Generate an integration token below: choose “Generate token” to open the dialog for your saved Client ID, client secret, and scopes. GraphiQL will use it automatically. You can also paste a token manually.

The secret is cleared when the dialog closes. A portal ID token has the signed-in user’s permissions; it is not an integration token or an elevated admin token.

Existing integration secrets cannot be recovered. If you did not save one, create a new integration.

Copy the current session ID token using “Token API” in the account section of the portal left menu (open navigation on mobile), then paste it here. The displayed validity is for the current token; refresh can extend it.

Open OAuth integrations in the console

OAuth instructions