Asks the provider what webhook URL it currently has registered for this config and whether recent deliveries have been failing.
Phase 11e. Read-side companion to `:applyWebhookToProvider`. Resolves an Fruxon.Model.Integrations.Configs.Webhook.IProviderWebhookInspector keyed by integration id and probes the provider — Telegram returns `getWebhookInfo`'s URL + `last_error_message` + `pending_update_count`; providers without a registered inspector return 400 and the FE hides the verify affordance.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The integration ID.
The configuration ID.
uuidThe tenant identifier
Optional expected URL for drift detection.
The URL Fruxon previously minted, for drift detection. Null when the FE doesn't have the URL in memory (e.g. fresh page load).
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/integrations/string/configs/497f6eca-6276-4993-bfeb-53cbbbba6f08:inspectWebhook" \ -H "Content-Type: application/json" \ -d '{}'{
"inspectFailed": false,
"providerHasUrl": false,
"providerUrlMatchesExpected": false,
"providerReportedUrl": "string",
"lastErrorMessage": "string",
"lastErrorAt": 0,
"pendingUpdateCount": 0,
"errorMessage": "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
}Mints the inbound webhook URL for this configuration
For one-webhook-per-credential providers (Telegram, Slack Events API, Twilio, Dialog360) where every chat / channel under the same bot shares one URL. The full URL is shown exactly once in the response — read paths only ever expose the template + key prefix. Re-mint via `/webhook:rotate` if the URL is lost; that revokes the previous key, so the operator must re-register the new URL with the provider before traffic resumes. Returns 400 when the integration declares per-binding webhook ownership (the binding-level mint is the right surface for those — activations flow automatically through participant create / update), or when this config already has a key bound (use `/webhook:rotate` to refresh).
Updates a configuration.
Patches the draft state of the config only; the published revision is untouched until `:publish` is called again. Fields left null on the request body are preserved, so this is safe for partial updates of `DisplayName`, `Parameters`, `Auth`, or `AuthMap`.