FruxonDocs
IntegrationsCore

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.

POST
/v1/tenants/{tenant}/integrations/{integration}:verifyConfig

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

integration*string

The unique identifier of the integration.

tenant*string

The tenant identifier

Request Body

The auth metadata ID and configuration to verify.

authMetadataId*string|null
authConfig*

Auth credentials for an integration — the chosen auth method plus its filled-in parameters (API keys, tokens, …).

configParameters?|null

Extra parameters (e.g. connection_string, base_url) needed by some testers that live outside the auth config.

egressCountry?string|null

Egress country the config pins outbound traffic to (!:IntegrationConfig.EgressCountry). Testers that reach the target service must route their probe through the same country's egress proxy so the request exits the IP the service allowlisted — otherwise it leaves the default IP and a geo-fenced WAF rejects it. Null means no pinning (default direct egress).

authMapParameters?|null

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.

[key: string]?never

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
}
Empty
Empty
{
  "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.