Build an integration console

Run this integration code on the server unless the example explicitly mounts a browser button. tokenVault, savePendingOAuthState, loadQentrahSession, and event callbacks are application integration points, not exports supplied by the SDK. Implement them with your storage and user-session model.

Headless Integration Harness

The harness gives you reusable data models for a developer console without forcing a React component or a specific app layout.

1import {
2  createQentrahPartnerConsoleService,
3  qentrahPartnerSections,
4} from "@qentrah/auth-sdk/partner/harness";
5 
6const consoleService = createQentrahPartnerConsoleService({
7  workspaceBaseUrl: process.env.QENTRAH_WORKSPACE_BASE_URL!,
8  redirectUri: process.env.QENTRAH_PARTNER_REDIRECT_URI!,
9  requestedScopes: ["organization:read", "client:read", "client:create"],
10  session: await loadQentrahSession(userId),
11});
12 
13const sections = consoleService.sections();
14const lifecycle = consoleService.lifecycle();
15const credentialSnapshot = consoleService.credentials();
16const clientsQuery = consoleService.searchParams("clients", {
17  limit: 25,
18  search: "Acme",
19  status: "active",
20});

The harness can:

• Return the available console sections and the scopes each section needs.
• Detect missing scopes and reauthorization needs.
• Build OAuth lifecycle metadata for docs or UI.
• Build query parameters for list filters.
• Convert API responses into compact render rows.
• Normalize operation results for Test Results views.
• Sanitize nested payloads before rendering them.

Example rendering flow:

1const result = await consoleService.runResourceOperation({
2  sectionId: "clients",
3  operation: "read",
4  resource: "client",
5  options: { limit: 25, search: "Acme" },
6});
7 
8const rows = consoleService.renderRows("clients", result.responseSummary);
9const safeResult = consoleService.result({
10  sectionId: "clients",
11  operation: "read",
12  method: "GET",
13  path: "/api/qentrah/clients",
14  status: result.status,
15  response: result.responseSummary,
16  error: result.error,
17});

Render rows, sections, lifecycle, credentialSnapshot, and safeResult with your own UI framework.

WordPress And Server-Backed Apps

For WordPress or PHP-backed products, keep the same separation of responsibilities:

• Enqueue the browser button script in the admin screen or integration settings page.
• Point the button at a server route that starts OAuth.
• Store pending OAuth state in a server-side session or database table.
• Complete the callback on the server and save token data in encrypted storage.
• Proxy Qentrah resource calls through server endpoints.
• Render only sanitized connection status, section readiness, request summaries, and result summaries in the admin UI.

If your WordPress plugin uses a Node service or build step, you can use this package directly in that server layer. If your backend is pure PHP, mirror the same OAuth, webhook, and storage contract server-side, and use the browser bundle only for the connect button.