How an organisation lets people report a problem from its own websites and apps (PLAN 3.7). Everything here is set in OpsCommand under Customer Support Centre → Report a problem button: turn it on (a key is issued), list the websites allowed to use it, and allow your own mobile apps if you have them. A new key stops the old one working at once.
On a website
Paste the snippet OpsCommand shows, once per page (it loads asynchronously and weighs under 15 kB, with no dependencies):
<script src="https://api.opscommand.dev/v1/widget.js" data-key="wk_…" data-service="marketplace" async></script>
data-service(optional) is the key of the service in your registry the page belongs to.data-locale="nb"(optional) shows it in Norwegian; otherwise the page's language decides.- Tell it what the person is looking at, so support does not have to ask:
OpsCommand.setReference('BK-1042'); // the booking or transaction
OpsCommand.setCorrelationId('req-abc'); // your last request's correlation ID
OpsCommand.open(); // open it from your own link as well as its own button
What it sends. What the person types, and — only if they tick send technical details — the page's address without its query or fragment, the time, browser, operating system, language, window size, the reference and correlation ID you gave, the last error message, and a screenshot they choose. What it never sends: your page's form fields, passwords, payment details, cookies, storage or tokens. It redacts its own text before sending (cards, tokens, keys, secrets); the server redacts again and strips the address's query and fragment again. It runs in a closed shadow root: it does not read your page or change its styles. The browser journey proves this on a page full of secrets (apps/web/e2e/journey.cjs, Report a problem widget).
From a mobile app
Apps make the same call the widget makes; allow apps in the settings first (an app has no web origin):
POST https://api.opscommand.dev/v1/widget/reports
Content-Type: application/json
X-Widget-Key: wk_…
{ "category": "application_error", "summary": "Payment screen freezes", "description": "Tapped pay twice",
"consentDiagnostics": true, "locale": "nb", "service": "marketplace-app",
"context": { "app": "Marketplace 4.2.1 (Android 15)", "time": "2026-11-06T07:00:00Z", "reference": "BK-1042",
"correlationId": "req-abc", "lastError": "SocketTimeoutException" } }
The answer is { "reference": "R-123", "trackingUrl": "https://…/track/…" }: show both to the person (the link is shown once; it follows the report from step 3.8). The schema is WidgetReport in the API description (/v1/openapi.json): every field is checked, unknown fields are refused, and nothing technical is accepted without consentDiagnostics. Never put tokens, passwords, payment details or personal identity numbers in any field.