The integrator initiates the process by sending a data structure (as described in the WSDL) to the web service. Etinglysing will return an object containing the document itself, a reference to the document in etinglysing and some key information about it.

...

^{Normal flow}

Example request:

Code Block

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
                  xmlns:dok="http://dokument.ws7.etinglysing.no/">
    <soapenv:Header/>
   <soapenv:Body>
      <dok:generatePantedokument>
         <pantedokument referanse="Example">
            <panteobjekter>
               <panteobjekt>
                  <matrikkel 
                    kommunenummer="1234" 
                    gaardsnummer="1" 
                    bruksnummer="1" 
                    festenummer="0" 
                    seksjonsnummer="0" 
                    eiendomsnivaa="G"/>
                  <hjemmelshavere>
                     <hjemmelshaver>
                       <organisasjon id="123456789">
                           <navn>Organization name</navn>
                           <!--Optional, not needed for production-->
                           <!--Will be validated towards Enhetsregisteret if present-->
                           <signaturberettigede> 
                              <signaturberettigede id="12345678901">
                                 <fornavn>First Name</fornavn>
                                 <etternavn>Surname</etternavn>
                                 <epost>person@example.com</epost>
                              </signaturberettigede>
                           </signaturberettigede>
                        </organisasjon>
                        <broek teller="1" nevner="1"/>
                     </hjemmelshaver>
                  </hjemmelshavere>
               </panteobjekt>
            </panteobjekter>
            <pantebeloeper>
               <pantebeloep valuta="NOK" verdi="100000"/>
            </pantebeloeper>
            <panthavere>
               <panthaverId>123456789</panthaverId>
            </panthavere>
            <dokumentflyt>DOKUMENT_TIL_TINGLYSING</dokumentflyt>
            <refinansiering>false</refinansiering>
         </pantedokument>
         <options>
            <returnPdf>false</returnPdf>
         </options>
      </dok:generatePantedokument>
   </soapenv:Body>
</soapenv:Envelope>

...

Code Block

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <ns2:generatePantedokumentResponse xmlns:ns2="http://dokument.ws7.etinglysing.no/">
         <return>
            <status>
               <created>2018-09-06T14:09:34.710+02:00</created>
               <id>15742141</id>
               <statusCode>OPPRETTET</statusCode>
            </status>
            <documentHolder>
               <content>PEJhbmtJRFhNT...</content>
               <format>BIDXML</format>
               <type>PANTEDOKUMENT</type>
            </documentHolder>
            <documentVersion>KARTVERKET</documentVersion>
         </return>
      </ns2:generatePantedokumentResponse>
   </soap:Body>
</soap:Envelope>

Drawio

zoom	1
simple	0	zoom	1
inComment	0
custContentId	1446281352
pageId	1202192544
lbox	1
diagramDisplayName	Diagram uten navn.drawio	lbox	1
contentVer	1
revision	1
baseUrl	https://ambita.atlassian.net/wiki
diagramName	Diagram uten navn.drawio
pCenter	0
width	501
links
tbstyle
height	331

^{Validation and error handling}

Example response:

Code Block

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Server</faultcode>
         <faultstring>Ugyldig personnr eller organisasjonsnr: 123456789</faultstring>
         <detail>
            <ns2:FellesDokumentException xmlns:ns2="http://dokument.ws7.etinglysing.no/">
               <exceptionId>1536235901863</exceptionId>
               <documentMessages>
                  <documentMessage>
                     <errorGroup>VALIDERINGSFEIL</errorGroup>
                     <message>Ugyldig personnr eller organisasjonsnr: 123456789</message>
                     <errorCode>9014</errorCode>
                  </documentMessage>
               </documentMessages>
            </ns2:FellesDokumentException>
         </detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>

...

When generating a mortgage you may have two scenarios:

Send the document to the Land Registry
Send the document to a broker

This you can control by setting the flow. The possible flows are:

...

Code Block
<panteobjekt> <borettsandel .../> <hjemmelshavere> ... </hjemmelshavere> <totalBroek teller="1" nevner="1"/> </panteobjekt>

How to handle additional signatures

For some cases it is not enough that the owners sign the document. This typically means that there are “rettighetshavere” that needs to be taken into account. If not taken into account the service will respond with validation errors on generate (and that could be valuable and correct). If the case is, however, that you intend to get these signatures, the signature role must be applied. This tells the service that “I’ve got it!”.

There are four types of roles:

...

Role

...

Description

...

BORTFESTER

...

The land owner that lease out land
(feste))

...

RETTIGHETSHAVER_I_URAADIGHET

...

A legal person is blocking registration
unless his consent is given (signature on the document)

...

UTSTEDER

