This page describes status codes, information and error messages for all etinglysing SOAP services.

Http status codes for etinglysing soap web service

HTTP Status code	Meaning

HTTP Status code	Meaning
200	Successful request and response. (200 OK) For the `generate<TYPE>` operations, may be accompanied by information messages that may be important. See Generate document or below for more information.
401	Authentication failed. (401 Unauthorized) Occurs if username/password is wrong/deactivated or the authentication token (bearer) is invalid or expired.
500	Soap fault response. (500 Internal Server Error) The response body contain a SOAP Fault message. The fault message includes a description of the the specific error condition. More information soap fault.

Successful request and response(200)

Successful request and response means that the operation was successful. For an explanation about the responses for the various operations in the api, see the description of the operation.

For the generate<TYPE> (Generate document) operations, note that even if the response is a successful one, it might contain information messages(INFOMELDING) that may be important later in the process.
If the information messages are not taken into account, it may affect the tinglysing operation.
See the errorGroup explanation for information about INFOMELDING.

Soap fault response(500)

Description of soap fault elements. See examples

Element	Description

Element	Description
faultcode	Values: `soap:Server` - conveys the fault is on the server side and there exists a detail element with more information `soap:Client` - The xml message is incorrectly formed or contains incorrect information. The `faultstring` is the only source of more information.
faultstring	Human readable error message. Note, if the soap fault response contain more that one `documentMessage`, the faultstring is a concatenation of the documentMessages.
detail	Contains detailed error information structured as documentMessages provided `faultcode` is `soap:Server`
FellesDokumentException	Exception wrapper
exceptionId	A timestamp that identifies the error message. Important for solving support cases.
documentMessages	A wrapper that contains at least one `documentMessage` with errorGroup other than INFOMELDING
documentMessage/detail	Detail message
documentMessage/errorGroup	errorGroup tells you what category of error messages this is and it should decide further action. Correct the request data or simply try again. See table for explanation
documentMessage/message	Short message
documentMessage/errorCode	Error code number, identifying the message

ErrorGroup explanation

ErrorGroup	Explanation	Action	Corresponding REST API status code

ErrorGroup	Explanation	Action	Corresponding REST API status code
INTERNFEIL	Internal error - There is a state in data, environment or configuration that we couldn't recover from.	Try again. Another server might handle this request. If the problem persists contact support	500 - INTERNAL SERVER ERROR
VALIDERINGSFEIL	Validation error - the request does not validate. These are business / professional / legal reasons why the request did not validate. Validation rules for this error involves verifying request data with grunnboken. In the last validation rule, we actually validates the complete document using Statens Kartverk validation service. Example	Verify and correct the data in the request.	400 - BAD REQUEST
EKSTERNFEIL	External error - This means that one of the external services we depend on to complete the request does not respond or is faulty.	Try again later. The external services we use are seldom faulty for a longer period.	500 - INTERNAL SERVER ERROR
UKJENT_FEIL	Unknown error - A flaw in the code or it may also be that the server which processed the request had a problem	Please try again, if the problem persists contact support	500 - INTERNAL SERVER ERROR
INPUTFEIL	Bad request - The xml message validates, but data in the message does not meet requirements. Not authorized, accessing data owned by others Property/cooperative share/document referred in the request does not exist in grunnboken. Example	Verify and correct the data in the request.	400 - BAD REQUEST
INFOMELDING	Information message - No error, just information. Both fault response and successful responses might have INFOMELDING. Example		200 - OK, unless there are other error categories in the same response.

Example soap fault messages

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
        <soap:Fault>
            <faultcode>soap:Client</faultcode>
            <faultstring>Unmarshalling Error: cvc-complex-type.2.4.a: Invalid content was found starting with element 'adocumentId'. One of '{documentId}' is expected. </faultstring>
        </soap:Fault>
    </soap:Body>
</soap:Envelope>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Server</faultcode>
         <faultstring>Det er avvik mellom innsendte opplysninger og det som står oppført i grunnboken. Det kan være feil hjemmelshaver, eiendom/borettsandel eller eiendomsnivå: Gjelder 10038239762 LUNDELAND MADS ANDRE</faultstring>
         <detail>
            <ns2:FellesDokumentException xmlns:ns2="http://dokument.ws7.etinglysing.no/">
               <exceptionId>1625215833724</exceptionId>
               <documentMessages>
                  <documentMessage>
                     <detail>Gjelder xxxxxxxxxxx LUNDELAND MADS ANDRE</detail>
                     <errorGroup>VALIDERINGSFEIL</errorGroup>
                     <message>Det er avvik mellom innsendte opplysninger og det som står oppført i grunnboken. Det kan være feil hjemmelshaver, eiendom/borettsandel eller eiendomsnivå</message>
                     <errorCode>9014</errorCode>
                  </documentMessage>
               </documentMessages>
            </ns2:FellesDokumentException>
         </detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Server</faultcode>
         <faultstring>Fant ikke dokument med id=123: null</faultstring>
         <detail>
            <ns2:FellesDokumentException xmlns:ns2="http://dokument.ws7.etinglysing.no/">
               <exceptionId>1625215328560</exceptionId>
               <documentMessages>
                  <documentMessage>
                     <errorGroup>INPUTFEIL</errorGroup>
                     <message>Fant ikke dokument med id=123</message>
                     <errorCode>9002</errorCode>
                  </documentMessage>
               </documentMessages>
            </ns2:FellesDokumentException>
         </detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>

Documentation

Codes and messages

Http status codes for etinglysing soap web service

Successful request and response(200)

Soap fault response(500)

ErrorGroup explanation

Example soap fault messages