To provide a versioned and described data format for exchanging data with external entities. Since Avro is used at FINN for data exchange, it seems as a good fit for describing our externally delivered data.

• Schema: src/main/avro/billan.avsc
• Example: src/test/resources/billan-example.json

• Schema: src/main/avro/boliglan.avsc
• Example: src/test/resources/boliglan-example.json

• Schema: src/main/avro/utleieforsikring.avsc
• Example: src/test/resources/utleieforsikring-example.json

• Schema: src/main/avro/forsikringspakke.avsc
• Example: src/test/resources/forsikringspakke-example.json

For the API integration a multipart POST is issued to the configured endpoint, on the format:

POST /some-url
Content-Type: multipart/form-data; boundary=------------------------d74496d66958873e
--------------------------d74496d66958873e
Content-Disposition: form-data; name="body.json"
Content-Type: application/json

{.. json content ..}
--------------------------d74496d66958873e
Content-Disposition: form-data; name="files"; filename="attachment-name.pdf"
Content-Transfer-Encoding: binary

.. data ..
--------------------------d74496d66958873e--

If request is successfully consumed, respond with 200 OK.

• Bindings: Avro provides bindings for multiple languages. We could therefore aim to provide an integration library for the commonly most used languages at our providers.