...

The seller is not the land owner
(only relevant for deeds)

...

PANTSETTER

...

If totalBroek is specified for a pantedokument with dokumentflyt = DOKUMENT_TIL_TINGLYSING the hjemmmelshaver broek will be validated and superseded according to grunnboken. totalBroek must be equal to sum broek for hjemmelshavere.

If totalBroek is specified for a pantedokument with dokumentflyt = DOKUMENT_TIL_OPPGJOER or dokumentflyt = DOKUMENT_TIL_EKSISTERENDE_OPPGJOER, the hjemmelshaver broek will NOT be validated. Hjemmelshavere are the new owners and at the time of writing, it is not possible to validate.
If totalBroek is 1/1, the fractions for hjemmelshavere will be disregarded. Because there is no requirement for fraction in a pantedokument includes the entire property.
If totalBroek is less than 1/1, sum broek for hjemmelshavere must be equal to totalBroek, and hjemmelshaver broek must be correct according to the buyer contract.

How to handle additional signatures

For some cases it is not enough that the owners sign the document. This typically means that there are “rettighetshavere” that needs to be taken into account. If not taken into account the service will respond with validation errors on generate (and that could be valuable and correct). If the case is, however, that you intend to get these signatures, the signature role must be applied. This tells the service that “I’ve got it!”.

There are four types of roles:

Role	Description
BORTFESTER	The land owner that lease out land (feste)). Only relevant for deeds.
RETTIGHETSHAVER_I_URAADIGHET	A legal person is blocking registration unless his consent is given (signature on the document)
UTSTEDER	The seller is not the land owner (only relevant for deeds)
PANTSETTER	The legal person if not equal to the land owner (hjemmelshaver)

In V7 this is put outside the property, hence yields the whole document (across all properties)

...

This feature enables the integrator to generate documents on behalf of another organization. Once added into the request, the document will be generated accordingly unless the validation fails to validate that the respective organisation is defined as rekvirent or panthaver (dokumenteier) in the user profile.

...

Figure 5 Example rekvirent & panthaverinto the request, the document will be generated accordingly unless the validation fails to validate that the respective organisation is defined as rekvirent or panthaver (dokumenteier) in the user profile.

...

Figure 5 Example rekvirent & panthaver

Using Ambita’s signing service

Ambita has a signing service named Esignering. Almost all bank customers have their own signing service they use for signing documents. However, a new feature in Etinglysing allows bank customers to use Ambita’s signing service for signing Pantedokument.

Using the options element sendToCustomerSigning will send the generated document to the specified parties for signing with their BankID (they will receive an email with link to www.esignering.no for signing the document).

Code Block
<options> ... <sendToCustomerSigning>true</sendToCustomerSigning> </options>

Handle signer’s notification in your own system

From version 51.67 (February 2024) it is possible for integrated clients to handle all signing notification and dialogue in their own system. This may require additional configuration of your account in Etinglysing. Contact customer support if you are interested in using this feature

It is now possible to suppress the email notification that is sent from Esignering to all parties that is expected to sign the document. By also setting the option returnCustomerSigningLinks to true the response from generatePantedokument will include an additional signing information object.

Request

Code Block
<options> ... <sendToCustomerSigning>true</sendToCustomerSigning> <returnCustomerSigningLinks>true</returnCustomerSigningLinks> </options>

Response

Code Block

<signingInformation>
  <signingLinks>
    <signingLink id="01010122222" signed="false">https://beta.esignering.no/kunde/login/055c018e-79h6-4c75-938g-ac78c1e53832</signingLink>
    <signingLink id="02020233333" signed="false">https://beta.esignering.no/kunde/login/d6s01844-6e63-488c-d396-4617626eff61</signingLink>
  </signingLinks>
</signingInformation>

The id attribute is the social security number (fødselsnummer), signed is the current signing status for that person and the element text is the link for that person to use for signing the document. Integrated clients can now present the link in their own system or be responsible for sharing the links to the parties in their preferred way.

Check signing status

For documentation about how to check the signing status, see Get status signing

Version	Old Version 5	New Version Current
Changes made by	Bjørn Ove Ingvaldsen	Bjørn Hamre
Saved on	Sept 15, 2020	Feb 12, 2024

Versions Compared

Key

^{Validation and error handling}

How to handle additional signatures

How to handle additional signatures

Using Ambita’s signing service

Handle signer’s notification in your own system

Request

Response

Check signing status

Page Comparison

Versions Compared

Key

Validation and error handling

How to handle additional signatures

How to handle additional signatures

Using Ambita’s signing service

Handle signer’s notification in your own system

Request

Response

Check signing status

^{Validation and error handling}