Developer API · v1

Use verified research outside Impartis.

Connect applications, internal tools, websites, reporting systems, and AI workflows to the evidence your institution has already reviewed in Impartis—without giving those systems permission to rewrite the science.

Manage API keys Read quickstart OpenAPI spec

GET verified claims

curl "https://impartis.app/functions/api-v1?resource=claims&limit=25&q=PFAS" \
  -H "Authorization: Bearer imp_live_…"

Read-only

No science mutation

Scoped

Least privilege keys

Governed

Approved evidence only

API contract

A connection to the approved layer—not the working layer.

Organization API keys do not represent a human user. For that reason, v1 exports only Workspace-visible records. Personal and Restricted Team research stays inaccessible through organization API keys.

resource=research

Verified research.

Researcher-reviewed sources that are explicitly Workspace-visible.

resource=claims

Approved claims.

Claim text plus caveats, causal status, generalization boundaries, and source locations.

resource=reports

Evidence reports.

Leadership and topic synthesis already created inside Impartis.

resource=outputs

Approved outputs.

Only final communication that passed scientific, researcher, and communications approval.

Quickstart

One endpoint. Explicit scopes.

1. An Organization Admin creates an API key in Organization → Connections → Advanced tools.

2. Store the secret server-side. Impartis shows it only once and stores only a SHA-256 hash.

3. Send it as a Bearer token. Select a resource with the resource query parameter.

4. Use q, limit, and offset for filtering and pagination.

JavaScript · server-side

const response = await fetch(
  "https://impartis.app/functions/api-v1?resource=research&q=climate&limit=25",
  {
    headers: {
      Authorization: `Bearer ${process.env.IMPARTIS_API_KEY}`
    }
  }
);

const { data, meta } = await response.json();

Response envelope

{
  "data": [ ... ],
  "meta": {
    "count": 25,
    "total": 84,
    "limit": 25,
    "offset": 0,
    "next_offset": 25,
    "request_id": "...",
    "governance": "..."
  }
}

Scopes

Grant only what an integration needs.

research:readVerified research metadata and institutional summaries

claims:readResearcher-approved claims, caveats, boundaries, and source locators

reports:readWorkspace-visible evidence reports

outputs:readFinal communication approved for institutional use

Governance remains upstream.

No endpoint can approve or edit scientific claims.

No private source files or verbatim evidence passages are exported.

Restricted Team and Personal records are excluded from organization API keys.

Outputs appear only after scientific, researcher, and communications approval.

Every request is logged by key, resource, status, and request ID.

Build with institutional evidence

Let other software use what your institution already knows.

API access is managed by each Impartis organization. Keys can be independently scoped, audited, expired, and revoked.

Open Developer API