Skip to content
Open Markdown

Get integration status ​

GET /v1/admin/system/integrations

  • Operation ID: getSystemIntegrations
  • Tags: System
  • Base URL: http://localhost:8787

Configuration summary only; no secrets or credential values are returned.

Workflow: Integration guide.

Authentication: staff Bearer JWT with permission system.read.

Authentication ​

  • Auth: staff Bearer JWT (Authorization: Bearer <access_token>) with the permissions below.
  • Required permissions: system.read

Responses ​

200 ​

Integration status.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object

FieldTypeRequiredDescription
stripeobjectyes-
stripe.modestringyesOne of: "test", "live", "unknown"
runtimeobjectyes-
runtime.reachablebooleanyes-
smtpobjectyes-
smtp.configuredbooleanyes-
mercureobjectyes-
mercure.configuredbooleanyes-

Errors ​

401 ​

Missing, malformed, expired or wrong-audience Bearer token (missing_token, invalid_token, invalid_audience).

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody)

FieldTypeRequiredDescription
errorstringyesStable machine-readable error code, e.g. forbidden, not_found.
detailsanynoOptional structured context. For 403 it is { perm }.

Error response

json
{
  "error": "missing_token"
}

403 ​

Authenticated but lacking the required permission. details.perm lists the accepted permission keys.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "forbidden",
  "details": {
    "perm": "system.read"
  }
}

500 ​

Unexpected server error (internal). No details are returned.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "internal"
}

Examples ​

curl ​

bash
curl -X GET 'http://localhost:8787/v1/admin/system/integrations' \
  -H "Authorization: Bearer $ACCESS_TOKEN"

TypeScript ​

ts
const accessToken = process.env.ACCESS_TOKEN; // user JWT from your sign-in flow

const response = await fetch("http://localhost:8787/v1/admin/system/integrations", {
  method: "GET",
  headers: {
    "Authorization": `Bearer ${accessToken}`,
  },
});
if (!response.ok) throw new Error(`HTTP ${response.status}: ${await response.text()}`);
const data = response.status === 204 || response.status === 205
  ? undefined
  : response.headers.get("content-type")?.includes("json")
    ? await response.json()
    : await response.text();

Try this endpoint

Requests go directly from your browser to the API. Send request executes this endpoint against the selected server.

GET/v1/admin/system/integrations

Your token stays in this tab's memory and is sent only when you press Send request.

Built for developers. Ready for agents.