Manage integration API keys

Create and review keys used by external integrations.

Before you start

Sign in as the account owner or an admin of the workspace. API key availability depends on your plan. Check the integration’s required permissions before creating a key; this form does not offer custom scopes, and switch to the workspace the integration should reach.

Open the feature

Choose Settings > Workspace > Social Champ API Keys.

Steps

1. Under Create New Key, enter Key name if you want a name, then choose Create Key.
2. Copy the newly created key into your approved secure credential store. It is shown only once.
3. Review its name, status, permissions and last-use details under Your API Keys. Applies to shows This workspace for a key made here, or Account-wide.
4. Review Connected OAuth Sessions separately for integrations connected through OAuth.
5. Revoke keys or sessions that should no longer have access.

Check approval permissions

Review the permission badges under Your API Keys or Connected OAuth Sessions. Read profile and Post + queue are different from Approvals, which is needed for approval workflows and certain bulk agency actions.

The current key-creation form has no control for adding Approvals. Creating another key through the same form will not add it. For an external AI client that needs approval workflows, use the account Owner's OAuth connection and enable the optional permission on its consent screen. If your integration requires an API key instead, contact support about the missing permission before replacing a working key.

Expected result

The key appears in the list, with a prefix and last four characters for identification rather than the full secret.

Example

Create a descriptively named key for your reporting integration, then check its last-used time after setup.

Limits and permissions

A workspace can have at most 10 active keys, including account-wide keys. A workspace-specific key takes priority over an account-wide key. Key creation asks for a name and grants the standard integration permissions; it does not offer custom permission scopes.

• These keys are for integrations, not provider keys for the built-in assistant.
• A new key works only in the workspace you create it in. Calls it makes to any other workspace are refused.
• Keys created before keys moved to workspaces are listed as Account-wide and remain available where no workspace-specific key takes priority. Only the account owner can revoke them.
• Admins can't create keys with the Approvals permission.
• OAuth session permissions are requested when connecting. To change them, revoke and reconnect with the intended permissions.
• Never include a key in a support message or shared document.

Troubleshooting

• The full key is no longer visible: it is displayed only at creation; replace it if you did not store it securely.
• An integration stops after revocation: update it with an authorized replacement only if access is still intended.
• Key creation is unavailable: check the account’s plan, and that you're the owner or an admin of this workspace.
• An integration's calls to a workspace are refused: its key belongs to a different workspace. Create a key in the workspace it needs to reach.