API for integrations

Wisec exposes a small, read-only API so a third party can verify your supply-chain hygiene without you sending them anything.

The important part is who holds the credential: you issue the key, you hand it over, you revoke it. Wisec never transmits your data to a partner. You delegate a read access, and every key created or revoked is recorded in your own audit log.


Getting a key

In the dashboard, Settings → API keys (admin only, paid plans). Give the key a name describing what will use it, optionally an expiry date, and copy the token: it is shown once. We store only its fingerprint, so we could not show it to you again even if you asked.

Revoking is immediate. A revoked key is kept rather than deleted: the record is what shows an auditor that an access existed between two dates and was withdrawn.

Calling it

bash
curl -H "Authorization: Bearer wsk_..." \
  https://api.wisec.io/api/v1/partner/exposure

All endpoints are GET, scoped to the organization that issued the key. There is no write endpoint: a machine credential that can change something is a machine credential that can destroy something, and no integration has asked for that.


Endpoints

GET /api/v1/partner/projects

json
{
  "projects": [
    {
      "id": 1610620,
      "name": "payment-service",
      "last_build": "2026-09-24T10:46:55Z",
      "security_score": 71,
      "open_alerts": 3
    }
  ]
}

The score runs from 0 to 100 and higher is better. Its formula is published in full on the security score page.

GET /api/v1/partner/builds

Optional parameters: project_id, and limit (50 by default, 200 maximum).

json
{
  "builds": [
    {
      "id": 4,
      "project_id": 1610620,
      "project_name": "payment-service",
      "commit_hash": "11b86937adf0f8e8bb4c4514c0eed037307ce3f0",
      "branch": "main",
      "timestamp": "2026-09-24T10:46:55Z",
      "verification_status": "VALID",
      "analysis_status": "COMPLETED",
      "security_score": 71,
      "score_version": 3,
      "alert_count": 4,
      "event_hash": "a57c6f3578cc99ae1cc9959d3167baa2eae23bc097477c6ecb72325c2f0ca678",
      "previous_event_hash": "3a07e20c7749bcb9943e925f26f1a63fe0a54081b8b542096a6c38a653875943",
      "ipfs_cid": "QmSbkM2zFpMMc49WA7gyAhYDvviT51aumXGm4aikFmEPU1",
      "slsa_attestation_cid": "QmZPmFFCEcWRCcSVCBMV8Jbi2oWLgr5p1169cAsoeLz3TL",
      "rekor_log_index": 2936744143,
      "vex_attestation_cid": "QmeSvSTPdnVP3twFB5vxDTa3pbZNcsnKfTM4nLZ4QJ7Z4s",
      "vex_rekor_log_index": 2936744694
    }
  ]
}

Every field after event_hash is a proof you can check without us: fetch the anchored manifest and the two attestations by CID from https://api.wisec.io/ipfs/<cid>, and look up the transparency log entries at https://search.sigstore.dev/?logIndex=<index>. previous_event_hash links this build to the one before it, which is what makes the chain verifiable end to end.

score_version travels with the score because two versions do not compare. Plotting scores from different versions as one series reads a change of formula as a change of security.

GET /api/v1/partner/exposure

json
{
  "generated_at": "2026-09-24T16:03:30Z",
  "sla_critical_days": 7,
  "sla_high_days": 30,
  "open_by_severity": { "CRITICAL": 0, "HIGH": 3, "MEDIUM": 2, "LOW": 1 },
  "open_total": 6,
  "fixed": 12,
  "not_observed": 1,
  "accepted_risks": 2,
  "accepted_risks_overdue": 0,
  "contradicted_fix_claims": 0,
  "coverage": [
    {
      "project_id": 1610620,
      "project_name": "payment-service",
      "branch": "main",
      "last_build_at": "2026-09-24T10:46:55Z",
      "tools": [
        { "name": "Trivy", "version": "0.74.0" },
        { "name": "gitleaks" },
        { "name": "OSV (Wisec built-in)" }
      ]
    }
  ],
  "establishing": false
}

Read coverage before reading the counts. A finding total means nothing without saying what was searched for: zero critical findings from a pipeline running no scanner is not a result. A project with an empty tools list proves nothing about its counts, in either direction.

Two figures are reported separately on purpose. fixed means the tool that found it ran again and no longer reports it. not_observed means it stopped being reported by a tool that did not run, which is not an achievement and is never counted as one.

establishing is true while there is not enough history for remediation figures to mean anything.


What this API deliberately does not expose

Not an oversight, a decision: no findings, no secrets report, no email addresses, no file lists.

What a customer delegates has to be legible to them. "My partner can see that I notarise my builds and how exposed I am" is something a CISO signs off. "My partner can read every finding and every leaked secret" is not, and a product that offered the second would deserve the refusal it would get.

If your integration needs something that is not here, ask: the surface is small because it is new, not because it is finished.


Limits and stability

MethodGET only
ScopeThe organization that issued the key
HistoryBounded by the customer's plan retention
Page sizelimit, 50 by default, 200 maximum
Rate limitGenerous, sized for CI traffic; a per-key quota will come with the first real usage

The surface is versioned by its path (/api/v1/). It is new and small, so tell us what you are building before relying on a shape: we would rather add a field than break yours.

Without a key

A single endpoint is public and needs no credential: GET /api/v1/verify/:hash returns the public verification of one build from its event hash. It is what the QR code on every notary certificate points to, and it is rate limited for a human opening a page rather than for a server integration.