This article is also available in:

How does the Mareon integration work?

Mareon is Aareon's platform with which housing corporations exchange maintenance orders with their maintenance partners. Robaws connects to it via the DICO integration: you create a DICO endpoint in Robaws, Mareon sends its messages there, and Robaws converts them into an order. In the other direction, Robaws sends status changes of that order back to Mareon.


The DICO standard is a Dutch agreement. This integration can therefore only be used by customers in the Netherlands.


You find the configuration via settings > integrations > DICO, in the Dico Endpoints overview.


Receiving maintenance orders from Mareon


To receive maintenance orders from Mareon, you create an endpoint in Robaws that Mareon can call.


  1. In the Dico Endpoints overview, click the action button +.
  2. Switch Enabled on and give the endpoint a clear name.
  3. At Incoming/Outgoing, choose the Incoming option.
  4. At Type, choose the Generic SOAP option. For incoming messages, only SOAP messages are currently supported.
  5. Generate the credentials you pass on to Mareon: click the pencil next to Credentials and then click Generate new credentials. They are saved automatically.
  6. Choose a Contracting party. As soon as a maintenance order comes in from Mareon, that contracting party is linked to the order as the customer automatically.
  7. Select the order template with which the order is built up, and fill in the company and the corresponding journals.


An incoming DICO endpoint of the Generic SOAP type


Copy the credentials before you close the window. You cannot request them again afterwards. You can always generate new credentials, but then you have to pass those on to Mareon again.


Generating credentials on the DICO endpoint


On an incoming endpoint, the Message service base URL field is filled in automatically with https://dico.robaws.com/services/MessageService31 and cannot be changed. That is the address to which Mareon sends its messages.


Mareon sends its messages to that URL with Basic Authentication. On the basis of the credentials, Robaws knows which environment the message is intended for. You find a processed message back as an order in the orders module.


Which information from the message ends up in which field of the order is determined by replacement codes and extra fields on the order template. This is described in full in the article about the DICO integration.


Sending status updates back to Mareon


Once you have received an order from Mareon, Robaws can report status changes of that order back.


On the same incoming endpoint, fill in the URL for status feedback field. That URL looks like this:


  • test environment: https://marx.mareon-test.nl/?API=MLD_OPDR_SALES005_1.0_MS31&APIKEY=<API_KEY>
  • production environment: https://marx.mareon.nl/?API=MLD_OPDR_SALES005_1.0_MS31&APIKEY=<API_KEY>


The <API_KEY> is unique per customer. You request it from Mareon, together with confirmation of the correct URL. If a login belongs with it, fill that in at Credentials for status feedback.


URL for status feedback on the endpoint


After that, you translate the statuses of your orders in Robaws into a DICO code. You do this via the DICO order status mapping function in the Dico Endpoints overview.


The DICO order status mapping function


To send status updates, you only use the right-hand column Order status > Outgoing DICO code. For each order status in Robaws, you fill in the DICO code there that has to go along with the outgoing message.


The right-hand column: order status to outgoing DICO code


If an order changes to a status for which no outgoing DICO code is set, no status message is sent to Mareon.


Available DICO codes


Code

Description

ACC

Accept

AFH

Tenant appointment

AFR

Awaiting inspector's response

AFW

Awaiting due to weather conditions

ANN

Order cancelled

BBT

Tenant calls back

BNT

Tenant not home

GER

Completion notification

MIB

Material on order

TFC

To be invoiced

UIT

In progress

VBW

Tenant request

VER

Extension

WEI

Decline


Receiving status updates from Mareon


Mareon can also send status updates to Robaws. For that you translate the opposite direction: from DICO code to order status. Use the left-hand column Incoming DICO code > Order status in the same DICO order status mapping function for this.


The left-hand column: incoming DICO code to order status


If a status message comes in with a DICO code for which no order status is set, the status of the order in Robaws remains unchanged.


Need help?


Is it about the endpoint, the mapping or the order template in Robaws? Contact support@robaws.com.


Is it about your API key, the feedback URL or the messages Mareon sends? Then contact Mareon support via aareon.nl/mareon.

Updated on: 09/09/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!