# ElektroniskAkt

Tinglysningsretten
1.0.0

← Back to Main Page

## Overview

You can search for the following object types in the e-Act:

- Property

- Car

- Cooperative housing

- Person

- Corporation

- General powers of attorney

The search facilities generally allow the requester to specify search criteria, which may result in anywhere from 0 to (theoretically) infinitely many matches.

Therefore, E-Tinglysning imposes an upper limit on how many matches can be returned to the requester in a search result via the system-to-system interface.

### Endpoints

#### SenesteAendringTinglysningsobjektHent

Endpoint URL: `ElektroniskAkt/SenesteAendringTinglysningsobjektHent`

Description | Used to find the date of the most recent change to a registration object. The search is performed using the registration object identifier. The result consists of the date of the latest change.
Input | SenesteAendringTinglysningsobjektHent.xsd
Output | SenesteAendringTinglysningsobjektHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### AendredeTinglysningsobjekterHent

Endpoint URL: `ElektroniskAkt/AendredeTinglysningsobjekterHent`

Description | Used to find changed registration objects. The search is performed on the specified book and within the specified period, maximum one month. The result consists of a list with RegistrationObject and date of last change.
Input | AendredeTinglysningsobjekterHent.xsd
Output | AendredeTinglysningsobjekterHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### AliasSoeg

Endpoint URL: `ElektroniskAkt/AliasSoeg`

Description | Used to search for a document alias or parts thereof. e-TL searches based on the search criteria specified in the invocation. The result consists of the document aliases matching the criteria, along with the corresponding document UUID.
Input | AliasSoeg.xsd
Output | AliasSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### AndelsbogDokumentAktuelHent

Endpoint URL: `ElektroniskAkt/AndelsbogDokumentAktuelHent`

Description | Used to retrieve rights information for a document registered in the e-Act.
Input | AndelsbogDokumentAktuelHent.xsd
Output | AndelsbogDokumentAktuelHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### AndelsbogDokumentRevisionssporHent

Endpoint URL: `ElektroniskAkt/AndelsbogDokumentRevisionssporHent`

Description | Used to retrieve the historical view for a rights document from the revision trail.
Input | AndelsbogDokumentRevisionssporHent.xsd
Output | AndelsbogDokumentRevisionssporHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### AndelSoeg

Endpoint URL: `ElektroniskAkt/AndelSoeg`

Description | Used to search for one or more shares in the e-Act. e-TL searches based on the search criteria specified in the invocation. The result consists of the unique keys (identifiers) with which the shares are identified in the e-Act. The search is implemented with a number of restrictions for reasons of both performance and complexity. The search works by searching within specific use cases, each requiring different fields. If not enough fields are filled in for a use case, an error is returned. If enough fields are filled in for multiple use cases, only the result from the first matching use case is returned, in the order listed below. Currently, the keys and data volumes for the car register are manageable, so there are no restrictions on the number of search results. Therefore, it is possible that a restriction, e.g., 100 results, will be introduced. The number can be adjusted for performance and usability. Use cases: ShareIdentifier Municipality code Road code House number Floor Side Result 0..1 shares Document alias (Search for shares registered on a document) Result 0..* shares Error if document alias is from the wrong book Document identifier (Like search by document alias) Rights identifier (Search for shares linked to a right) Result 0..1 shares
Input | AndelSoeg.xsd
Output | AndelSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### AndelSummariskHent

Endpoint URL: `ElektroniskAkt/AndelSummariskHent`

Description | Used to retrieve an overview of all rights associated with the specified share.
Input | AndelSummariskHent.xsd
Output | AndelSummariskHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### BilbogDokumentAktuelHent

Endpoint URL: `ElektroniskAkt/BilbogDokumentAktuelHent`

Description | Used to retrieve rights information for a document registered in the e-Act.
Input | BilbogDokumentAktuelHent.xsd
Output | BilbogDokumentAktuelHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### BilbogDokumentRevisionssporHent

