Public Position

**One answer with every official record the execution retrieved** — the unified position of your customer across the administrations it reached: identity, academic records, driver and vehicles, employment and pensions, tax, properties and the credit registry, each family under its own key. The keys are described in [Data models](/guides/data-models/overview). <Tip> **This is the read we recommend, and the one to build on.** Every family below also has its own endpoint — [Labor check](api:GET/executions/results/{execution_id}/public/v1/labor-check), [Credit registry](api:GET/executions/results/{execution_id}/public/v1/credit/registry), and the rest — and they answer the same records. The difference is the number of requests: **one here, up to ten there**, for the same execution and the same data. Reach for a single family when you genuinely want one — an employment check on its own — and for anything that reasons over the whole person come here. </Tip> <Note> **Only what was requested appears.** A family that was not asked for, or that the administration did not answer, is absent rather than empty. Nothing here fails because a feature is missing — so read the keys rather than assuming them. </Note> | Status | Meaning | | :--- | :--- | | `200` | The position. | | `202` | `execution_still_processing` — this endpoint waits for the **whole** execution, unlike the per-family ones: a partial picture of somebody's official records is a misleading one. | | `404` | No execution with that id for your application, or it has been deleted. | <Note> **Server to server only.** This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read. </Note>