Skip to navigation

Platform updates and API changelog for INFONITE

You choose the administrations, and the order — the Banco de España and the DGT among them

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.

  • The Banco de España is an administration you can allow (bde): the CIRBE report from its own service, without signing in at the Social Security. With bde in the list, the report is read there and at no other administration.
  • The DGT is an administration like the others (dgt): the driving licence and the vehicles from the DGT itself, wherever you place it in the list.
  • The driving licence and the vehicles are combined across administrations: what one returns completes what another left out — licence categories, points history, vehicles —, so a later sign-in adds to them instead of repeating them.
  • fixed_parameters.birth_date, optional: give your customer’s date of birth and the Banco de España’s screen does not ask for it.

fixed_parameters.user_email is required whenever you ask for credit_registry_data, whichever administration reads the report: the CIRBE report is requested with it. A session without it is refused at creation with a 422 on fixed_parameters.user_email.

Spain Public Administration Flow: what Cl@ve allowed, said in the results

When your customer’s Cl@ve keeps an administration out, messages says so once, as an info under a stable message_id — What the session tells you:

  • clave_not_registered — they are not registered in Cl@ve. No administration that signs in with Cl@ve is offered again; the Social Security is still reached through its SMS access.
  • clave_level_insufficient — their Cl@ve registration is below the level an administration requires; at ["data", "credit", "registry"] when it is the Banco de España’s level for the CIRBE report. It replaces the credit_registry_insufficient_clave_level warning.
  • clave_access_unavailable — signing in with Cl@ve failed repeatedly, or the access was blocked. It may work again later, in a new session.

Spain Public Administration Flow: how a session ends, and why your customer left

  • status_code says who ended the session, status by status in How a session ends.
  • Abandoning one connection is not leaving the session. A sign-in your customer abandons can be started again; one abandoned after signing in keeps what had arrived, and the session moves on to the next administration. A session that connects no administration because your customer abandoned one closes as CUSTOMER_CANCELLED, no longer SYSTEM_CANCELLED.
  • Why they left: when your customer leaves from the widget, es-public-administration:ended carries user_feedback.reason — took_too_long, missing_information, distrust, unclear_steps or other — and, when they wrote something, user_feedback.feedback in their own words.
  • Leaving while a connection is in progress asks your customer to stay: going on is the obvious choice, and abandoning that one connection stays within reach.

Spain Public Administration Flow: records from a second administration reach the results

Pensions, income tax, academic degrees, properties and the CIRBE report are read from the connection that holds them, not from the first one that could have: a record that a second administration returned, when the first could not, now reaches the results.