The aim is to make using our API as transparent as possible whether it is an Ambita broker or not. When the message containing tinglysing information for the pantedokument is available, the only difference will be the content of the sendToRealestateBroker sendToRealEstateBroker response which will contain MOTTATT_AV_MEGLER.

To make the handling uniform whether it is an Ambita broker or not, the preferred handling is polling for events or status will work in both cases.

...

Send pantedokument to an existing settlement for an Ambita broker

If it is an Ambita broker and the settlement exists, the response is immediate and will contain the status MOTTATT_AV_MEGLER:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
	<soap:Body>
		<ns2:sendToRealEstateBrokerResponse xmlns:ns2="http://dokument.ws7.etinglysing.no/">
			<return>
				<status>
					<created>2021-01-07T14:50:45.667+01:00</created>
					<documentStatusTinglysing/>
					<id>123321123</id>
					<statusCode>MOTTATT_AV_MEGLER</statusCode>
					<description>Pant - 4444/66/66// [G]</description>
					<reference>Customer reference</reference>
				</status>
				<type>PANTEDOKUMENT</type>
				<documentVersion>KARTVERKET</documentVersion>
			</return>
		</ns2:sendToRealEstateBrokerResponse>
	</soap:Body>
</soap:Envelope>

Pantedokument sendt to an existing settlement for an Ambita broker will get TINGLYST or TINGLYSING_FEILET. (given that the broker tinglyser pantedokumentet) Se this state diagram for more details.

Alternate flows

No alternate flows for “Send pantedokument to an Ambita broker and the settlement exists”

Send pantedokument to an external broker

If a pantedokument is sent to a broker (sendToRealEstateBroker) and a settlement does not exist/is not an Ambita broker, the following steps is executed:

• Can the real estate broker given, received pantedokument. Determined by a lookup in Akeldo.

• The pantedokument is uploaded to AFPant(Altinn) for the broker to download.

• The pantedokument copy in etinglysing is changed from PART_SIGNER to SENDT_TIL_MEGLER

• The response will contain SENDT_TO_MEGLER:
  

  Code Block
  language xml
  <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:sendToRealEstateBrokerResponse xmlns:ns2="http://dokument.ws7.etinglysing.no/"> <return> <status> <created>2021-01-07T14:50:45.667+01:00</created> <documentStatusTinglysing/> <id>123321123</id> <statusCode>MOTTATT_AV_MEGLER</statusCode> <description>Pant - 4444/66/66// [G]</description> <reference>Customer reference</reference> </status> <type>PANTEDOKUMENT</type> <documentVersion>KARTVERKET</documentVersion> </return> </ns2:sendToRealEstateBrokerResponse> </soap:Body> </soap:Envelope>

The final MOTTATT_AV_MEGLER state must be obtained by polling for event(hendelser) or status(getStatus)

Alternate flows

The following alternate flow might happen

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Server</faultcode>
         <faultstring>Megler med org.nr. 999999999 kan ikke motta pantedokumentet elektronisk. Opprett pantedokumentet på papir.: null</faultstring>
         <detail>
            <ns2:FellesDokumentException xmlns:ns2="http://dokument.ws7.etinglysing.no/">
               <exceptionId>1610453917418</exceptionId>
               <documentMessages>
                  <documentMessage>
                     <errorGroup>VALIDERINGSFEIL</errorGroup>
                     <message>Megler med org.nr. 999999999 kan ikke motta pantedokumentet elektronisk. Opprett pantedokumentet på papir.</message>
                     <errorCode>9050</errorCode>
                  </documentMessage>
               </documentMessages>
            </ns2:FellesDokumentException>
         </detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>