FruxonDocs
IntegrationsWebhooks

List webhooks, optionally filtered by provider.

Returns every webhook in the tenant, or just those for one provider when `provider` is supplied (e.g. `github`, `stripe`). Subscription details are not embedded — fetch them per webhook via `GET WebhookSubscriptions`.

GET
/v1/tenants/{tenant}/webhooks

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

tenant*string

The tenant identifier

Query Parameters

provider?string

Optional provider name to filter by.

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/webhooks"
[
  {
    "id": "string",
    "provider": "string",
    "authMode": "API_KEY",
    "status": "ACTIVE",
    "expiresAt": 0,
    "createdAt": 0,
    "modifiedAt": 0,
    "webhookUrl": "string",
    "signingSecret": "string"
  }
]
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Finds catalog and workspace tools that match a described capability.

Ranks every tool in the catalog, and every tool this workspace defined itself (its API tools, scripts and MCP servers' tools), against the words of `query`, in one ranking — a tool matches when any of them appears in its name, its integration or tool id, or its description, and ranks higher the more and the more prominently they do. Each result says where it comes from (`CATALOG` or `WORKSPACE`) and whether this workspace could use it now (`READY`: its integration needs no credentials, or a published config exists) or must connect the integration first (`NEEDS_CONNECTION`). Internal tools are never returned. An empty query returns an empty list.

Delete a webhook and deregister it from the external system if applicable.

Removes the webhook and cascades the delete to all subscriptions attached to it; any agent triggers wired through those subscriptions stop firing immediately. When the provider supports remote registration the external listener is also torn down — if that call fails the local delete is still attempted. After this, the inbound URL returns 404.