Changelog

Vehicles: each registration in a field of its own

• last_registration_date, new: the registration in force, the day the vehicle was registered in country.
• first_registration_date: the vehicle’s first registration, in any country — the original one abroad for an imported vehicle. The same day as last_registration_date for a vehicle first registered in country.
• An absent one means only that the connection does not give it: the date present may well be both.
• registration_date is deprecated: depending on the connection it is one registration or the other. It is still there and filled as before — move to the two fields above. How to read them: Registration dates.
• Fixed: one connection returned the dates of vehicles, insurance, driving licences and identity documents one day early.

Vehicles: the incident report, flag by flag

The Vehicles data model now explains every incident flag in simple_vehicle_report.flags, with the DGT’s own name for it — Embargo, Precinto, Carga de entidad financiera, the deregistrations — and what it means for a vehicle you buy, finance or insure.

• inspection_expired, a new flag: the vehicle’s inspection (ITV) had expired on the day of the report, so the vehicle may not circulate. It is raised whichever source returned the vehicle; when no source issued a report, the report holds this flag alone.
• A flag always means incidents: has_incidents is true whenever flags names one. Having no flags never makes it false: a vehicle can carry incidents no flag names.
• Each flag once: flags holds each code once, in no particular order.
• The report comes when you ask for it: {"code": "vehicles_data", "configurations": {"simple_vehicle_report": true}}. Without it, no report is returned.

Spain Public Administration Flow: the administrations are yours to choose, in order

settings.allowed_sources is now an ordered list: the administrations your customer may be asked to sign in to, in your order of preference. The session goes to the first one that returns something still missing, and never back to one it passed over. Leaving an administration out spares your customer that sign-in, never data that another administration you allow returns. Without the list, your application’s default applies, else ["tgss", "aeat", "citizen_folder"]; a list that leaves a feature you ask for with no administration to return it is refused when you create the session. Every choice, and what it gives you, is in Choosing the administrations.

Spain Public Administration Flow: three more features

A session can now ask for three more features in settings.executions_features, alongside the ones it already reads:

• yearly_individual_tax — the person’s fiscal data from the Agencia Tributaria, year by year: the last three closed fiscal years by default, up to five with last_n_years. What employers, banks and lenders reported, payer by payer — every home loan with its lender and the person’s share — and the filed income-tax return attached, with its verification code. See Taxes.
• academic_data — the official degrees the person holds, university and non-university, from the Ministry’s registries through the Carpeta Ciudadana. See Academic Records.
• properties_data — the real estate the person holds in the Cadastre, through the Carpeta Ciudadana, with its cadastral value and every co-owner with their share. See Properties.

Labor check: a partly worked month no longer sets the income floor

The labor check’s income floor is the lowest of the last twelve months, after deductions. A month in which a job started or ended part-way through holds only the days worked, so for a recent hire it set the floor far below their salary. Such a month is now left out once at least two full months are on record; with less evidence it still counts, so the floor stays a floor. The method is now floor-v3.

Financial Rider: Open Banking in a widget we host, now documented end to end

Financial Rider has its public reference. Create a session from your backend — naming the markets and kinds of bank your customer may choose from, or the one bank to connect —, send your customer to the widget, and read one financial position merged from every bank they connected, up to three per session: accounts, cards, deposits, loans, investments and direct debits, in the same shape direct executions return.

Credit registry: the whole report, read from the Bank of Spain’s document

The credit registry is now filled from the official CIRBE report itself: every operation the holder has with each institution, the minor risks, and the totals, exactly as the Bank of Spain printed them. The report still travels as an attachment, and its metadata now carries the verdict on its digital signature — who signed it and whether the signature is valid.

The results of a Spain Public Administration session carry a new field: messages — situations the session detected while it ran, beside the records themselves. It travels in Get Session Results and in the payload of the ended and partial webhooks.

Nothing changes for an integration that ignores it. Most sessions detect nothing and the list is empty.

The second way to use INFONITE now has a section of its own: Direct Executions — the same engines, called straight from your backend, for the cases where nobody is in front of a screen.

It is not a new API. It is the one that has been running client integrations for a long time, written down properly for the first time: what to send, what comes back, what each state means, and the decisions that are easy to get wrong.

Two things: webhooks now have a page of their own, and the site has been reorganised around what you are actually trying to do.

Webhooks, explained end to end

The Webhooks page covers what the four events mean and when each one fires, the delivery envelope field by field, the authentication header your endpoint can require, the rules a destination URL has to satisfy, and the template variables and hooks_extra_data you can use to carry your own context into the call.

Two families of news: the Spanish labor check got substantially deeper, and the documentation gained a whole section dedicated to the data itself.

Spain Public Administration (v1)

• Guaranteed income floor: every labor check now carries an automatically computed income insight — a conservative minimum net income — deductions estimated conservatively, so it stays a floor — derived from the person’s certified contribution bases, with each current employer’s share broken out. It ships as part of the labor check model (income_floor — how to read it). Nothing to configure: it is computed automatically whenever you request the labor_check feature.

Some administrations do not answer in real time. The CIRBE credit risk report from the Banco de España is the usual case: it can take minutes to be produced, and until now your customer sat in front of a spinner waiting for it.

Spain Public Administration (v1)

• New callback event es-public-administration:partial: the widget now lets the customer go as soon as they are done, and this event delivers everything gathered up to that moment — the same FlowResultsSchema you already parse, with the pending sources simply absent from it. Use it to show your customer something immediately, or to start the work that does not depend on the slow source.

Welcome to the official launch of the new INFONITE Developer Portal and Documentation. This release consolidates our existing services, API references, and security integrations into a single unified developer platform:

Spain Public Administration (v1)

• Integration Reference: Ported the OpenAPI references and callback events (started, consent, ended) to the portal for real-time verification sessions with official registries (AEAT, TGSS, MEC, DGT, CIRBE).