One contract
The same parameters and the same response structure for every body.
Developers
Govreader runs on the Wealthreader API: HTTPS, form parameters and JSON responses. If you already integrate Wealthreader, you already know how to integrate Govreader.
Send your API key and the document code. The response includes the session and the QR code that the data subject must approve with Cl@ve.
curl https://api.wealthreader.com/entities/ \
-d api_key=$API_KEY \
-d code=declaracion_renta
Your customer scans the code with the Cl@ve app and confirms. You repeat the call with the session to collect the result.
curl https://api.wealthreader.com/entities/ \
-d api_key=$API_KEY \
-d code=declaracion_renta \
-d session=$SESSION \
-d otp=PUSH
Normalised data and the original document encoded in Base64, ready for your file.
Example using a personal income tax return. The values are illustrative.
{
"success": true,
"payload": {
"tax_returns": [
{
"model": "100",
"fiscal_year": 2025,
"filing_date": "2026-05-14",
"filing_type": "individual",
"result_amount": -1284.36,
"secure_verification_code": "QJ7M4KXT9PLD2WHV",
"xml_file": "PD94bWwgdmVyc2lvbj0i…",
"pdf_file": "JVBERi0xLjcK…"
}
]
}
}
The same parameters and the same response structure for every body.
Documented codes that distinguish an unapproved access, a body under maintenance or a report issued with a delay.
Some bodies, such as the Banco de España, do not deliver the report instantly. The API tells you so, and you collect it when it is ready.
Full API reference, with response schemas and error codes.
We will walk you through the complete flow — identification, request and response — using the cases that matter most to you.