INTEGRATIONS & DEVELOPER API

Every integration method in one place.

Install the JavaScript widget or Chrome extension, pass user identity, and optionally send events to a secure webhook.

Identity comes from your product

PentaScope does not guess identity. Your product passes the current login context, so each issue has the real user, ID and session. Public visitors stay explicitly anonymous.

Host product providesid · name · email · role · sessionNever send the user's password or access token.

Connector workflow

User identity

The widget reads ID, name, email and role from the currently signed-in user. Guests are recorded as Anonymous with a session ID.

Issue capture

PentaScope stores the route, screen, item, evidence and request/response context.

Optional webhook

Use a generic webhook on report, on approval, or on both events.

Status sync

The connector receives issue.created or issue.approved and can return the external task link.

One configuration per product

<script src="https://pentascope.example.com/qa-widget.js"></script>
<script>
QATest.init({
  apiUrl: "https://pentascope.example.com/api",
  token: "YOUR_WIDGET_TOKEN",
  system: "My Product",
  user: () => ({
    id: currentUser.id,
    name: currentUser.name,
    email: currentUser.email,
    role: currentUser.role
  }),
  userStory: () => currentStory,
  tracker: {
    provider: "generic-webhook",
    createOn: "approve", // report | approve | both
    project: "Engineering",
    board: "Product Bugs",
    webhookUrl: "https://YOUR-SERVER/qa-connector"
  }
});
</script>

Point webhookUrl to a secure server-side connector responsible for authentication and any future external-system mapping.

API structure and payload

POST /api/issuesJSON

system · route · screen · user · request/response · evidence

POST /api/test-runsJSON

mode · scenarios · cases · status · duration · issues

POST /api/project-documentsJSON

SRS / Test Cases → requirements → traceability

POST /api/test-commandsJSON

project · role · data profile · selected requirements

GET /api/system-logsJSON

frontend · API · upload · agent errors

Response contract{ ok, id, status, correlationId, durationMs, errors[] }The correlation ID links UI activity, API calls, logs and defects.

Generic, extensible webhooks

issue.created

Send an event when an issue is detected.

issue.approved

Send after operator approval.

Status sync

Store the external reference, delivery state and retries.

Keep integration secrets server-side

Never place an external-system secret in page code. The widget calls a secure connector that owns credentials on the server.