On Partial Results (Experience Closed) | INFONITE

Triggered when the user is done and the widget closes, but one or more sources are still working. Some administrations do not answer in real time — the CIRBE report from the Banco de España is the usual case — so the session keeps running in the background instead of holding your user in front of a spinner.

This event hands you everything retrieved so far.

This data is PARTIAL. It is not the final result.

The payload of this event always carries is_closed: false — that field is how you tell partial from final, wherever you read it. Sources that had not answered yet are simply absent from the data: not empty, not null — absent.

The session is still open. Do not treat this as the outcome of the verification and do not close the case on it.

The complete data arrives afterwards in On Flow Ended, whose payload carries is_closed: true. That is the only event that means the session is finished.

The payload

It is the same schema as the end event — FlowResultsSchema — so you parse it with the same code you already wrote. The only difference is what is in it: the sources that finished, and nothing else.

If an aes_key was provided during Create Session, the partial results inside the data payload are delivered encrypted in aes::Base64(IV + Ciphertext + Tag) format.

Encrypted Payload

If you configured an aes_key, this payload is encrypted. View step-by-step decryption walkthrough and code templates in the Payload Encryption guide.

If no aes_key was specified, the data payload is omitted (null), and you must retrieve the partial results manually using the session API.

What it is for

Use it to move early: show your user what you already have, or start the work that does not depend on the slow source. Then wait for es-public-administration:ended before treating the verification as complete.

Delivered at most once

You receive this event once per session, even though the flow may move in and out of the waiting state several times while the remaining sources finish.

As with every webhook, make your endpoint idempotent: a network-level retry must never create the record twice on your side.

Triggered when the user is done and the widget closes, but **one or more sources are still working**. Some administrations do not answer in real time — the CIRBE report from the Banco de España is the usual case — so the session keeps running in the background instead of holding your user in front of a spinner. This event hands you **everything retrieved so far**. <Warning title="This data is PARTIAL. It is not the final result."> The payload of this event always carries **`is_closed: false`** — that field is how you tell partial from final, wherever you read it. Sources that had not answered yet are simply **absent** from the data: not empty, not null — absent. The session is still open. Do not treat this as the outcome of the verification and do not close the case on it. The **complete** data arrives afterwards in [On Flow Ended](api:POST/es-public-administration:ended), whose payload carries `is_closed: true`. That is the only event that means the session is finished. </Warning> ## The payload It is the **same schema as the end event** — `FlowResultsSchema` — so you parse it with the same code you already wrote. The only difference is what is in it: the sources that finished, and nothing else. If an `aes_key` was provided during [Create Session](api:POST/es-public-administration/v1/manager/init), the partial results inside the `data` payload are delivered encrypted in `aes::Base64(IV + Ciphertext + Tag)` format. <Card title="Encrypted Payload" icon="fa-solid fa-key" href="/payload-encryption"> If you configured an `aes_key`, this payload is encrypted. View step-by-step decryption walkthrough and code templates in the **Payload Encryption** guide. </Card> If no `aes_key` was specified, the `data` payload is omitted (null), and you must retrieve the partial results manually using the session API. ## What it is for Use it to move early: show your user what you already have, or start the work that does not depend on the slow source. Then **wait for `es-public-administration:ended`** before treating the verification as complete. <Note title="Delivered at most once"> You receive this event **once per session**, even though the flow may move in and out of the waiting state several times while the remaining sources finish. As with every webhook, make your endpoint idempotent: a network-level retry must never create the record twice on your side. </Note>

Payload

The payload of this webhook request is an object.

event_class"EsPublicAdministrationV1FlowEvent"Required

Payload class discriminator — always this value for Spain Public Administration events.

app_idstringRequiredformat: "ObjectId"

customer_idstringRequired1-64 characters

session_idstringRequiredformat: "ObjectId"

producer"es-public-administration"Required

The flow that produced the event.

event"es-public-administration:partial"Required

The event type: partial.

status_codeenumRequired

Base status codes for widget flows Allowed values are:

READY: The flow is waiting for an input
WAITING: Flow is waiting for an external event
COMPLETED: The flow has finalized successfully
FAILED: The flow has failed
SYSTEM_CANCELLED: The flow has ben cancelled by the system
CLIENT_CANCELLED: The flow has been cancelled by the client
CUSTOMER_CANCELLED: The flow has been cancelled by the customer
TIMED_OUT: The flow has timed out
CONFIGURATION_ERROR: The flow has been rejected due to a configuration error

datestringOptionalformat: "datetime"

status_messagestring or nullOptional

dataobjectOptional

Partial results: everything retrieved at the moment the user closed the experience.

It is the same payload as the ended event, FlowResultsSchema, with the sources that had not answered yet simply absent. Parse it with the same code; do not expect every field to be present.
Delivered under the same rules as the final results: if an aes_key was provided when the session was created, this payload is encrypted (see the Payload Decryption section of the API introduction). If no aes_key was specified, this field is not informed (null) and the partial results can be retrieved through the session API.
This is not the end of the session. The pending sources keep working and the complete results arrive later, in ended. Treat this as an early view, not as a final answer, and do not close the case on it.

Response

200

Successful Response

422

Validation Error