Endpoint URL: `ElektroniskAkt/BilbogDokumentRevisionssporHent`

Description | Used to retrieve the historical view for a rights document from the revision trail.
Input | BilbogDokumentRevisionssporHent.xsd
Output | BilbogDokumentRevisionssporHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### BilSoeg

Endpoint URL: `ElektroniskAkt/BilSoeg`

Description | Used to search for one or more cars in the e-Act. e-TL searches based on the search criteria specified in the invocation. The result consists of the unique keys (identifiers) by which the cars are identified in the e-Act. The keys in the car register consist of chassis numbers. The search is implemented with a number of restrictions for reasons of both performance and complexity. The search operates by searching within specific use cases, each requiring different fields. If not enough fields are provided for a use case, an error is returned. If enough fields are provided for multiple use cases, only the result from the first matching use case is returned, in the order listed below. Currently, the keys and data volumes for the car register are manageable, so there are no restrictions on the number of search results. A search by partial chassis number may potentially return a very large number of results. Therefore, it is likely that a restriction, e.g., 100 results, will be introduced. The number can be adjusted for performance and usability. Use cases: Chassis number Search by chassis number Long chassis number – 17 characters. Result 0..1 cars Short chassis number – up to 16 characters, with serial number Result 0..1 cars Partial chassis number 3-16 characters. Searches for chassis numbers that END with the search string. Result 0..* cars Document alias Search for cars registered on a document Result 0..* cars Error if document alias is from the wrong book Document identifier As search by document alias Rights identifier Search for car linked to a right Result 0..1 cars PersonSimpleIdentifier Searches for cars with a given debtor. Note that a search may match multiple persons. Result 0..* cars CPR / CVR Searches for cars with a given debtor Result 0..* cars
Input | BilSoeg.xsd
Output | BilSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

Example request:

    GET /s2s/ElektroniskAkt/BilSoeg HTTP/1.1
    Content-Type: application/xml
    Tinglysning-Message-ID: uuid:4128df9d-42df-42f9-a274-2d49c60bd728
    Tinglysning-Relates-To: s2s-http-xml-api-end2end-test
    Content-Length: 544

    <?xml version="1.0" encoding="UTF-8"?><BilSoeg xmlns="http://rep.oio.dk/tinglysning.dk/service/message/elektroniskakt/1/" xmlns:ns="http://rep.oio.dk/tinglysning.dk/schema/elektroniskakt/1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://rep.oio.dk/tinglysning.dk/service/message/elektroniskakt/1/ http://rep.oio.dk/tinglysning.dk/service/message/elektroniskakt/1/BilSoeg.xsd">
      <ns:BilSoegningKriterier>
        <ns:SoegStelnummer>VF7U6UF0012353662</ns:SoegStelnummer>
      </ns:BilSoegningKriterier>
    </BilSoeg>

