Du er ikke logget på
Teledata person matcher

Welcome to the documentation of the Teledata person matcher. Here you will find the following:

How is it working?

The teledata person matcher will try to find a person that matches the information provided. If there is not a perfect match it will try to find a person that could be the person requested. The specific matchcode for the matcher will reflect how good a match it was, and what kinds of liberties was taken to find the result.

Matching

Teledata person matcher matches on the following domains:

Domain ID Description
Personer (Teledata) tele_per Personer fra den danske telefonbog (også kaldet §34-data).

The matching algorithm will handle incorrect spelling and typos in the input in order to find a match. See examples of this in the examples section below.

Using Teledata person matcher API

The API for Teledata person matcher follows the standard API for matchers.

The Request

To find a match using Teledata person matcher, you need to make a GET request that looks as follows:

https://apps.conzoom.eu/api/v1/match/dk/tele_per?in_x1=?&in_x2=?...

Input Arguments

As explained in the general documentation you pass the input to the Teledata person matcher in as the in_* query string parameters. For Teledata person matcher you can use the following in_* parameters:

Parameter Name Description
in_phone_number Phone number Supply the phone number.
in_name Name This argument must contain the name of the person.
in_kvhx Kvhx Use this argument if you have the kvhx or kvh. If you supply this, then you can omit the other arguments.
in_muni Kommune code If used, this argument must contain the kommune code.
in_strcode Street code If used, this argument must contain the street code.
in_stednavn Stednavn Stednavn is a town name that is used as part of a Danish address, when the street name of an address appears in multiple towns within the same post code.
in_adr Address Use this argument if you have the entire address as a single text string. If you supply this, then you can omit the other arguments.
in_houno House number If used, this argument must contain house number and/or letter. The argument can also handle floor/apartment number if this comes after the house number.
in_str Street If used, this argument must contain the street name. The street name can optionally be followed by housenumber/letter and floor/apartment number, but these can also be supplied as seperate arguments if desired.
in_pcode Post code / City If used, This argument must contain the post code and/or postaldistrikt/town/city name.
in_apt Apartment If used, this argument should contain floor, apartment number and/or door specifier.

If you have the entire address text in a single string, then it would suffice to use in_adr. Otherwise use the more specific in_* arguments above to supply the address you want to match.

Optional parameters

You can add the following optional arguments as query string parameters:

The Response

The structure of match response is described here in the general documentation. For specific examples, see the example section below.

Batching

If you need to do multiple match requests, you can batch them using a batch request. This works in a very similiar way to the single match request.

Examples

The following example will try to match the person named Britt Pedersen on the address Vestergade 22, 8700 Horsens:

https://apps.conzoom.eu/api/v1/match/dk/tele_per?in_name=Britt Pedersen&in_adr=Vestergade 22, 8700 Horsens

The following example will try to match the person named Svend Otto Bryrup with the phonenumber 27326700:

https://apps.conzoom.eu/api/v1/match/dk/tele_per?in_phone_number=27326700&in_name=Svend Otto Bryrup 

Match Variables

In order to tell how good a match was, or the reason why no match was found, the Teledata person matcher returns the match variables.

A match variable outputs a category, which tells something about how good a match was. Below you can see the categories for the different match variables. Normally you only need to use one of them, unless you are investigating why a particular input is not matching as expected.

Detailed Match Variable

The detailed match variable is defined specifically for the Teledata person matcher. It would for most scenerios suffice to use this.

Specifik Matchkode - tele_per_matchlvl_detail

ID Name Description
m1 Sikker
m2 Sandsynlig
m3 Usikkert
fmp Sikker familiematch, måske rigtig person
fa1 Sikker familiematch
fa2 Sandsynlig familiematch
fa3 Usikker familiematch
xim Usikker familiematch
xvn Virksomhedsnavn
xtn Tomt navn
i Utilstrækkeligt input
am Mere end en person matcher

Generic Match Variables

The generic match variables has some common categories that are shared among different matchers. These are useful if you are programming generically against different matchers, and want a common way of handling matches.

There is a generic match variable for each domain that is being matched. Therefore, these variables can be useful to inspect if you interested in matches on a particular domain.

Matchkode - tele_per_matchlvl

ID Name Description
i Utilstrækkeligt input
x Ingen match
a Tilnærmet match
m Match