Setting up the HTTP client
The S2S (System-to-System) platform has undergone a modernization, transitioning from SOAP web services to a HTTP XML API server architecture. This upgrade requires all integrating parties to migrate their existing SOAP connectors to properly configured HTTP clients.
This guide provides a complete overview of:
-
HTTP XML API architecture details
-
Required configuration changes for client integration
-
Authentication and security requirements (mTLS with OCES certificates)
-
API endpoint structure
-
Digital signature implementation for XML payloads
Throughout this documentation, you’ll find Java code examples extracted from the reference client. These examples demonstrate code snippets that could be used for reference when making your own implementation.
Endpoints
The endpoints paths are structured in a way to maintain the naming of the SOAP endpoints. Each SOAP action have their own unique URL mapping.
All the endpoints follow the pattern:
xml-api.tinglysning.dk/<SOAP_WEB_SERVICE_NAME>/<SOAP_ACTION>
Example endpoints are presented below:
| SOAP Web Service | SOAP Action | Endpoint URL |
|---|---|---|
ElektroniskAkt |
BilSummariskHent |
xml-api.tinglysning.dk/ElektroniskAkt/BilSummariskHent |
TingbogAnmeld |
EjendomOpret |
xml-api.tinglysning.dk/TingbogAnmeld/EjendomOpret |
Abonnement |
AbonnementOpret |
xml-api.tinglysning.dk/Abonnement/AbonnementOpret |
OCES certifikat
All endpoints require mTLS, where the client uses a valid OCES certificate.
If a valid OCES certificate is not used for mTLS, the endpoints will respond with an HTTP status 400 Bad Request, and an error message in XML that follows the schema defined in Fejl.xsd.
In the event of a lack of OCES certification, the error message in XML will look like:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Fejl xmlns="http://rep.oio.dk/tinglysning.dk/schema/fault/1/">
<faultcode>Client</faultcode>
<faultstring>Der var intet SSL certifikat i requestet</faultstring>
</Fejl>Reference implementation
The Java reference client demonstrates how to create an SSLContext with an OCES client certificate and an OCES truststore.
This can subsequently be used to set up an HTTP client.
As shown in the Java reference client, an SSLContext can be created by:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
public static SSLContext createSslContext(ApiClientConfiguration configuration, SslStoreBundle sslStoreBundle)
throws SslFactoryException {
try {
KeyManagerFactory keyManagerFactory =
KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm());
keyManagerFactory.init(sslStoreBundle.getKeyStore(), sslStoreBundle.getKeyStorePassword());
TrustManagerFactory trustManagerFactory =
TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());
trustManagerFactory.init(sslStoreBundle.getTrustStore());
SSLContext sslContext = SSLContext.getInstance(configuration.getSslProtocol());
sslContext.init(
keyManagerFactory.getKeyManagers(), trustManagerFactory.getTrustManagers(), new SecureRandom());
return sslContext;
} catch (KeyStoreException
| NoSuchAlgorithmException
| UnrecoverableKeyException
| KeyManagementException exception) {
throw new SslFactoryException("Could not create Ssl context.", exception);
}
}
An HTTP client can then be created and configured with mTLS:
1
2
3
4
5
6
7
8
9
public static HttpClient create(ApiClientConfiguration configuration, SslStoreBundle sslStoreBundle)
throws SslFactoryException {
SSLContext sslContext = SslContextFactory.createSslContext(configuration, sslStoreBundle);
return HttpClient.newBuilder()
.sslContext(sslContext)
.connectTimeout(Duration.ofSeconds(configuration.getConnectTimeoutSeconds()))
.build();
}
Verification
Java reference client comes with connection tests. They are used to verify that successful connection to e-Tinglysning is possible.
To verify that OCES certificates are correct, update the application.properties file in Integration test package.
Then run one of the integration tests (for example ElektroniskAktSpec).
Alternatively, you can run gradle integrationTest to run all connection tests.
Example configuration of keystores is shown below:
1
2
3
4
5
6
7
8
9
10
11
12
13
ssl.keystore.system.certificate.path=test.pfx
ssl.keystore.system.certificate.password=Test1234
ssl.keystore.system.certificate.key.alias=testSystem
ssl.keystore.system.certificate.type=PKCS12
ssl.truststore.path=test.p12
ssl.truststore.password=Test1234
ssl.truststore.type=PKCS12
ssl.keystore.company.certificate.path=test.pfx
ssl.keystore.company.certificate.password=Test1234
ssl.keystore.company.certificate.key.alias=testCompany
ssl.keystore.company.certificate.type=PKCS12
Headers
The S2S server is configured to require a set of custom headers in each HTTP call. To make a successful request, you are responsible for configuring your HTTP client to provide these headers in your calls. This chapter provides an overview of the expected values and possible issues that you may encounter.
| Header | Required | Format |
|---|---|---|
Tinglysning-Message-ID |
Yes |
uuid:[uuid-v4] |
Tinglysning-Relates-To |
No |
String |
Tinglysning-Message-ID
The land registry message ID is a random UUIDv4 generated by the client before sending a new request to the S2S endpoint. This header is used to uniquely identify the full request-response process, and therefore it is required in every request. It also helps both parties debug problems more easily.
Header structure
The header consists of the prefix "uuid:" followed by a randomly generated UUIDv4. The header must not contain uppercase letters.
| Header name | Header value |
|---|---|
Tinglysning-Message-ID |
uuid:44b147ff-b221-43f7-be45-cdb55f085413 |
Expected errors
If the header is not provided, you can expect HTTP status 400 Bad Request with this XML response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Fejl xmlns="http://rep.oio.dk/tinglysning.dk/schema/fault/1/">
<ns2:faultcode xmlns="" xmlns:ns2="http://rep.oio.dk/tinglysning.dk/schema/fault/1/">Client</ns2:faultcode>
<faultstring>Følgende krævede header var ikke tilstede: Tinglysning-Message-ID</faultstring>
</Fejl>If the header has an invalid structure, expect HTTP status 400 Bad Request with this XML response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Fejl xmlns="http://rep.oio.dk/tinglysning.dk/schema/fault/1/">
<ns2:faultcode xmlns="" xmlns:ns2="http://rep.oio.dk/tinglysning.dk/schema/fault/1/">Client</ns2:faultcode>
<faultstring>Det modtagne MessageID er i invalidt format: uuid:ce01bb6d-3479-4975-8ab5-. Et MessageID skal være på formen uuid:[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}</faultstring>
</Fejl>Tinglysning-Relates-To
Sometimes your application needs to provide additional reference information in the call. You can use the "relates to" header for this purpose. This header is not required and expects a string value.
| Header name | Header value |
|---|---|
Tinglysning-Relates-To |
CASE-2024-001 |
Content-Type
All endpoints expect users to provide their request body in XML format. API is configured to receive XML and will also respond with XML. If left out, this header will be filled out automatically but you can also set it up manually.
| Header name | Header value |
|---|---|
Content-Type |
application/xml |
Expected errors
Providing a different value will result in request rejection with HTTP status 415 Unsupported Media Type and this message:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Fejl xmlns="http://rep.oio.dk/tinglysning.dk/schema/fault/1/">
<ns2:faultcode xmlns="" xmlns:ns2="http://rep.oio.dk/tinglysning.dk/schema/fault/1/">Client</ns2:faultcode>
<faultstring>Ikke understøttet Content-Type: 'test/test'. Indstil venligst 'Content-Type'-headeren til 'application/xml'.</faultstring>
</Fejl>Reference implementation
Given the correct SSL context and HTTP client setup (look at the Reference OCES implementation), you can create a successful call using the provided example from the Java reference client:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
public <T> HttpResponse<T> sendPostRequest(
String endpoint, String xmlPayload, HttpResponse.BodyHandler<T> bodyHandler)
throws IOException, InterruptedException {
URI fullUrl = URI.create(configuration.getBaseUrl() + endpoint);
HttpRequest request = HttpRequest.newBuilder()
.uri(fullUrl)
.header(TINGLYSNING_MESSAGE_ID, "uuid:ce01bb6d-3479-4975-8ab5-cdb8b203ab5e")
.header(TINGLYSNING_RELATES_TO, "test")
.header(CONTENT_TYPE,"application/xml")
.timeout(Duration.ofSeconds(configuration.getRequestTimeoutSeconds()))
.POST(HttpRequest.BodyPublishers.ofString(xmlPayload))
.build();
return httpClient.send(request, bodyHandler);
}
Signing of payload
This chapter describes how to digitally sign XML documents using OCES (Offentlige Certifikater til Elektronisk Service) certificates. The implementation supports multiple signature types for different use cases in Danish digital infrastructure. Signing the document remains the same between SOAP and HTTP.
Signature types
-
System Certificate Signing
Used for standard document operations such as data retrieval and searching. This must be used as the default unless stated otherwise.
-
Non-Repudiation Certificate Signing
Used for legally binding documents that modify existing data.
-
Disponent Role Signing
Used for legally binding documents where a person acts on behalf of another individual or company.
Most endpoints still require you to sign the document. If you are unsure about which signature type to use, check the request message XSD in the controller documentation. In most cases, system certificate signing will be the correct option.
Usage and implementation of signature types can be found in the reference client by examining these methods:
1
2
3
4
public void sign(Document document)
public void signWithNonRepudiation(Document document)
public void signAsDisponent(Document document)
public void signAsDisponentWithSystemCertificate(Document document)
Signature body
The signature takes the form of an encrypted string appended to the XML sent in the request body
Currently, the S2S server supports RSA_SHA1, RSA_SHA256, and RSA_SHA512 algorithms for signature methods and RSA_SHA1, RSA_SHA256 for digest. Creating signatures with other algorithms will result in document rejection. Due to security reasons, it is recommended to use at least RSA_SHA256, as RSA_SHA1 is not considered secure anymore.
All signatures follow the XML Digital Signature specification and include:
-
SignedInfo: Contains canonicalization method, signature algorithm, and references
-
KeyInfo: Embeds the X.509 certificate used for signing
-
Signature Value: The actual cryptographic signature
Differences between signing methods:
| Disponent signatures | Basic signatures |
|---|---|
Use XPath filtering to sign only specific parts of the document while excluding metadata and administrative elements |
The full document is signed in a designated element at the end of the XML |
Use CanonicalizationMethod.INCLUSIVE |
Use CanonicalizationMethod.EXCLUSIVE |
For disponent signatures, HTTP XML API will check for the correct XPath expression. Either one of following expressions could be used to exclude parts of the document from signing.
not(ancestor-or-self::xpathds:Signature) and not(ancestor-or-self::xpathanm:Procesinstruktion) and not(ancestor-or-self::xpathanm:AnmelderInformation) and not(ancestor-or-self::xpathmodel:TinglysningAfgift) and not(ancestor-or-self::xpathmodel:AnmelderOrdningSamling) and not(ancestor-or-self::xpathmodel:ForespoergselsIdentifikatorSamling) and not(ancestor-or-self::xpathmodel:UnderskriftsmappeSignaturSamling) and not(ancestor-or-self::xpathmodel:FuldmagtOrdningSamling)
not(ancestor-or-self::xpathds:Signature) and not(ancestor-or-self::xpathanm:Procesinstruktion) and not(ancestor-or-self::xpathanm:AnmelderInformation) and not(ancestor-or-self::xpathmodel:TinglysningAfgift) and not(ancestor-or-self::xpathmodel:AnmelderOrdningSamling) and not(ancestor-or-self::xpathmodel:ForespoergselsIdentifikatorSamling) and not(ancestor-or-self::xpathmodel:UnderskriftsmappeSignaturSamling) and not(ancestor-or-self::xpathmodel:FuldmagtOrdningSamling) and not(ancestor-or-self::xpathmodel:AktoerReference) and not(ancestor-or-self::xpathmodel:SagsReference) and not(ancestor-or-self::xpathxkom:EmailAddressIdentifier) and not(ancestor-or-self::xpathmodel:UnderskriftIkkeNoedvendigIndikator)
Here is example from reference client on how you can include XPath into your project:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
private static Reference createXpathReferenceForDisponent(XMLSignatureFactory signatureFactory)
throws InvalidAlgorithmParameterException, NoSuchAlgorithmException {
DigestMethod digestMethod = signatureFactory.newDigestMethod(DigestMethod.SHA256, null);
List<Transform> transforms = new ArrayList<>();
Transform excCanonicalization =
signatureFactory.newTransform(CanonicalizationMethod.EXCLUSIVE, (TransformParameterSpec) null);
XPathFilterParameterSpec spec = new XPathFilterParameterSpec(XPATH_SUBSET_V2, XPATH_SUBSET_NS_MAP);
Transform transformXpath = signatureFactory.newTransform(Transform.XPATH, spec);
transforms.add(transformXpath);
transforms.add(excCanonicalization);
return signatureFactory.newReference("", digestMethod, transforms, null, null);
}
Example usages
Since the S2S reference client expects the XML to be passed as String, current examples will parse to the Document using helper methods.
For data retrieval, a simple signature will suffice:
1
2
3
4
5
6
7
8
9
10
11
ApiClientConfiguration configuration = ApiClientConfiguration.getApiConfigWithAppProperties();
S2sHttpClient s2sHttpClient = S2sHttpClientFactory.create(configuration)
ElektroniskAkt elektroniskAkt = new ElektroniskAkt(s2sHttpClient)
DocumentSigner documentSigner = new DocumentSigner(configuration);
Document document = StringToDocumentMapper.stringToDocument(xmlPayload);
documentSigner.sign(document);
String signedXmlPayload = StringToDocumentMapper.documentToString(document)
HttpResponse<String> response = elektroniskAkt.getBilSummariskHent(xmlPayload, messageId, relatesTo)
When you need to change or add new data, signing with repudiation must be used. The example below shows a case when a disponent is involved in document creation. This requires two types of signatures at the same time:
1
2
3
4
5
6
7
8
9
10
11
12
ApiClientConfiguration configuration = ApiClientConfiguration.getApiConfigWithAppProperties();
S2sHttpClient s2sHttpClient = S2sHttpClientFactory.create(configuration)
TingbogAnmeld tingbogAnmeld = new TingbogAnmeld(s2sHttpClient)
DocumentSigner documentSigner = new DocumentSigner(configuration);
Document document = StringToDocumentMapper.stringToDocument(xmlPayload);
documentSigner.signAsDisponent(document)
documentSigner.signWithNonRepudiation(document)
String signedXmlPayload = StringToDocumentMapper.documentToString(document)
HttpResponse<String> response = tingbogAnmeld.postEjendomOpret(xmlPayload, messageId, relatesTo)
General error response
General failure response consists of HTML response with body that follows XML Fejl.xsd. Here is a result of example request with invalid UUID.
HTTP/1.1 400 Bad Request
Date: Thu, 31 Jul 2025 13:43:48 GMT
Server: Apache/2.4.59 (Win64) OpenSSL/3.1.5
Access-Control-Allow-Credentials: true
Referrer-Policy: same-origin
X-Frame-Options: DENY
Content-Type: application/xml;charset=UTF-8
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Access-Control-Allow-Origin: http://localhost:4200
Access-Control-Allow-Headers: origin, x-requested-with, content-type
Access-Control-Allow-Methods: PUT, GET, POST, DELETE, OPTIONS
X-Apache-Request-Id: (null)
X-Apache-Stats: Received: t=1753969428028952 Elapsed time: D=125634
X-Apache-Node: localhost
Connection: close
Transfer-Encoding: chunked
Content-Length: 432
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><Fejl xmlns="http://rep.oio.dk/tinglysning.dk/schema/fault/1/"><ns2:faultcode xmlns="" xmlns:ns2="http://rep.oio.dk/tinglysning.dk/schema/fault/1/">Client</ns2:faultcode><faultstring>Det modtagne MessageID er i invalidt format: uuid:44b147ff-b221-43f7-be45-. Et MessageID skal være på formen uuid:[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}</faultstring></Fejl>Service Categories
Administrative Services
Abonnement
| Operation | Description |
|---|---|
Subscribe to a single property. In response, you receive a Subscription Identifier that can be used for subsequent administration of the subscription. For notifications about incidents on the property, the subscription identifier is sent. |
|
Deletes the subscription to a single property. In response, you receive information that the subscription is inactive. |
|
Retrieves the status of a property subscription. Returns subscription details including whether the subscription exists. If the subscription is found, the date of creation is returned. |
Anmeldelsesstatus
| Operation | Description |
|---|---|
Retrieve the status of notifications/cases provided in AnmeldelseStatusHent. |
Bilagsbank
| Operation | Description |
|---|---|
Used to retrieve a copy of a document from the document repository. |
|
Used to submit notification documents to e-TL, which are to be referenced in a notification that is subsequently submitted via one of the notification operations. The digital signature identifies who owns the document. |
|
Used to delete a document in the document repository. |
|
Retrieves a list of UUIDs for the GML files available in e-TL. If a date is specified, only documents created on or after that date are returned. |
Brugerformular
| Operation | Description |
|---|---|
This operation allows an actor to retrieve a user form that has been submitted to the Registration Court. The response contains the User Form. |
|
This operation allows an actor to submit a user form for approval by the Registration Court. The response contains a User Form Identifier. The actual approval or rejection will be sent asynchronously via the BrugerformularNotifikationModtag service operation. |
|
This operation allows an actor to update a user form. Specifically, the validity period and which users may use it can be updated. |
|
This operation allows an actor to search for a user form in the e-TL solution using criteria such as user form name, description, owner, validity period, or invalid user forms. |
Erklæringssøgning
| Operation | Description |
|---|---|
Used to search for a declaration. If no search criteria are provided, all declarations are returned. |
Frasekatalog
| Operation | Description |
|---|---|
Ability to retrieve Phrase Identifier(s) for a Phrase Text (or Phrase Texts). e-TL always returns the same Phrase Identifier for the same Phrase Text. If the exact same phrase text exists in the phrase catalog, its UUID is returned; otherwise, the new text is created in the catalog. |
|
Ability to retrieve a Phrase for one or more Phrase Identifiers. e-TL always returns the same Phrase Text for the same Phrase Identifier. The e-TL signature on the response guarantees that the use of the Phrase Identifier always corresponds precisely to the Phrase Text. |
|
Ability to create phrases. e-TL returns Phrase Identifier(s) for the created phrase texts. The e-TL signature on the response guarantees that the use of the Phrase Identifier always corresponds precisely to the Phrase Text. |
Praesentation
| Operation | Description |
|---|---|
Generates snapshots for a notification message. |
|
Generates a text representation for the specified XML notification message. Snapshots are generated automatically. |
|
Generates a text representation for the specified XML notification message plus snapshots. |
|
Generates a PDF representation for the specified XML message including notifications, DokumentAktuelHent, SummariskHentResultat, AnmaerkningStatusModtag, and AnmeldelseSvarModtag. Snapshots are generated automatically. |
|
Generates a PDF representation for the specified XML notification message plus snapshots. |
Underskriftsmappe
| Operation | Description |
|---|---|
Inserts a notification document into the signature folder. A synchronous response is returned with a SignatureFolderIdentifier, which can subsequently be used to reference the document. An asynchronous notification is sent to the specified submitter. |
|
Retrieves and deletes a document from the signature folder. The response is provided as a notification. |
Inquiry Services
ElektroniskAkt
| Operation | 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. |
|
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. |
|
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. |
|
Used to retrieve rights information for a document registered in the e-Act. |
|
Used to retrieve the historical view for a rights document from the revision trail. |
|
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. |
|
Used to retrieve an overview of all rights associated with the specified share. |
|
Used to retrieve rights information for a document registered in the e-Act. |
|
Used to retrieve the historical view for a rights document from the revision trail. |
|
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. |
|
Used to retrieve a rights overview for all rights on the specified car. |
|
Used to retrieve rights information for a document registered in the e-Act. |
|
Used to retrieve associated registration objects for a document registered in the e-Act. |
|
Used to retrieve the historical view for a rights document from the revision trail. |
|
Used to retrieve a rights overview for all titles for the specified property. |
|
Used to retrieve historical titles. |
|
Used to retrieve a rights overview for all encumbrances on the specified property. |
|
Provides access to the entire scanned deed for a property. |
|
Used to retrieve a rights overview for all easements on the specified property. |
|
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. |
|
Used to retrieve basic information for a property. |
|
Returns basic information as well as a rights overview for titles, easements, and encumbrances on the requested property. |
|
Ordering a signed paper printout with land registry information for a property. |
|
Search for powers of attorney. |
|
Search for powers of attorney. |
|
Search for powers of attorney. |
|
Search for powers of attorney. |
|
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. |
|
Used to retrieve a rights overview for all rights on the specified movable. |
|
Used to retrieve rights information for a document registered in the e-Act. |
|
Used to retrieve the historical view for a rights document from the revision trail. |
|
Used by city and bailiff courts to retrieve an overview of wills and financial conditions. |
|
Used by probate court to retrieve an overview of wills and marriage contracts. |
|
Ordering a signed paper printout with land registry information for a property, vehicle, share, or movable. |
|
Search by CVR number. |
Anmeldelse Svar
| Operation | Description |
|---|---|
Fetch the latest response. |
Application Services
AndelsbogAnmeld
| Operation | Description |
|---|---|
This operation allows an actor to submit a notification that may include a partial or complete cancellation of a duty mortgage deed. This operation can be used for case type 244. |
|
This operation allows an actor to submit a notification that establishes an attachment in real estate. This operation can be used for case type 37. |
|
Digitization of a mortgage deed. Used for case type 234. |
|
This operation allows an actor to submit a notification that may include an endorsement of a document with adjustment of duty. Used for case types 119, 187, and 209. |
|
This operation allows an actor to submit a notification that may include conversion of a document to a duty mortgage deed. Used for case type 251. |
|
This operation allows an actor to submit a notification that may include an endorsement of a document. Used for case types 10 and 149. |
|
This operation allows an actor to submit a notification that may include the cancellation of one or more documents. Used for case types 103 and 171. |
|
This operation allows an actor to submit a notification that may include the relaxation of several liabilities or servitudes. Used for case types 99 and 221. |
|
This operation allows an actor to submit a notification regarding an EjerpantebrevAndel to e-TL, and thus the notification can only include Ejerpantebrev case type 14. However, a sub-mortgage may be specified in the notification. |
|
This operation allows an actor to create a power of attorney in a share. Used for case type 222. |
|
This operation allows an actor to revoke a power of attorney in a share, specified by its identifier (UUID). Used for case type 224. |
|
Used to submit one or more endorsements of liabilities for a document for registration. This operation allows an actor to submit a notification with multiple endorsements concerning the same document. |
|
This operation allows an actor to submit a notification regarding the creation of a public law notice. Used for case type 124. |
|
This operation allows an actor to submit a notification that includes the endorsement of a public law notice. Used for case types 167, 176, and 180. |
|
This operation allows an actor to submit a notification regarding a PantebrevAndel to e-TL, and thus the notification can only include case type 10 for PantebrevAndel. |
|
This operation allows an actor to submit a notification regarding a Skadeløspantebrev to e-TL, and thus the notification can only include case type 28 for Skadeløspantebrev. |
|
This operation allows an actor to submit a notification for the creation of a levy in a property. Used for case type 34. |
|
This operation allows an actor to register a sub-mortgage in a share for registration. Used for case type 22. |
|
This operation allows an actor to submit a notification including the endorsement of a sub-mortgage on a share for registration. Used for case type 216. |
|
This operation allows an actor to specify a declaration of title for a cooperative housing unit. Used for case type 246. |
BilbogAnmeld
| Operation | Description |
|---|---|
This operation allows an actor to submit a notification that establishes an attachment on a vehicle. This operation can be used for case type 36. |
|
Digitization of a mortgage deed. Used for case type 233. |
|
This operation allows an actor to submit a notification that may include an endorsement of a document with adjustment of duty. Used for case types 119, 187, and 209. |
|
This operation allows an actor to submit a notification that may include an endorsement of a document. Used for case types 110 and 147. |
|
This operation allows an actor to submit a notification that may include the cancellation of one or more documents. Used for case types 101 and 169. |
|
This operation allows an actor to submit a notification that may include the relaxation of several liabilities or servitudes. Used for case types 97 and 217. |
|
This operation allows an actor to submit a notification regarding EjendomsforbeholdBilOpret to e-TL, and the notification can only include case type 12. |
|
This operation allows an actor to submit a notification regarding an EjerpantebrevBil to e-TL, and the notification can only include case type 12. A sub-mortgage may be specified in the notification. |
|
This operation allows an actor to create a power of attorney in a vehicle. Used for case type 218. |
|
This operation allows an actor to revoke a power of attorney in a vehicle, specified by its identifier (UUID). Used for case type 220. |
|
Used to submit one or more endorsements of liabilities for a document for registration. This operation allows an actor to submit a notification with multiple endorsements concerning the same document. |
|
This operation allows an actor to submit a notification regarding the creation of a public law notice. Used for case type 123. |
|
This operation allows an actor to submit a notification including the endorsement of a public law notice. Used for case types 165, 174, and 178. |
|
This operation allows an actor to submit a notification regarding a PantebrevBil to e-TL, and the notification can only include case type 8 for PantebrevBil. |
|
This operation allows an actor to submit a notification regarding a Skadeløspantebrev to e-TL, and the notification can only include case type 26 for Skadeløspantebrev. |
|
This operation allows an actor to submit a notification for the creation of a levy in a vehicle. Used for case type 33. |
|
This operation allows an actor to register a sub-mortgage in a vehicle for registration. Used for case type 20. |
|
This operation allows an actor to submit a notification including the endorsement of a sub-mortgage in a vehicle for registration. Used for case type 214. |
PersonbogAnmeld
| Operation | Description |
|---|---|
Digitization of a mortgage deed. Used for case type 235. |
|
This operation allows an actor to submit a notification that may include an endorsement of a document with adjustment of duty. Used for case types 119, 187, and 209. |
|
This operation allows an actor to submit a notification that may include an endorsement of a document. Used for case types 148 and 166. |
|
This operation allows an actor to submit a notification that may include the cancellation of one or more documents. Used for case types 102 and 170. |
|
This operation allows an actor to submit a notification that may include the relaxation of several liabilities or servitudes. Used for case types 98 and 225. |
|
This operation allows an actor to submit a notification regarding an EjerpantebrevLoesore to e-TL, and the notification can only include case type 13. A sub-mortgage may be specified in the notification. |
|
This operation allows an actor to submit a notification regarding an EjerpantebrevVirksomhedspantOpret to e-TL, and the notification can only include case type 243. A sub-mortgage may be specified in the notification. |
|
This operation allows an actor to create a power of attorney in personal property. Used for case type 226. |
|
This operation allows an actor to revoke a power of attorney in personal property, specified by its identifier (UUID). Used for case type 228. |
|
Used to submit one or more endorsements of liabilities for a document for registration. This operation allows an actor to submit a notification with multiple endorsements concerning the same document. |
|
This operation allows an actor to submit a notification regarding a hoestpantebrev to e-TL, and the notification can only include case type 31. |
|
This operation allows an actor to submit a notification including the endorsement of a public law notice. Used for case types 166, 175, and 179. |
|
This operation allows an actor to submit a notification regarding a PantebrevAndel to e-TL, and the notification can only include case type 9 for PantebrevAndel. |
|
This operation allows an actor to submit a notification regarding a pledge prohibition to e-TL, and the notification can only include case type 45. |
|
This operation allows an actor to submit a notification regarding a Skadeløspantebrev to e-TL, concerning personal property, pledge of receivables, and business mortgage. Used for case types 27, 29, and 30. |
|
This operation allows an actor to register a property regime for registration. Used for case types 144, 145, and 157. |
|
This operation allows an actor to submit a notification including the endorsement of a property regime for registration. Used for case type 192. |
|
This operation allows an actor to register a sub-mortgage in a share for registration. Used for case type 21. |
|
This operation allows an actor to submit a notification including the endorsement of a sub-mortgage in a share for registration. Used for case type 231. |
TingbogAnmeld
| Operation | Description |
|---|---|
The operation allows an actor to submit a request containing a combination of title endorsements. This operation can be used for processing types 51, 52, and 54. All endorsements must concern the same document. |
|
The operation allows an actor to submit a request containing a reduction or cancellation of a duty mortgage deed. This operation can be used for processing type 244. |
|
The operation allows an actor to submit a request that creates another encumbrance on real estate. This operation can be used for processing type 38. |
|
The operation allows an actor to submit a request to establish a seizure on real estate. This operation can be used for processing type 35. |
|
The operation allows an actor to submit a request to create a judge’s certificate. This operation can be used for processing type 184. |
|
Digitization of a mortgage deed. Used for processing type 232. |
|
The operation allows an actor to submit a request that may include an endorsement of a document with adjustment of duty. Used for processing types 119, 121, 187, and 209. |
|
The operation allows an actor to submit a request that may include the conversion of a document to a duty mortgage deed. Used for processing type 251. |
|
The operation allows an actor to submit a request to create a document of type "other" relating to real estate. Used for processing types 6, 115, 116, 150, 183, 199, and 203. |
|
The operation allows an actor to submit a request that may include an endorsement of a document. Used for processing types 10, 109, 120, 146, and 164. |
|
The operation allows an actor to submit a request that may include the cancellation of one or more documents. Used for processing types 55, 100, 108, and 168. |
|
The operation allows an actor to submit a request that may include the relaxation of several encumbrances or easements. Used for processing types 96 and 107. |
|
The operation allows an actor to submit a request for the creation of new real estate. Used for processing type 185. |
|
The operation allows an actor to submit a request regarding an EjerpantebrevFastEjendom to e-TL, and the request may thus only cover Ejerpantebrev processing type 11. |
|
The operation allows an actor to create a power of attorney regarding real estate. Used for processing type 204. |
|
The operation allows an actor to revoke a power of attorney regarding real estate, specified by its identifier (UUID). Used for processing type 206. |
|
Used to submit one or more encumbrance endorsements for a document for registration. This operation allows an actor to submit a request with multiple endorsements concerning the same document. |
|
The operation allows an actor to submit a request regarding an IndekspantebrevFastEjendom to e-TL, and the request may thus only cover an Indekspantebrev processing type 24. |
|
The operation allows an actor to submit a request with endorsement of a notice on a title document. Used for processing type 240. |
|
The operation allows an actor to submit a request to create a public law notice. Used for processing types 143 and 163. |
|
The operation allows an actor to submit a request with endorsement of a public law notice. Used for processing types 173, 177, and 210. |
|
The operation allows an actor to submit a request regarding a PantebrevFastEjendom to e-TL, and the request may thus only cover the PantebrevFastEjendom processing type 7. |
|
The operation allows an actor to submit a request regarding a Realkreditpantebrev, SDRO Mortgage Deed, or SDO Mortgage Deed to e-TL, and the request may thus only cover one of the processing types 23, 211, or 212. |
|
The operation allows an actor to submit a request for the creation of a servitude declaration. Used for processing type 182. |
|
Used to submit one or more servitude endorsements for a document for land registration. This operation allows an actor to submit a request with multiple endorsements concerning the same document. |
|
The operation allows an actor to submit a request for the creation of one or more servitudes. Used for processing types 42, 49, and 50. |
|
The operation allows an actor to submit a request for the creation of one or more servitudes with possible time limitation. Used for processing types 40, 41, 46, 47, and 48. |
|
The operation allows an actor to submit a request regarding a Skadesløs mortgage deed to e-TL, and the request may thus only cover processing type 25. |
|
The operation allows an actor to submit a request regarding a Skadesløs mortgage deed concerning property tax to e-TL, and the request may thus only cover processing type 253. |
|
The operation allows an actor to submit a request for the creation of a probate court certificate. Used for processing type 118. |
|
The operation allows an actor to submit a request for the creation of an auction deed. Used for processing type 117. |
|
The operation allows an actor to submit a request for the creation of a deed. Used for processing types 1, 3, 4, and 5. |
|
The operation allows an actor to submit a request for the creation of an attachment in real estate. Used for processing type 32. |
|
The operation allows an actor to submit a request for the creation of a sub-sheet. Used for processing type 181. |
|
The operation allows an actor to register a pledge in real estate for land registration. Used for processing type 19. |
|
The operation allows an actor to submit a request with endorsement of a pledge in real estate for land registration. Used for processing type 214. |