You can now create API keys that only work in one workspace, right from the Salesforge dashboard. This makes it safer to give API access to a client, a contractor, or a third-party tool, because the key cannot reach anything outside that workspace.
A workspace key has full access to the workspace it was created in. It can make all types of API requests there, including GET and POST, so it can read, create, update, and delete data. This includes:
Sequences, including their steps, schedules, contacts, and mailbox assignments
Contacts, including bulk actions and the DNC list
Mailboxes, threads, and replies
Webhooks
Products and knowledge bases
Integration endpoints such as RB2B, Make.com, and data enrichment
Some of the integration endpoints work only with a workspace key. An account-wide key is not accepted for them.
It cannot access any other workspace in your account. A request for another workspace returns a “not found” response.
It cannot create a new workspace.
When it lists workspaces, it only returns the workspace it belongs to.
Workspace key | Account-wide key | |
|---|---|---|
Access inside a workspace | Full access | Full access |
Workspaces it can reach | Only the one it was created in | All workspaces in your account |
If the key is leaked | Only that workspace is exposed | Every workspace is exposed |
Creating new workspaces | Not allowed | Allowed |
Use a workspace key when:
You are giving API access to a client, contractor, or partner who should only see their own workspace.
You are connecting a third-party tool or integration to one workspace.
You want to limit the damage if a key is leaked or a tool misbehaves.
Use an account-wide key when:
You manage several workspaces from one script or tool.
You need to create new workspaces through the API.
The key is only used internally by your own team.
Log in to your Salesforge account and switch to the workspace you want the key to work in.
Go to Settings.
Open the API & MCP tab.
Click Add new key.

In the Add new API key pop-up, enter a descriptive name in API key name. This field is required.
Keep Limit this key to the current workspace ticked.
Click Generate API key.

To create a key that works across your whole account, untick Limit this key to the current workspace before you click Generate API key.
A workspace key is tied to the workspace you are in when you create it, so select the right workspace first.
Because a workspace key has full access in its workspace, treat it like a password and share it only with people and tools you trust.
Use a clear name for each key, such as the client or tool it is for, so you can tell your keys apart later.
If you have any questions about API keys, reach out to our support team through the chat widget and we will be happy to help.