Skip to content
Journeybee Help Center home
Journeybee Help Center home

Partner API & MCP

Partner API & MCP

The Partner API lets your partners connect their own tools to the data they see in your partner portal — and MCP lets them do the same with AI assistants like Claude, ChatGPT, and Cursor. A connected tool or assistant can work with the partner's leads and deals in exactly the same way the portal does: it sees only what that partner can see, and follows all of your portal's visibility and sharing rules.

This is a partner-facing feature. Your own team's API access is separate — see API Keys for that.

Turning it on

Go to Settings, then Modules & AI, and turn on the Partner Portal API & MCP switch. Only admins can do this.

  • The switch only appears when the company-wide API & MCP feature is turned on for your account. That one is managed by Journeybee — if you do not see the switch, contact your account manager or support.

  • You can turn the Partner Portal API & MCP off again at any time. Partners' keys and connections stop working straight away, and their API & MCP page disappears from the portal.

What partners see

When the feature is on, partners get an API & MCP item at the bottom of their portal menu, just above Settings. It opens a page called Connect with MCP or API with:

  • Buttons to the Partner API docs and Partner MCP docs — the technical guides for whoever sets up the connection.

  • The MCP server URL they use to connect an AI assistant, with a copy button.

  • A list of their partner API keys, with a Create key button.

Connecting an AI assistant (no key needed)

For AI assistants like Claude, ChatGPT, or Cursor, partners do not need an API key at all:

  1. In the AI assistant, add a remote MCP server (sometimes called a custom connector) using the MCP server URL from the API & MCP page.

  2. The assistant opens your partner portal sign-in page. The partner logs in as usual.

  3. They review and approve access on the consent screen.

  4. Done — the assistant is connected. Access can be removed at any time by deleting the connector in the assistant.

Once connected, an assistant can look up the partner's partnerships, view and register leads, and view, create, and update deals — including moving them between pipeline stages. Nothing can ever be deleted through the Partner API or MCP.

Partner API keys

For custom integrations and tools that cannot sign in through a browser, partners create a key instead:

  1. On the API & MCP page, click Create key.

  2. Give it a Label (optional) and choose Read access and/or Write access. Read is on by default; write is off.

  3. Click Create. The full key is shown once, with the warning: “Store this key in a safe place. You won't be able to see it again.”

Good to know about keys:

  • Partner keys start with jb_partner_, so they are easy to tell apart from your company's own keys (which start with jb_live_).

  • Each partner user can have up to 10 active keys. If they need more, they should revoke ones they no longer use.

  • Revoking a key (the bin button, then Revoke key) stops it working immediately and cannot be undone.

  • A read-only key can never change anything — tools connected with it will not even see the actions that create or update records.

Good to know

  • Everything a partner's tools and assistants can see or change follows the same rules as the portal itself — room access, partnership settings, sharing settings, and visibility limits all apply.

  • If a partner's tool reports the error “Partner API access is not enabled for this company”, the Partner Portal API & MCP switch is off on your Modules & AI page.

  • The Partner API and Partner MCP developer guides cover the technical details — endpoints, regions, and connection examples — and are the right thing to send to a partner's developer.

Powered by Plain