Example response:

    HTTP/1.1 200 OK

    <ns:BilSoegResultat xmlns:ns="http://rep.oio.dk/tinglysning.dk/service/message/elektroniskakt/1/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsigModel="http://rep.oio.dk/tinglysning.dk/schema/model/1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://rep.oio.dk/tinglysning.dk/service/message/elektroniskakt/1/ http://rep.oio.dk/tinglysning.dk/service/message/elektroniskakt/1/BilSoegResultat.xsd"><ns1:BilSoegningInformationSamling xmlns:ns1="http://rep.oio.dk/tinglysning.dk/schema/elektroniskakt/1/"><ns1:BilSoegningInformation><ns2:BilIdentifikator xmlns:ns2="http://rep.oio.dk/tinglysning.dk/schema/model/1/"><ns2:Stelnummer>VF7U6UF0012353662</ns2:Stelnummer></ns2:BilIdentifikator><ns2:HaeftelserPaaBilIndikator xmlns:ns2="http://rep.oio.dk/tinglysning.dk/schema/model/1/">true</ns2:HaeftelserPaaBilIndikator><ns2:BilStruktur xmlns:ns2="http://rep.oio.dk/tinglysning.dk/schema/model/1/"><ns2:BilMaerke><ns2:BilFabrikatTekst>CITROËN</ns2:BilFabrikatTekst><ns2:BilModelTekst>JUMPY</ns2:BilModelTekst><ns2:BilVariantTekst>1,9 D</ns2:BilVariantTekst></ns2:BilMaerke><ns2:RegistreringsnummerTekst>AH34963</ns2:RegistreringsnummerTekst><ns2:FoersteRegistreringsAar>1998</ns2:FoersteRegistreringsAar></ns2:BilStruktur></ns1:BilSoegningInformation></ns1:BilSoegningInformationSamling><Signature xmlns="http://www.w3.org/2000/09/xmldsig#" Id="ID26264251975901-ReplySignature"><SignedInfo Id="ID26264251975902-ReplySignatureInfo"><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><Reference URI=""><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue>VUK29PkvODPmb24eS9Ke2dRXLZ0=</DigestValue></Reference><Reference Type="http://www.w3.org/2000/09/xmldsig#SignatureProperties" URI="#ID26264251975904-ReplySignatureProperty"><Transforms><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue>eo3g52fyXLfx+J9nQZkTGV6N78k=</DigestValue></Reference></SignedInfo><SignatureValue> </SignatureValue><KeyInfo><X509Data><X509Certificate> </X509Certificate></X509Data></KeyInfo><Object Id="ID26264251975903-ReplySignatureObject"><SignatureProperties><SignatureProperty Id="ID26264251975904-ReplySignatureProperty" Target="#ID26264251975901-ReplySignature"><dsigModel:UnderskriftTidspunkt>2025-10-31T15:30:44</dsigModel:UnderskriftTidspunkt></SignatureProperty></SignatureProperties></Object></Signature></ns:BilSoegResultat>

#### BilSummariskHent

Endpoint URL: `ElektroniskAkt/BilSummariskHent`

Description | Used to retrieve a rights overview for all rights on the specified car.
Input | BilSummariskHent.xsd
Output | BilSummariskHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### DokumentAktuelHent

Endpoint URL: `ElektroniskAkt/DokumentAktuelHent`

Description | Used to retrieve rights information for a document registered in the e-Act.
Input | DokumentAktuelHent.xsd
Output | DokumentAktuelHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### DokumentTinglysningsobjekterHent

Endpoint URL: `ElektroniskAkt/DokumentTinglysningsobjekterHent`

Description | Used to retrieve associated registration objects for a document registered in the e-Act.
Input | DokumentTinglysningsobjekterHent.xsd
Output | DokumentTinglysningsobjekterHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### DokumentRevisionssporHent

Endpoint URL: `ElektroniskAkt/DokumentRevisionssporHent`

Description | Used to retrieve the historical view for a rights document from the revision trail.
Input | DokumentRevisionssporHent.xsd
Output | DokumentRevisionssporHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### EjendomAdkomsterHent

Endpoint URL: `ElektroniskAkt/EjendomAdkomsterHent`

Description | Used to retrieve a rights overview for all titles for the specified property.
Input | EjendomAdkomsterHent.xsd
Output | EjendomAdkomsterHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### EjendomHistoriskAdkomsterHent

Endpoint URL: `ElektroniskAkt/EjendomHistoriskAdkomsterHent`

Description | Used to retrieve historical titles.
Input | EjendomHistoriskAdkomsterHent.xsd
Output | EjendomHistoriskAdkomsterHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### EjendomHaeftelserHent

Endpoint URL: `ElektroniskAkt/EjendomHaeftelserHent`

Description | Used to retrieve a rights overview for all encumbrances on the specified property.
Input | EjendomHaeftelserHent.xsd
Output | EjendomHaeftelserHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### EjendomIndskannetAktHent

Endpoint URL: `ElektroniskAkt/EjendomIndskannetAktHent`

Description | Provides access to the entire scanned deed for a property.
Input | EjendomIndskannetAktHent.xsd
Output | EjendomIndskannetAktHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### EjendomServitutterHent

