FruxonDocs
IntegrationsCore

Lists asset source types this integration can back.

Catalog metadata, not per-tenant data. Examples: the Jira integration backs the `jira` asset source ("ingest Jira issues matching a JQL query"); Zendesk backs both `zendesk_articles` and `zendesk_tickets`. Integrations with no ingestion path return an empty list. Drives the integration detail page's Assets tab and the "create asset for this integration" affordance.

GET
/v1/tenants/{tenant}/integrations/{integration}/assets

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 integration ID.

tenant*string

The tenant identifier

Query Parameters

PageSize?integer

The maximum number of items to return per page

Formatint32
PageToken.Skip?integer
Formatint32
PageToken.Cursor?string

Opaque cursor token from an external system (e.g. RAG API). When set, M:Fruxon.Common.Collections.PageToken.AsString returns this value directly instead of encoding Fruxon.Common.Collections.PageToken.Skip.

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/integrations/string/assets"
{
  "items": [
    {
      "sourceType": "string",
      "displayName": "string",
      "description": "string",
      "integrationId": "string",
      "properties": [],
      "authMetadata": [
        null
      ],
      "supportsAutoUpdate": false,
      "supportsWebhookRegistration": false,
      "supportsPollSchedule": false,
      "webhookSetupGuide": "string"
    }
  ],
  "nextPageToken": "string",
  "totalCount": 0
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Lists integrations in the workspace, paginated.

Returns a page of configured integrations, each annotated with its tool count. Use the `search`, `types`, and `tags` query parameters to filter server-side, and `pageSize`/`pageToken` to page through results. The full tool collection for an integration is fetched separately via `/integrations/{integration}/tools`.

Initiates an OAuth flow for application-level (agent-level) integration auth

Used when the agent builder wants to connect an OAuth account during agent setup, so that all users of the agent share the same credentials. After the user authorizes, the OAuth callback stores credentials temporarily. Use `:consumeOAuthCredentials` to finalize and create the auth record.