oneapi
Sign in
Business v1 / Persoane

Person profile

A person's details (name, locality) plus the number of companies they appear in.

GET
https://oneapi.ro/api/business/v1/persoane/{id}

Path parameters

NameTypeDescriptionExample
idrequired string Internal identifier of the person — obtained from search responses; it is not a personal numeric code.

Query parameters

This route accepts no query parameters.

How it behaves

  • A name alone identifies nobody, and the register does not publish the national ID number. That is why every person carries an identificator (a UUID derived from name + county of birth + date of birth) and a judet_nastere. The date of birth is neither stored nor exposed — it only feeds the identifier. Where the register gives no date of birth (13% of mentions, mostly corporate liquidators), the person stays distinct at each company, so that no link is invented.
  • The profile of a person (internal identifier), with the number of companies they appear in. The actual companies are at /persoane/{id}/firme.

What it is for

  • A person's record in an analysis app, with the scale of their involvement.
  • Triaging search results by how many companies each person holds.
  • A stable header from which you chain to companies, roles and connections.

Response structure

All fields below live inside data.

FieldTypeDescription
id integer The internal identifier.
identificator string The person's stable identifier (UUID), derived from name + county of birth + date of birth. Unlike id, it does not change on reimport. Use it to tell whether the administrator of two companies is the same person or two namesakes.opțional
nume string The name.
judet_nastere string The county of birth, as published by the register. Together with identificator, it tells namesakes apart when displaying them.opțional
localitate string The locality.opțional
judet string The county.opțional
tara string The country.opțional
nr_firme integer The number of companies.

Response examples

GEThttps://oneapi.ro/api/business/v1/persoane/abecb6a3-ce1d-5648-b7c3-1ab11a3a6046
{
    "data": {
        "id": 16383590,
        "identificator": "abecb6a3-ce1d-5648-b7c3-1ab11a3a6046",
        "nume": "POPESCU A. ALEXANDRA",
        "judet_nastere": "Bucureşti",
        "nr_firme": 0
    }
}

Error codes

CodeSlugWhen it occurs
401neautentificatToken missing, invalid, expired or revoked.
403feature_indisponibilThe current plan does not include the feature the route depends on.
404negasitThe person [{id}] was not found.
422validareThe route takes no parameters apart from lang: any other parameter returns 422 instead of being ignored.
429cota_depasitaThe plan's monthly quota has been exceeded (see Retry-After).

All errors share the same shape. eroare.cod is stable and is the value you should branch on in code — not the text in mesaj, which may change.

{
    "eroare": {
        "cod": "validare",
        "mesaj": "The route takes no parameters apart from lang: any other parameter returns 422 instead of being ignored.",
        "detalii": {
            "id": [
                "The value sent does not satisfy the parameter rule."
            ]
        }
    }
}