Company risk data

UK Company Risk Data API

Consume UK company risk signals as structured evidence, with the source coverage and uncertainty needed to interpret a score safely.

Claim your key Read the quickstart

What it makes possible

A public-record check that keeps its provenance

Growth and Enterprise keys receive risk_signals on the entity response and can use the risk endpoint for the signal object alone. The score is made from confirmed flags; coverage, indeterminate flags, score_is_floor, and potential_score prevent an incomplete record from looking more certain than it is.

Ask for a risk-bearing profile

Use the entity profile when the workflow needs supporting company data too, or GET /entity/{company_number}/risk when it only needs the risk object. risk_signals is a paid feature and is omitted for Free keys; absence is not a clean result.

Act on stable codes

Match rules to published flag codes such as INSOLVENCY_ACTIVE, COMPANY_DISSOLVED, ACCOUNTS_OVERDUE, OUTSTANDING_CHARGES, and ALL_ASSETS_CHARGED. Codes are stable and only added to, which makes them safer workflow inputs than prose.

Read the confidence boundary

When score_is_floor is true, the score is a lower bound because a required source was unavailable or a relevant check was indeterminate. potential_score provides the worst-case ceiling from those indeterminate flags, capped at 100.

Response surface

Fields to put in the workflow

The response uses named slabs, stable enum values, and null or empty values instead of silently omitting fields.

score and potential_score: Confirmed risk points and the worst-case ceiling after indeterminate flags are included.
score_is_floor: True when the visible score is only a lower bound, so a low value must not be read as low risk.
coverage: Risk-bearing sources actually consulted for the score. A missing source was not assessed.
flags and indeterminate: Confirmed flags, plus flags that could not be evaluated and the source-related reason.

Interpretation

A score is not a decision by itself

Risk signals report deterministic conditions from the returned record. For example, an outstanding registered charge can be routine for a financed company; it is a prompt to inspect creditor priority, not a conclusion. Pair flag codes with the underlying profile, coverage, and the workflow's own review policy.

Review prompts

Which confirmed conditions should stop, route, or annotate this case?
Were the Companies House, PSC, insolvency, and charge sources assessed for this score?
Is the score a floor because a source or check could not be evaluated?
What does the source record say behind a triggered flag?

First request

Start with a company number

curl "https://api.rotuli.co.uk/v1/entity/00445790/risk" \
  -H "Authorization: Bearer uk_live_YOUR_KEY"

The Free tier includes 500 requests per month with no card required. See the API reference for the full response schema and data sources for licence and freshness details.

Guide: screen company risk signals safely