Endpoint URL: `ElektroniskAkt/EjendomServitutterHent`

Description | Used to retrieve a rights overview for all easements on the specified property.
Input | EjendomServitutterHent.xsd
Output | EjendomServitutterHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### EjendomSoeg

Endpoint URL: `ElektroniskAkt/EjendomSoeg`

Description | Used to search for one or more properties in the e-Act. e-TL searches based on the search criteria specified in the invocation. The result consists of the unique keys (identifiers) by which the properties are identified in the e-Act. The result page contains 20 results; "sidefra" specifies which page number you want the result from. The search is implemented with a number of restrictions for reasons of both performance and complexity. The search works by searching within specific use cases, each of which has different required fields. If not enough fields are filled in for a use case, an error is returned. If enough fields are filled in so that multiple use cases match, only the result from the first use case in the order listed below is returned. Use cases: SFE/BFE number Retrieves a Collective/Specific Real Property required: kms:LandPropertyIdentifier (sfe number) number of results: 0..1 property Cadastral number and Cadastral District Retrieves a property based on a cadastral number, cadastral district, and possibly additional information if it is a special property type. required: kms:CadastralDistrictIdentifier (national cadastral district number) OR CadastralDistrictDescription (precisely filled unique name, e.g., Pagterold, Skuldelev) For performance reasons, it is recommended to fill in the national cadastral district number. If provided, content in CadastralDistrictDescription is ignored. required: CadastralNumber (precisely filled, 4 digits + [0-3] letters) required/optional: PropertyType (if the field is not filled, a search is performed for a property without property type) required: if PropertyType is filled, fields belonging to the property type (e.g., condominium number) must also be filled Optional fields under property type, such as description, are not considered in the search. The search is strict regarding the entry of property type. For example, if you search for a property of type "land," the search will only return a result if the property type in the search is set to "land." response: All cadastral numbers of the property matching the search. If no result is found for the cadastral number, a search is performed for historical cadastral numbers that match. response: 0..1 property. A cadastral number belongs to exactly one property. Address Address search. Searches for an exact match on street name, city, and house number. required: StreetName, HouseNumber required: PostalCode (preferred) OR City optional: Floor, DoorSide response: Max 20 results. This number can be changed without notice if performance requirements dictate. No support is provided for searches without house number. Document/Rights search Retrieves the property or properties associated with a specific document or right. required: AktHistoriskIdentifikator OR DokumentAliasIdentifikator OR DokumentUUID OR RettighedUUID response: Max 100 results. This number can be changed without notice if performance requirements dictate. Unregistered area Retrieves a property that contains an unregistered area. UnregisteredIdentifier (unique e-TL identifier for an unregistered area) OR UnregisteredAreaDescription Response: 0..1 property if identifier is specified. Max 100 properties if searching by description.
Input | EjendomSoeg.xsd
Output | EjendomSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### EjendomStamoplysningerHent

Endpoint URL: `ElektroniskAkt/EjendomStamoplysningerHent`

Description | Used to retrieve basic information for a property.
Input | EjendomStamoplysningerHent.xsd
Output | EjendomStamoplysningerHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### EjendomSummariskHent

Endpoint URL: `ElektroniskAkt/EjendomSummariskHent`

Description | Returns basic information as well as a rights overview for titles, easements, and encumbrances on the requested property. Source: 69056-v2-Baseline e_TL.DOC, ch. 6, "Land Registry Information on a Single Property". The property is specified by the unique keys (identifiers) by which the property/properties are identified in the e-Act.
Input | EjendomSummariskHent.xsd
Output | EjendomSummariskHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### EjendomUdskriftBestil

Endpoint URL: `ElektroniskAkt/EjendomUdskriftBestil`

Description | Ordering a signed paper printout with land registry information for a property.
Input | EjendomUdskriftBestil.xsd
Output | EjendomUdskriftBestilResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### FuldmagtAndelSoeg

