Bring your own connector

Bring your own connector lets you add custom connectors when the API you need is not available as a built-in connector.

Use bring your own connector to support unsupported SaaS APIs, partner systems, and internal APIs while keeping authentication, authorization, and secure API access in Scalekit.

Once the connector is created, you use the same flow as other connectors: create a connection, create or fetch a connected account, authorize the user, and call the upstream API through Tool Proxy.

Custom connectors appear alongside built-in connectors when you create a connection in Scalekit:

Why use bring your own connector

Bring your own connector lets you:

• Extend beyond the built-in connector catalog without inventing a separate auth stack
• Bring unsupported SaaS APIs, partner systems, and internal APIs into the same secure access model
• Reuse connections, connected accounts, and user authorization instead of building one-off auth plumbing
• Keep credential handling, authorization, and governed API access centralized in Scalekit
• Move from connector definition to live upstream API calls through Tool Proxy using the same runtime model as other integrations

Note

Custom connectors route all API calls through Tool Proxy. Direct SDK calls to the upstream API are not supported.

How bring your own connector works

Bring your own connector uses the same model as built-in connectors:

1. Create a connector definition
2. Create a connection in Scalekit Dashboard
3. Create a connected account and authorize the user
4. Use Tool Proxy to call the upstream API

Creating the connector defines how Scalekit should authenticate to the upstream API. After that, connections, connected accounts, user authorization, and Tool Proxy work the same way as they do for built-in connectors.