FruxonDocs
IntegrationsConfigs

Lists the configuration's open credential links.

Newest first. The links themselves are never listed: each was shown once, when it was minted. A link that was filled, withdrawn, superseded or ran out is not open and is not listed.

GET
/v1/tenants/{tenant}/integrations/{integration}/configs/{config}/credentialRequests

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

config*string

The configuration ID.

Formatuuid
tenant*string

The tenant identifier

integration*string

The integration identifier

Query Parameters

PageSize?integer

The maximum number of items to return per page

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

Opaque pagination token returned by an external service. Pass it back unchanged rather than interpreting it as an offset.

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/integrations/string/configs/497f6eca-6276-4993-bfeb-53cbbbba6f08/credentialRequests"
{
  "items": [
    {
      "id": "00000000-0000-0000-0000-000000000000",
      "url": "string",
      "intendedForEmail": "string",
      "note": "string",
      "mode": "CAPABILITY",
      "issuedByUserId": "string",
      "issuedByName": "string",
      "issuedByAgentId": "string",
      "issuedByAgentName": "string",
      "target": "INTEGRATION",
      "status": "OPEN",
      "expiresAt": 0,
      "closedAt": 0,
      "createdAt": 0
    }
  ],
  "nextPageToken": "string",
  "totalCount": 0
}
{
  "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
}

Mints a short-lived, client-usable OAuth access token for this config so an in-browser SDK that requires the token directly (e.g

Available only for integrations that opt in via `Integration.AllowsClientOAuthToken` — a live token in the browser is usable outside Fruxon with the config's full scopes, so most integrations must never expose it. The token carries the config's scopes and self-expires on the provider's TTL. The underlying credential access is audited by the resolver; this adds a distinct browser-vend log signal. Returns 400 when the integration hasn't opted in, the config has no OAuth auth configured, the stored credentials can't be refreshed, or no account is connected yet.

Mints a link asking for the configuration's credentials.

The link is in the response once and never again; only its hash is kept. Minting another for the same configuration withdraws the open one. Refused (409 `not_linkable`) for a configuration each person connects with their own credentials and one that picks its credentials by request parameters. For a configuration that connects an account by signing in to its provider (OAuth), whoever opens the link signs in, granting the `scopes` asked for, and that account becomes the configuration's connection. A sign-in link (`requireSignIn: true`) takes `integrations:write`. A capability link, which anyone holding it can fill, takes `workspace:write` as well (403 `insufficient_scope` naming it without). Either stops working once its sender no longer holds what sending it took.