set_site_connector

Pick the connector by its toolkitSlug from list_site_connectors. The change applies to the site's chat from the next message.

Turning one on needs your own connected account for it, which list_site_connectors reports as usableByMe, so a connector only a teammate has connected is refused with Connect your own account for this connector before enabling it here! Connecting an account happens on the Connectors page or under Manage connectors in the chat's + menu, never with an access token, over MCP or the HTTP API.

A site can have up to 10 connectors on at once, so turning one more on is refused until another is turned off. See Connectors.

Request

Call it with a POST to https://api.modulify.ai/v1/set_site_connector, sending the inputs below as a JSON object. The token needs the config:write scope.

It makes changes, so send an Idempotency-Key header whenever you might retry it. A retry with the same key gets the first answer back instead of running again.

curl -X POST https://api.modulify.ai/v1/set_site_connector \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID","toolkitSlug":"TOOLKIT_SLUG","enabled":true}'

Over MCP, the same method is the set_site_connector tool.

Inputs

Response

Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.