MCP Connectors
Refresh tenant connector caches
Invalidates and refreshes all cached connector instances for a tenant. Use this after updating a tenant's connector configuration.
{tenant_id} is not a selector. It is validated against the identity apiAuthMiddleware resolved and a mismatch is 403 (platform/agent/connector_refresh_api.go:152-156); the tenancy that is actually refreshed always comes from the credential.
- Basic auth: the resolved identity is your licensed org, so this route can only ever refresh your own pool.
- Internal-service credential: the resolved identity is whatever X-Tenant-ID you send (platform/agent/authenticator.go:127-130), so an operator targets a named tenant by sending that header and the matching path segment. Naming a tenant in the path with no X-Tenant-ID is 403, because the identity then falls back to the synthetic orchestrator-internal client id.
stats.cached_connectors is structurally 0 on this route — the refresh empties the tenant's scope immediately before the count is taken.
post/api/v1/connectors/refresh/{tenant_id}
Request
- Base URLhttps://agent.getaxonflow.com
- Auth
- HTTP basic
- or API key in header X-Internal-Service-ID and API key in header X-Internal-Service-Token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
tenant_idstring required
The tenant whose connectors should be refreshed. Must equal the authenticated tenant — see the description.
Response
Tenant connectors refreshed
Example response
{
"duration": "12.345ms"
}Changes
No recorded changes to this operation across all 1 revision of this API.