Connect connectors

Returns the provider authorize URL the console opens to connect this org's account.

GET /v1/knowledge/connectors/{provider}/connect

Addresshttps://api.hanzo.ai/v1/knowledge/connectors/{provider}/connect
MethodGET
Operationget_knowledge_connectors_by_provider_connect
AuthAuthorization: Bearer $HANZO_API_KEY

Returns the provider authorize URL the console opens to connect this org's account. There is no server-side redirect — the console stays in control of the navigation. The URL carries a state this server SIGNED over the caller's validated org, so the connection the callback completes can only ever land in that org.

Request

1 field.

FieldInTypeRequiredDescription
providerpathstringyesProvider is the connector to act on: github, slack, google or notion.

Response

StatusBodyMeaning
200knowledge.kbAuthorizeOutok
defaultproblem-detailsrefused

200 body — 1 field.

FieldInTypeAlwaysDescription
authorizeUrlbodystring—AuthorizeURL is the provider's authorize endpoint with an org-bound signed state.

Failure carries the platform error shape — see Errors.

Examples

hanzo knowledge connectors connect <provider>
import { Configuration, KnowledgeApi } from 'hanzoai';

const api = new KnowledgeApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getKnowledgeConnectorsByProviderConnect({ provider: 'provider' });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import KnowledgeApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = KnowledgeApi(client).get_knowledge_connectors_by_provider_connect(provider='provider')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.KnowledgeAPI.GetKnowledgeConnectorsByProviderConnect(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, knowledge_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = knowledge_api::get_knowledge_connectors_by_provider_connect(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.KnowledgeApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new KnowledgeApi(client).getKnowledgeConnectorsByProviderConnect();
curl https://api.hanzo.ai/v1/knowledge/connectors/<provider>/connect \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches knowledge through the knowledge tool, which names its 9 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_knowledge_connectors"
         }
       }
     }'

Knowledge API · All Hanzo APIs · Interactive reference

Was this page useful?