Developers

Build approved partner integrations on top of TradeVulcan workspace data.

TradeVulcan API access is currently available for approved partner and server-to-server workspace use cases. The current API is built for scoped access to contacts, leads, workspace identity, and app-adjacent workflow data where the workspace has approved the use case.

Request API access Read API docs

Already approved and signed in? Manage API clients from Workspace Settings.

Current API surface

POST /api/oauth/tokenPOST /api/oauth/revokeGET /api/v1/meGET, POST /api/v1/contactsGET, POST /api/v1/leads

The first release supports OAuth 2.0 client credentials for approved server-to-server partners. Redirect URI fields may appear in settings for future partner app patterns, but public SDKs are not implied.

Workspace-owned credentials

Approved workspaces can create named API clients from Workspace Settings, choose scopes, and rotate secrets.

Scoped partner access

Every access token carries explicit scopes so partners can read or write only the resources approved for that workspace.

Built for revenue workflows

Start with contacts and leads, then expand into app-specific workflows, booking data, webhooks, and connector-safe automation.

Partner-ready

What partners can build first

The API starts with the objects that most integration partners need to move quickly without touching fragile app internals.

Lead marketplaces sending qualified demand into TradeVulcan

Agency reporting dashboards that need contact and lead context

Form, call, and chat partners creating leads from customer conversations

Automation tools that bridge TradeVulcan into field-service operations