wundertre.help
Team login

Create and revoke organization API keys

Organization API keys provide long-lived access for custom integrations or scripts. Treat a key as a credential with broad access to your organization's data.

Before you begin

Confirm the organization and the integration that will use the key. Obtain the appropriate approval for persistent access and decide where the credential will be stored securely.

The creation form uses the application's default full-access scope set and does not provide a scope picker. Do not create a key expecting to restrict it to one selected feature from this screen. Use the authorization flow for the specific app when that is the intended connection method; Zapier uses OAuth.

New API Key opens an inline Key name field with Create and Cancel. There is no scope picker.

New API Key opens an inline Key name field with Create and Cancel. There is no scope picker.

Create a key

  1. Open Settings → Integrations → API Keys.
  2. Select New API Key.
  3. Enter a descriptive Key name so you can identify the integration later.
  4. Review the organization and intended use before selecting Create. Pressing Enter in the name field can also create the key.
  5. In API Key Created, copy the key directly to your approved secure storage. It is shown only once.
  6. Select Done after storing it safely.

Never put the key in a help article, public repository, screenshot, recording or ordinary chat message.

Check the key list

The list shows Name, Key prefix, Last used and Created. Use the name and creation date to identify the key. A prefix is an identifier, not the complete credential.

Never under Last used means no last-used date is displayed. It does not verify that an integration has been configured successfully.

For authentication requirements, endpoints and scope details, follow the API-reference link on the page. The developer reference is linked at docs.wundertre.com.

Revoke a key

  1. Identify the exact key and the integrations that depend on it.
  2. Coordinate any replacement before revoking a key still in use.
  3. Select Revoke on its row when you are ready to stop that access. The action does not present a separate confirmation dialog in this screen.
  4. Wait for the result and check that the key no longer appears in the active list.

Revocation can interrupt scripts or integrations using that key. If a credential was exposed, revoke the affected key and use a securely handled replacement rather than continuing to use it.

If you lose a newly created key

The full key cannot be recovered from the list. Review and revoke the unused key when appropriate, then create a replacement through an approved credential-handling process.

Was this helpful?

Related

Configure social approvals and per-person publishing rules
Social Approvals lets an organization admin decide whose posts need review before they reach social networks. These controls affect teammates’ ability to publish and approve posts.
Understand why a feature is unavailable to your account
A missing or disabled feature can depend on your organization, role, hub access, subscription, usage limits or feature availability. Start with the message on screen rather than changing settings at random.
Set member roles, hub access and prospecting budgets
A teammate's tier defines what they can do, hub access defines where they can work, and a prospecting budget limits their prospecting spend. Review all three before saving.
Invite and manage organization members
Use User Management to invite teammates and review whether they have finished signing in. An invitation, a member record and a completed first sign-in are separate states.