Endpoint URL: `ElektroniskAkt/FuldmagtAndelSoeg`

Description | Search for powers of attorney.
Input | FuldmagtAndelSoeg.xsd
Output | FuldmagtAndelSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### FuldmagtBilSoeg

Endpoint URL: `ElektroniskAkt/FuldmagtBilSoeg`

Description | Search for powers of attorney.
Input | FuldmagtBilSoeg.xsd
Output | FuldmagtBilSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### FuldmagtFastEjendomSoeg

Endpoint URL: `ElektroniskAkt/FuldmagtFastEjendomSoeg`

Description | Search for powers of attorney.
Input | FuldmagtFastEjendomSoeg.xsd
Output | FuldmagtFastEjendomSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### FuldmagtLoesoereSoeg

Endpoint URL: `ElektroniskAkt/FuldmagtLoesoereSoeg`

Description | Search for powers of attorney.
Input | FuldmagtLoesoereSoeg.xsd
Output | FuldmagtLoesoereSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### LoesoereSoeg

Endpoint URL: `ElektroniskAkt/LoesoereSoeg`

Description | Used to search for one or more movables in the e-Act. e-TL searches based on the search criteria specified in the invocation. The result consists of the unique keys (identifiers) by which the movable is identified in the e-Act. The search is implemented with a number of restrictions for both performance and complexity reasons. Currently, the keys and data volumes in the person register are manageable, so there are no restrictions on the number of search results. Therefore, it is very likely that we will set a restriction, e.g., 100 results. This number can be adjusted for performance and usability. Use cases: MovableIdentifier Result: 0..1 movable Document alias Search for movables registered on a document Result: 0..* movables Error if document alias from the wrong register Document identifier Like search by document alias Rights identifier Search for movables attached to a right Result: 0..1 shares
Input | LoesoereSoeg.xsd
Output | LoesoereSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### LoesoereSummariskHent

Endpoint URL: `ElektroniskAkt/LoesoereSummariskHent`

Description | Used to retrieve a rights overview for all rights on the specified movable.
Input | LoesoereSummariskHent.xsd
Output | LoesoereSummariskHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### PersonbogDokumentAktuelHent

Endpoint URL: `ElektroniskAkt/PersonbogDokumentAktuelHent`

Description | Used to retrieve rights information for a document registered in the e-Act.
Input | PersonbogDokumentAktuelHent.xsd
Output | PersonbogDokumentAktuelHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### PersonbogDokumentRevisionssporHent

Endpoint URL: `ElektroniskAkt/PersonbogDokumentRevisionssporHent`

Description | Used to retrieve the historical view for a rights document from the revision trail.
Input | PersonbogDokumentRevisionssporHent.xsd
Output | PersonbogDokumentRevisionssporHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### PersondokumentSummariskHent

Endpoint URL: `ElektroniskAkt/PersondokumentSummariskHent`

Description | Used by city and bailiff courts to retrieve an overview of wills and financial conditions.
Input | PersondokumentSummariskHent.xsd
Output | PersondokumentSummariskHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### PersondokumentSkifteretHent

Endpoint URL: `ElektroniskAkt/PersondokumentSkifteretHent`

Description | Used by probate court to retrieve an overview of wills and marriage contracts.
Input | PersondokumentSkifteretHent.xsd
Output | PersondokumentSkifteretHentResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### UdskriftBestil

Endpoint URL: `ElektroniskAkt/UdskriftBestil`

Description | Ordering a signed paper printout with land registry information for a property, vehicle, share, or movable.
Input | UdskriftBestil.xsd
Output | UdskriftBestilResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent

#### VirksomhedSoeg

Endpoint URL: `ElektroniskAkt/VirksomhedSoeg`

Description | Search by CVR number
Input | VirksomhedSoeg.xsd
Output | VirksomhedSoegResultat.xsd
Error handling | See the general section regarding this.
Security | Simple web service (i.e., based on HTTP)
Interaction pattern | Request-response
Call effect | Idempotent