API keys and SDK setup

Keys authorize integrations. Public documentation shows only placeholders; actual keys remain in your private account.

Before you start

Use an account with key-management permission and select the intended app. Decide the minimum scope the integration requires.

Step by step

Open the app's API Keys, or account-level Manage → API Keys.
Create a key using the name, app assignment and scope controls available to your account.
Limit the key to the intended app and required operations. Keep administrative or multi-app keys out of distributed client apps.
Copy the key only into your own private development configuration.
Follow the platform's SDK installation guide and replace YOUR_API_KEY locally.
Send a non-sensitive test event and confirm it under the correct app.
If changing or revoking a key, identify dependent integrations first, deploy the replacement and verify them before disabling the old key.

Confirm it worked

Only the intended integration can access its allowed app/resources, and a known test operation succeeds. A created key alone is not SDK integration.

Troubleshooting

A 401 can indicate a missing, inactive or invalid key. A scope/permission failure can require a different authorized operation, not broader access by default. A mobile app key can be extracted from its binary; never use it to hold server, store or provider secrets.