The Salesforge API lets you work with your Salesforge workspace programmatically, for custom integrations, automation, and data sync between Salesforge and your other tools. Agent Frank is part of Salesforge, so the same API and webhooks apply to it.
Key facts
The Salesforge API is available on the Growth plan. An Agent Frank subscription gives you the same access as the Growth plan, including the API.
Send the raw API key in the Authorization header, with no "Bearer " prefix.
Agent Frank has no separate API or webhooks. Use the Salesforge API and Salesforge webhooks.
No rate limit is currently enforced on the Salesforge public API.
The full reference is in the developer documentation at developer.salesforge.ai.
The Salesforge API is available on the Growth plan. An Agent Frank subscription gives you the same access as the Growth plan, including the API. If you're on the Pro plan without Agent Frank, you'll need to upgrade to use the API. See the Salesforge pricing page for current plans.
No. Agent Frank doesn't have a separate API or separate webhooks. Agent Frank is part of Salesforge, so everything goes through the Salesforge public API and Salesforge webhooks described in this article and in the Webhooks article.
There is no Agent Frank-specific API documentation. The Salesforge docs are the ones to use.
Use Salesforge webhooks to get notified about replies and booked meetings, and use the Salesforge API to read and update contacts, sequences, and conversations. Booked and completed meetings arrive as label_changed events, which is explained in the Webhooks article.
Sequence responses include an agentId field, and you can filter threads by agent with the agent_ids[] parameter. Webhook events don't include an agentId. See the developer documentation for the exact request and response format.
Log in to Salesforge.
Go to Settings.
Open the API & MCP tab.
Click Add new key, enter a name, and click Generate API key.
Store your API key securely, as it grants access to your Salesforge data. Use a separate key for each integration, rotate keys regularly, and never share a key in tickets, chat, or screenshots.
By default a key is limited to the workspace you created it in, and it can't see anything else. To create a key that works across your whole account, untick "Limit this key to the current workspace" before generating it.
Use a workspace-limited key for a client or contractor, so they only get access to their own workspace. Use an account-wide key only for your own integrations that need to work across workspaces. For the differences between the two types, see Workspace-level API keys in Salesforge.
All API requests require your API key. Send the raw API key in the Authorization header of each request, with no prefix:
Authorization: YOUR_API_KEYDo not add "Bearer " before the key. Adding it changes the header value and Salesforge API requests will fail. The Multichannel endpoints also accept an optional "Bearer " prefix, but the raw key works with both the Salesforge and Multichannel endpoints, so it is the format to use.
Example request:
curl -sS "https://api.salesforge.ai/public/v2/workspaces" \
-H "Authorization: YOUR_API_KEY"If a request fails, check the response status:
401: the API key is missing or invalid. Check that you are sending the raw key, with no "Bearer " prefix and no extra spaces.
403: the key is valid but does not have access to the requested resource, for example a workspace-limited key used on another workspace.
Send a request to GET /me. If the key is valid, you get a 200 response with your account ID and the key name. If the key is invalid, you get a 401.
curl -sS "https://api.salesforge.ai/public/v2/me" \
-H "Authorization: YOUR_API_KEY"No rate limit is currently enforced on the Salesforge public API or the Multichannel API. These limits may change as the APIs evolve. For the limits on other Forge products, see Forge API & MCP: Rate Limits, Authentication & Known Gaps.
Developer documentation: endpoints, request formats, response schemas, and authentication.
Swagger documentation: explore the endpoints and test requests directly.
Webhooks article: event types, filters, and the payload for each event.
Verify webhook signatures: how to check that a webhook delivery really came from Salesforge.
The Salesforge API provides access to many core platform features, including:
Create and retrieve workspaces
Access workspace information
Create contacts
Bulk import contacts
Retrieve contact records
Create, update, and delete sequences
Assign contacts to sequences
Manage sequence schedules
Update sequence status
Retrieve sequence analytics and performance data
Manage multichannel sequences
Connect LinkedIn accounts
Configure sender profiles
Manage enrollments and sequence actions
Retrieve validation results
Retrieve mailbox information
Update mailbox settings
Retrieve email threads
Manage thread labels
Reply to email conversations
Access conversation data
Create and manage products
Retrieve product information
Create webhooks
Receive real-time notifications when supported events occur
If you have questions about using the Salesforge API or run into issues while building an integration, contact us via the live chat in the bottom right corner.