How Do I Regenerate My API Keys in Feedspace?

Overview

Regenerating your API keys creates a new API Key and Secret Key pair for your Feedspace workspace. The previous credentials are invalidated the moment you regenerate, so any custom integration, app, or script using the old keys will return authentication errors until it is updated with the new credentials.

Use this action if your credentials were compromised, were shared with a party that no longer has authorised access, or if you are following a security rotation practice.

Before You Start

Make a list of every integration, script, or application that currently uses your existing API Key and Secret Key. You will need to update each one immediately after regenerating to avoid service interruptions.

Steps to Regenerate API Keys

1. In the left sidebar, click Automation under the Workspace section.
2. Click the API tab at the top of the Automation page.
3. Locate the API Key section. If keys have already been generated, you will see your existing API Key and Secret Key fields.
4. Click Regenerate.
5. Confirm the action when prompted. A new API Key and Secret Key pair will be generated instantly.
6. Click the Copy icon next to each field to copy the new values, then store them in a secure location.

Important: Update All Integrations

As soon as you regenerate, the old API Key and Secret Key stop working. Any integration that still uses the old credentials will fail with an authentication error. Update the following before your next API call:

• Custom applications or internal tools built against the Feedspace REST API
• Automation workflows in third-party tools (such as Make or Zapier) that use API Key authentication
• Scripts or serverless functions that send requests to the Feedspace API
• Any environment variables or secrets stored in deployment platforms (such as CI/CD pipelines or cloud function configs)

When to Regenerate

• Compromised credentials: If you suspect the API Key or Secret Key was exposed in a public repository, log file, or error report, regenerate immediately.
• Access revocation: If a team member, agency, or external contractor who had access to your credentials no longer works with you, regenerate to cut off their access.
• Security rotation: As a periodic security practice, rotating API credentials limits the window of exposure if keys are ever intercepted.

Common Confusion

Does regenerating affect my Automation Secret Key?

No. Regenerating the API Key and Secret Key on the API tab only affects your developer REST API credentials. The Automation Secret Key on the Automation tab is a separate credential used by form automation tools such as Pabbly Connect and Make. Regenerating one does not change the other.

Can I undo a regeneration?

No. Once you confirm the regeneration, the old credentials are permanently invalidated and cannot be restored. Make sure you are ready to update all dependent integrations before confirming.

What happens to active API requests in progress?

Any request that was already authenticated before regeneration will complete normally. New requests sent after regeneration using the old API Key will fail with an authentication error. Update your credentials as soon as possible after regenerating.

What You Can Do Next

• Update all applications and scripts with the new API Key and Secret Key.
• Verify your integrations are working correctly by testing an API call with the new credentials.
• Store the new credentials in a secure secret manager rather than in plain text or source code.