Create an application
Sign in with an email code at dev.offlineprotocol.com. Create or select an organization, then choose Create application. In the application’s API keys tab, copy the App ID (app_...). Pass this value as appId to React 0.2.0, React Native 0.3.3 or Proof of Location. It is not the Mesh SDK’s mesh app identifier. It is not a secret and is not a device’s off1… address.
Create a key
Only organization Owners and Admins can create or delete keys. In the application’s API keys tab:- Choose Create key and name the credential.
- Choose a product: OfflineID, Mesh SDK, Proof of Location or All products.
- Choose Full access, Read & write or Read only for the required operation.
- Copy the secret immediately. Offline Protocol stores only a hash of it, so it cannot be shown again or recovered; the list shows a masked preview such as
••••xxxx. Replace a lost key with a new one.
Enable SDK telemetry
Telemetry is the client-side credential exception:- Create a dedicated application key scoped to Mesh SDK only, used for nothing else. Do not use an All products key or your CLI key. The key ships inside your app, so treat it as extractable: anyone holding it can send telemetry that counts toward your usage. The permission level does not restrict telemetry ingest. Set a billing limit for telemetry, and rotate the key in the portal if you see unexpected events.
- Enable telemetry in the application’s Mesh SDK tab. If it is off, ingest returns
403 telemetry_disabled. - Pass the key and App ID to
enableTelemetry.
Replace or delete a key
Create a replacement, update the consuming deployment, and verify requests before removing the old key. Choose Delete key and enter the key’s name to confirm. Deletion revokes hosted access; it does not erase local device identity or application records.Organization keys and roles
Organization keys are under Settings → Advanced → Organization keys. Use an app API key for an application-specific integration; do not distribute an organization key in a client. Organization keys are not accepted by the CLI or hosted MCP. Both require an app API key. Roles are Owner, Admin, Developer, Billing, Analyst and Viewer. Developer and Viewer members can be restricted to selected applications; the other roles have access to every application in the organization.CLI credentials
offline login opens the portal’s CLI approval page, where you confirm the code shown in the terminal. Each approved login creates a new app API key for that terminal. offline logout clears local credentials and revokes that key; keys created in the portal stay active until you delete them. See CLI login.

