# Check holder data with eID assertion

Validates holder data using an eID assertion before enrolling. Checks: mandatory fields, allowed values, LRA authorization for the eID type. See [checkDataWitheIDAssertion](https://docs.namirial.app/products/leandisposable/enterprise-documentation/developer-documentation/api-references/lean-checkdata/lean-checkdata-eid-assertion-method) and [How to enroll with eID assertion](https://docs.namirial.app/products/leandisposable/enterprise-documentation/developer-documentation/integration-guide/lean-ig-how-to-enroll-disposable-eid-assertion).

Endpoint: POST /api/certificate/{lraId}/checkDataWitheIDAssertion
Version: 26.1.0.3
Security: basicAuth, sslCertificate

## Security:

  - `basicAuth` (unknown)
    http basic

  - `sslCertificate` (unknown)
    mutualTLS

## Path parameters:

  - `lraId` (string, required)
    Local Registration Authority (LRA) identifier.

## Request fields (application/json):

  - `eidAssertionHolder` (object, required)
    eID assertion holder data. The `country` and `eIDType` together identify the eID method (e.g., IT-SPID, IT-EIDNAMIRIAL, AT-EID). The `assertion` format depends on the eID type.

  - `eidAssertionHolder.country` (string, required)
    Country code of the eID provider. ISO 3166-1 alpha-2 code. Together with `eIDType` identifies the eID method (e.g., IT-SPID, IT-EIDNAMIRIAL, AT-EID).
    Example: IT

  - `eidAssertionHolder.eIDType` (string, required)
    Type of eID assertion. Together with `country` identifies the eID method (e.g., IT-SPID, IT-EIDNAMIRIAL, AT-EID). Allowed values depend on LRA configuration.
    Example: SPID

  - `eidAssertionHolder.assertion` (string, required)
    Base64-encoded eID assertion. The format depends on `eIDType`.

  - `certificate` (object, required)

  - `certificate.password` (string, required)
    Certificate PIN.

  - `certificate.securityCode` (string, required)
    Certificate security code.

  - `certificate.fullData` (boolean)
    Enroll with full profile. Default: `false`.

  - `certificate.withoutUsageLimitLRA` (boolean)
    Omit LRA limitation of use (LoU). Default: `false`.

  - `certificate.type` (string)
    Disposable certificate type. See [allowed values](https://docs.namirial.app/products/leandisposable/enterprise-documentation/developer-documentation/api-references/lean-enum-types#disposabletype). Default: `DISPOSABLE`.
    Enum: "DISPOSABLE", "DISPOSABLE_30_DAYS", "LONG_LIVED", "DISPOSABLE_FEA"

  - `certificate.otpType` (string)
    OTP delivery method. See [allowed values](https://docs.namirial.app/products/leandisposable/enterprise-documentation/developer-documentation/api-references/lean-enum-types#disposableotptype). Default: `SMS`.
    Enum: "SMS", "EMAIL", "NO_OTP", "EXTERNAL_OTP"

  - `certificate.transactionLimit` (object)

  - `certificate.transactionLimit.value` (integer)
    Maximum transaction value.

  - `certificate.transactionLimit.currency` (string)
    Currency code. ISO 4217.

  - `certificate.limitationOfUse` (object)

  - `certificate.limitationOfUse.withoutUsageLimitLRA` (boolean)
    Omit LRA limitation of use. Default: `false`.

  - `certificate.limitationOfUse.language` (string)
    Language of the limitation of use text. ISO 639-1 alpha-2 code.

  - `contacts` (object)
    Holder contact information. Required if `otpType=SMS` or `otpType=EMAIL`. Provide `mobile` if `otpType=SMS`, `email` if `otpType=EMAIL`.

  - `contacts.email` (string)
    Email address of the holder. Required if `otpType=EMAIL`.

  - `contacts.mobile` (string)
    Mobile phone number in E.164 format with `+` prefix (e.g. `+390000000000`). Required if `otpType=SMS`.

  - `buReId` (string)
    Business relation identifier (optional).

## Request examples:

  - `IT-EIDNAMIRIAL with SMS OTP` (unknown)
    Check data with IT-EIDNAMIRIAL eID assertion. The assertion is a base64-encoded JSON format with current `iat` timestamp.

## Response 200:

  - `200` (unknown)
    Validation successful. The holder data is valid and the LRA is authorized for the specified eID type. Response body is empty.

## Response 500:

  - `500` (unknown)
    Application error. The backend returns HTTP 500 for all application errors, including validation failures and authentication errors.

## Response 500 fields (application/json):

  - `code` (integer, required)
    Application error code.
    Example: 242

  - `message` (string, required)
    Human-readable error description. For validation errors (code 242), includes field-level details in the format `Input parameter invalid: [{field=..., message=...}]`.
    Example: Input parameter invalid: [{field=disposableHolder, message=must not be null}]

## Response 500 examples:

  - `Validation error — missing or invalid field (code 242)` (unknown)

  - `Expired eID assertion (code 237)` (unknown)

  - `Invalid eID assertion (code 239)` (unknown)

  - `LRA not authorized for eID type (code 244)` (unknown)

  - `Authentication or authorization error (code 11002)` (unknown)

  - `Authorization error — user not authorized for this method or LRA (code 11002)` (unknown)

