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, …).
Id of the integration being verified. Used by the generic IntegrationAuths.GenericHttpConfigTester to resolve config metadata and apply auth exactly as the tool executor does. Null for legacy ad-hoc verification paths that only use provider-specific testers.
GET path (relative to the baseUrl connection parameter) the generic
IntegrationAuths.GenericHttpConfigTester probes to verify credentials — carried over
from IntegrationAuthMetadata.TestPath. Null for provider-specific
testers, which probe their own hard-coded endpoint.
Extra parameters (e.g. connection_string, base_url) needed by some testers that live outside the auth config.
Routing key parameters from the AuthMap entry being verified (e.g. owner,
repo for GitHub). Null when verifying a top-level Auth rather than
an AuthMap entry. Lets per-entry-aware testers probe the specific resource the
credential is mapped to instead of a generic endpoint that may have different
permission requirements.
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",
"credentialsRejected": false,
"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
}Lists every integration that declares at least one trigger descriptor.
Drives the new-trigger picker so the operator doesn't see the 40+ trigger-less integrations in a long flat dropdown. Each row is `{ integrationId, displayName, triggers[] }`; consumers can pick an integration and use the embedded `triggers` array directly without a second round-trip.
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.