Skip to main content
Open Menu → API access. Keys belong to the workspace. Use the sender identifier in your message requests to select a sender. Provider credentials remain private.

​
Create a sandbox key

An administrator enters a name, chooses 7, 30 or 90 days, and selects Create sandbox key. Copy the secret immediately. It appears only once. Dismiss secret removes it from the page. Existing keys show their name, scopes, expiry and status without their secret. Select Revoke to invalidate a key. The screen currently creates keys with messages:read, messages:write and events:read. The management API supports narrower scope selections. Members must ask an administrator to manage keys.
Sandbox keys simulate messaging. They cannot send to real phones or operate a live RCS test sender. Real-device testing currently uses Inbox with an enabled connection and allowed recipient. General live developer access is not enabled.
API key management with synthetic data and no visible secrets

​
Sender identifiers

The Sandbox sender IDs section lists identifiers for simulated requests. Channels → RCS → Your senders shows the separate real RCS identifiers. An identifier alone does not grant access or enable delivery.
See the API contract for message schemas, scopes and idempotency. Key creation and revocation appear in Account activity, without recording the secret.