Infer ID type

The /infer-type endpoint infers the most plausible ID types for a raw identifier string when its nature is unknown or ambiguous.

It analyses the input against all supported ID types and returns a ranked list of candidates with associated confidence scores.

This endpoint performs format, checksum, and pattern analysis only. It does not verify existence or query external registries.

Making a request

The endpoint supports GET and POST requests.
Parameters may be provided via path segments, query parameters, or JSON body fields.

1
### JSON body
2
POST https://api.verifyvat.com/v1/infer-type
3
Content-Type: application/json
4
{
5
    "id": "{id}",
6
    "country": "{country}"
7
}
8

9
### Path segment
10
POST https://api.verifyvat.com/v1/infer-type/:id
11
Content-Type: application/json
12
{
13
    "country": "{country}"
14
}
15

16
### Query parameters
17
GET https://api.verifyvat.com/v1/infer-type?id={id}&country={country}
18

19
### Mixed
20
GET https://api.verifyvat.com/v1/infer-type/:id?country={country}

Parameters

1
### Single value
2
POST { "region": "EMEA" }
3

4
### Comma-separated list
5
GET "?country=NO,IT"
6

7
### Array
8
POST { "country": ["NO", "IT"] }

Response structure

Responses use the common Response envelope.

Within data, the structure is:

If no supported format matches the input, the response will include an empty candidates array.

Each candidate includes:

Candidates are ranked by confidence with deterministic matches with checksum validation receiving the highest score.

The details object contains the ID acronym, formal name, formatting patterns, expected country, registry sources, and validation method.

Real-world examples

1. Straightforward Norwegian national ID

The system recognises a Norwegian organisation number with full confidence. It also suggests the equivalent VAT number with slightly lower confidence.

2. Structurally invalid under local rules

Norwegian organisation numbers must be 9-digit numbers with a valid checksum.
The input 9955258289 fails that check, so no candidates are returned.

3. A globally recognisable LEI number

LEI numbers often arrive fragmented or with spaces, type inference handles that reliably.

Recommended usage

Type inference determines ID type, not entity existence. A typical flow is:

1. Call /infer-type
2. Select the highest-confidence candidate
3. Pass the result to /verify for ID verification
4. Persist the selected type and canonical ID
5. Handle empty candidate sets explicitly