ObraXRAY Business · API
The risk of any construction company, by NIF, inside your application.
A call to our server returns the risk score, the verdict and the signals behind it, such as insolvencies, debts, licences, directors and court records. It's the same analysis as obraxray.com, available inside your product.
Request
curl https://obraxray.com/api/v1/contractors/514566680 \
-H "Authorization: Bearer obx_sk_..."Response
{
"object": "contractor",
"nif": "514566680",
"status": "complete",
"score": 78,
"verdict": "low_risk",
"color": "safe",
"checks": {
"insolvencyDeclared": 0,
"taxDebtor": false,
"ssDebtor": false,
"alvaraStatus": "valid",
"directorsWithIssues": 0
}
}What it returns
The answer you need about a construction company, in JSON.
Each response carries the score from 0 to 100, the verdict, the risk colour and 20+ signals behind the decision, the same analysis your user sees on obraxray.com, ready to use in your system.
Score and verdict
The score from 0 to 100, the risk colour and a clear verdict, from “no records” to “do not proceed”.
Detailed signals
Insolvencies by phase, tax and social-security debts, IMPIC licence, executions, ACT sanctions, civil cases.
Director risk
The link from directors to other companies, prior insolvencies and the phoenix pattern.
How it works
The analysis is done by NIF.
Request by NIF
GET /v1/contractors/{nif} with your key. If the company was already analysed, the response is immediate.
Background analysis
If the company is new, we start the analysis and return “analyzing”. Director analysis can take a few minutes.
Webhook when it's done
When the report is ready you get the analysis.completed event, signed with HMAC, without having to poll the API in a loop.
Where it fits
Built to bring risk into the flow you already have.
It's one call, from your server to ours, that fits wherever you already make decisions about companies.
Access and limits
Access keys are issued by us.
Each client gets their own key (obx_sk_…), issued by us, there's no automated sign-up yet. Each key has usage limits and an optional daily quota, and every request is logged. Talk to us and we'll set up access for your case.
Header authentication
The key goes in the Authorization header, never in the query string.
Per-key limits
Configurable usage limits and daily quota, with clear error responses.
What's behind it
9 official public sources, cross-referenced.
The score doesn't come from a single source, it's the result of cross-referencing 20+ checks across 9 official databases, with accumulated history and interpretation.
Want to test the API for your case?
We'll explain how it fits your case, give you a key and help with the integration, no commitment.
Prefer a visual seal on your site, with no server code? See the Embed