Verifies that the provided auth configuration can successfully connect to the integration.
Only supported for auth methods with `ConfigTestSupported = true`. Returns 400 if the auth method does not support verification.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The unique identifier of the integration.
The tenant identifier
The auth metadata ID and configuration to verify.
Auth credentials for an integration — the chosen auth method plus its filled-in parameters (API keys, tokens, …).
Extra parameters (e.g. connection_string, base_url) needed by some testers that live outside the auth config.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/integrations/string:verifyConfig" \ -H "Content-Type: application/json" \ -d '{ "authMetadataId": "string", "authConfig": {} }'{
"success": false,
"error": "string",
"authorizationUrl": "string",
"authMapResults": [
{
"parameters": {},
"success": false,
"error": "string",
"authorizationUrl": "string"
}
]
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Updates an existing integration.
Omit credential fields to keep existing values unchanged.
Get MCP settings for an integration.
Returns the integration's MCP server configuration: whether it is `enabled`, which integration `configId` backs production calls, the `exposedToolIds` list that filters which tools the MCP server advertises, and the `apiKeyId` used to authenticate inbound JSON-RPC traffic. If no MCP config exists for the integration one is created lazily with defaults, so this endpoint is safe to call before any configuration step.