Skip to main content
Version: 4.5

Services

The Harmoney API-gateway OpenAPI specification contains all the available Harmoney services.

Below, you can find additional information and examples about the services that are provided.

Dossier services​

PUT Dossier​

This API-gateway service call creates or updates a dossier for a front-office. A back-office can also initiate a dossier for a front-office. Both offices exist in MyHarmoney and have fixed unique identifiers.
The dossier will only be created/updated if the user is authorized to do so for the provided front office.

Additional information:

  • When mandatory fields are not provided, the request will not be valid.
  • When parties are created, they must have one and only one type-specific property (e.g., individual, company, …)
  • When the dossier identifier is not known in the system, the dossier will be created.
  • When the dossier identifier is known in the system, the dossier will be updated and the previous state is overwritten.
  • When the party is already known in the system (based on the identifier), the provided party data will be updated.

HTTP Request​

MethodPUT
URL../financial-sps/{front-office-identifier}/dossiers/{dossier-identifier}
URL (for back-office)../back-offices/{back-office-identifier}/dossiers/{dossier-identifier}

Request Body examples​

  • Individual - Type KYC - via Back Office
{
"frontOffice": {
"identifier": "front-office-identifier"
},
"dossier": {
"externalIdentifier": "identifier",
"number": "uniqueNumber",
"name": "dossier name",
"type": "KNOW_YOUR_CUSTOMER",
"service": "KNOW_YOUR_CUSTOMER",
"client": {
"externalIdentifier": "person_00001"
},
"externalInfo": {
"source": "CRM",
"metadata": {}
}
},
"associatedParties": [
{
"externalIdentifier": "person_00001",
"individual": {
"firstName": "john",
"lastName": "doe",
"dateOfBirth": "1999-12-31"
},
"externalInfo": {
"metadata": {
"METADATA_RISK": "High",
"METADATA_RELATION": "Medium"
}
}
}
]
}
  • Individual - Type Insurance - via Front Office
{
"dossier": {
"externalIdentifier": "identifier",
"number": "uniqueNumber",
"name": "dossier name",
"type": "INSURANCE",
"service": "SAVINGS_INVESTMENT_INSURANCE",
"client": {
"externalIdentifier": "person_00001"
},
"insurance": {
"paymentPeriodicity": "ONE_TIME",
"premium": "1000.00",
"balance": "1000.00",
"balanceDate": "2020-07-16",
"iban": "BE12999293718292",
"insurees": [
{
"externalIdentifier": "person_00001"
}
]
}
},
"associatedParties": [
{
"externalIdentifier": "person_00001",
"individual": {
"firstName": "john",
"lastName": "doe",
"dateOfBirth": "1999-12-31",
"placeOfBirth": "Gent",
"nationality": "BE",
"additionalNationalities": [
"NL",
"FR"
],
"gender": "MALE",
"mobilePhone": "+32456123789",
"email": "[email protected]",
"maritalStatus": "SINGLE",
"maritalStatusSince": "1999-12-31",
"language": "NL",
"occupation": "Homeless",
"socialState": "WORKER",
"education": "COLLEGE",
"industrySector": "CHARITY",
"dependentChildren": "2",
"partnerName": "Jane ",
"iban": "BE16557449113474",
"nationalRegistrationNumber": "99123100077",
"identityCardNumber": "555999999944",
"identityCardValidTo": "2050-12-31",
"address": {
"fullStreet": "Central Park 9/A",
"postalCode": "1234",
"city": "Some Town",
"country": "BE"
},
"identityDocuments": [
{
"name": "scan id card",
"type": "FRONT_BACK_SCAN",
"file": {
"filename": "scan_id_card.pdf",
"mimeType": "application/pdf",
"content": "iVBORw0KGgoAAAJggg=="
}
}
]
}
}
]
}
  • Company - Type Investment - via Front Office
{
"dossier": {
"externalIdentifier": "identifier",
"number": "uniqueNumber",
"name": "dossier name",
"type": "INVESTMENT",
"service": "DISCRETIONARY",
"client": {
"externalIdentifier": "company_00001"
},
"investment": {
"accounts": [
{
"externalAccountNumber": "Account number 1",
"assetName": "Account name 1",
"assetValue": "15000.00",
"assetValueDate": "2019-01-01"
}
]
}
},
"associatedParties": [
{
"externalIdentifier": "company_00001",
"company": {
"name": "Gemaflor",
"companyNumber": "0433357396",
"address": {
"country": "BE"
},
"owners": [
{
"externalIdentifier": "person_00001",
"percentage": "100",
"uboType": "OWNERSHIP"
}
]
}
},
{
"externalIdentifier": "person_00001",
"individual": {
"firstName": "john",
"lastName": "doe",
"dateOfBirth": "1999-12-31"
}
}
]
}
  • Indivision - Type KYC
{
"dossier": {
"externalIdentifier": "identifier",
"number": "uniqueNumber",
"name": "dossier name",
"type": "KNOW_YOUR_CUSTOMER",
"service": "KNOW_YOUR_CUSTOMER",
"client": {
"externalIdentifier": "indivision_00001"
}
},
"associatedParties": [
{
"externalIdentifier": "indivision_00001",
"indivision": {
"name": "indivision name",
"members": [
{
"externalIdentifier": "person_00001",
"percentage": "50"
},
{
"externalIdentifier": "person_00002",
"percentage": "50"
}
]
}
},
{
"externalIdentifier": "person_00001",
"individual": {
"firstName": "john",
"lastName": "doe",
"dateOfBirth": "1999-12-31"
}
},
{
"externalIdentifier": "person_00002",
"individual": {
"firstName": "jane",
"lastName": "doe",
"dateOfBirth": "1999-11-30"
}
}
]
}
  • Example with related dossiers & parties and tax information on a party
{
"dossier": {
"externalIdentifier": "identifier",
"number": "uniqueNumber",
"name": "dossier name",
"type": "KNOW_YOUR_CUSTOMER",
"service": "KNOW_YOUR_CUSTOMER",
"client": {
"externalIdentifier": "person_00001"
},
"relatedParties": [
{
"identifier": {
"externalIdentifier": "person_00002"
},
"relationType": "OTHER"
}
],
"relatedDossiers": [
{
"externalIdentifier": "dossier_x_1"
}
]
},
"associatedParties": [
{
"externalIdentifier": "person_00001",
"individual": {
"firstName": "john",
"lastName": "doe",
"dateOfBirth": "1999-12-31",
"address": {
"fullStreet": "Korenmarkt",
"postalCode": "9000",
"city": "Gent",
"country": "BE"
}
},
"relatedParties": [
{
"identifier": {
"externalIdentifier": "person_00002"
},
"relationType": "OTHER"
}
],
"taxInformations": [
{
"tin": "12345678901",
"isPrimary": true,
"useResidentialAddress": true
},
{
"tin": "12345678999",
"isPrimary": false,
"useResidentialAddress": false,
"address": {
"fullStreet": "Groenplaats",
"postalCode": "2000",
"city": "Antwerp",
"country": "BE"
}
}
]
},
{
"externalIdentifier": "person_00002",
"individual": {
"firstName": "jane",
"lastName": "doe",
"dateOfBirth": "1999-11-30"
}
}
]
}
  • Example with an intermediary on the dossier
{
"dossier": {
"externalIdentifier": "identifier",
"number": "uniqueNumber",
"name": "dossier name",
"type": "KNOW_YOUR_CUSTOMER",
"service": "KNOW_YOUR_CUSTOMER",
"client": {
"externalIdentifier": "indivision_00001"
},
"intermediary": {
"identifier": "frontoffice_reference"
}
},
"associatedParties": [
{
"externalIdentifier": "indivision_00001",
"indivision": {
"name": "indivision name",
"members": [
{
"externalIdentifier": "person_00001",
"percentage": "50"
}
]
}
},
{
"externalIdentifier": "person_00001",
"individual": {
"firstName": "john",
"lastName": "doe",
"dateOfBirth": "1999-12-31"
}
}
]
}

POST Flow​

This API-gateway service call performs the necessary actions to initiate the flow for a specific responsible on a dossier, by identifying the Dossier and Responsible within the context of a front-office. Depending on the configuration, one or several flow-options are possible. For each responsible on the dossier, the flow call must be executed separately to complete the Dossier, so the Dossier can be submitted to the front office.

Additional information:

  • The configured flow-options need to be communicated by Harmoney.
  • The front-office linked to the dossier must have the Investor flow module enabled.

Flow-options:

Flow optionDescription
GENERATE_CODEA CODE is created that should be used by the Responsible to start the correct Flow for a specific Dossier in Harmoney, using the dedicated landing-page on Harmoney indicated by the URL field.
GENERATE_URLAn absolute URL is created that should be used by the Responsible to directly start the correct Flow for a specific Dossier in Harmoney.
DIRECT_INVESTOR_MAILSend a mail inviting the responsible to complete the flow. The responsible will start directly with the flow. The responsible is required to have a valid e-mail.
INVESTOR_MAILSend a mail inviting the responsible to complete the flow. The responsible will have to login or register before they can start with the flow.The responsible is required to have a valid e-mail.

Response examples​

  • flowOption: GENERATE_CODE
{
"url": "https://<whitelabel>.myharmoney.eu/shorturl/",
"code": "AZERTY"
}
  • flowOption: GENERATE_URL
{
"url": "https://<whitelabel>.myharmoney.eu/token?token=<tokenId>&idLang=<langId>"
}
  • flowOption: DIRECT_INVESTOR_MAIL
{}

GET Dossier​

Use this API-gateway service call to retrieve a dossier from a front-office or a back-office. Based on the provided query params, more or less data will be added to the response. There are 2 options, either provide the expanded param that is true (everything is included) or false (minimal data is provided). To have a more controlled way to determine which data should be included, the includes param can be used. An overview of the includes options is available in the Gateway OpenAPI docs. Combining the query parameters is not possible.

HTTP Request​

MethodGET
URL../financial-sps/{front-office-identifier}/dossiers/{dossier-identifier}
URL (for back-office)../back-offices/{back-office-identifier}/dossiers/{dossier-identifier}

Request body examples​

  • ../financial-sps/front-office-identifier/dossiers/dossierExternalIdentifier?expanded=false
{
"frontOffice": {
"identifier": "front-office-identifier"
},
"dossier": {
"externalIdentifier": "dossierExternalIdentifier",
"internalIdentifier": "HhpTts9Qj/0gyhy+SnDLXQ==",
"number": "uniqueNumber",
"name": "name",
"type": "KNOW_YOUR_CUSTOMER",
"service": "KNOW_YOUR_CUSTOMER",
"client": {
"externalIdentifier": "company_00001"
}
},
"associatedParties": []
}
  • ../financial-sps/front-office-identifier/dossiers/dossierExternalIdentifier?expanded=true
{
"frontOffice": {
"identifier": "front-office-identifier"
},
"dossier": {
"externalIdentifier": "identifier",
"internalIdentifier": "HhpTts9Qj/0gyhy+SnDLXQ==",
"client": {
"externalIdentifier": "person_00001"
},
"number": "uniqueNumber",
"name": "name",
"type": "KNOW_YOUR_CUSTOMER",
"service": "KNOW_YOUR_CUSTOMER",
"commercialProduct": {
"externalReference": "commercial_product_ref"
},
"status": "APPROVED",
"rba": {
"rating": "HIGH",
"timeUpdated": "2018-12-12T15:16:46Z",
"score": "70",
"escalation": "false",
"productFactor": "1",
"systemAssessment": "NOK",
"details": [
{
"parameter": "PEP",
"result": "YES",
"score": "70"
}
]
},
"metadata": {},
"documents": [
{
"name": "doc name",
"type": "DOC_TYPE",
"filename": "file-name.pdf",
"contentURL": "https://cdn.myharmoney.eu/…",
"timeUpdated": "2020-10-02T15:18:44Z"
}
],
"externalInfo": {
"source": "CRM",
"metadata": {}
}
},
"associatedParties": [
{
"externalIdentifier": "person_00001",
"internalIdentifier": "HhpTts9Qj/0gyhy+SnDLXQ==",
"individual": {
"firstName": "john",
"lastName": "doe",
"nationality": "BE",
"nationalRegistrationNumber": "99123100077",
"mobilePhone": "+32456123789",
"gender": "MALE",
"email": "[email protected]",
"dateOfBirth": "1999-12-31",
"language": "NL",
"maritalStatus": "SINGLE",
"address": {
"fullStreet": "Central Park 9/A",
"postalCode": "1234",
"city": "OldTown",
"country": "BE"
},
"identityDocuments": []
},
"metadata": {},
"externalInfo": {
"metadata": {
"METADATA_RISK": "High",
"METADATA_RELATION": "Medium"
}
}
}
]
}
  • ../financial-sps/front-office-identifier/dossiers/dossierExternalIdentifier?includes=["CLIENT"]
{
"frontOffice": {
"identifier": "front-office-identifier"
},
"dossier": {
"externalIdentifier": "dossierExternalIdentifier",
"internalIdentifier": "HhpTts9Qj/0gyhy+SnDLXQ==",
"number": "uniqueNumber",
"name": "name",
"type": "KNOW_YOUR_CUSTOMER",
"service": "KNOW_YOUR_CUSTOMER",
"status": "APPROVED",
"lifecycle": "ONBOARDING",
"client": {
"externalIdentifier": "company_00001"
},
"metadata": {}
},
"associatedParties": [
{
"externalIdentifier": "company_00001",
"internalIdentifier": "HhpTts9Qj/0gyhy+SnDLXQ=="
}
]
}

GET Risk Analysis​

This service can be used to retrieve the RBA (Risk Based Approach) results for an existing dossier (if available).
The front-office/back-office must have the RBA module enabled.

Response examples​

{
"rating": "HIGH",
"timeUpdated": "2018-12-12T15:16:46Z",
"score": 70,
"escalation": "false",
"productFactor": 1,
"details": [
{
"parameter": "AML_MATCH",
"result": "YES",
"score": "70"
}
]
}

GET Dossier Questionnaire Answers​

This service can be used to retrieve the answers of questionnaires of a dossier.
Dossier questionnaires are only applicable when the Dossier Questionnaires module is active and when there are questionnaires configured for the dossier definition. The dossier questionnaires should not be confused with the questionnaires used in a flow (see flow-related endpoints for this).

For each questionnaire, only the questions are returned for which an answer has been provided.

Response examples​

[
{
"questionnaireIdentifier": "customer_advisor_form_01",
"answers": [
{
"questionIdentifier": "Q_HAS_PETS",
"answer": true
},
{
"questionIdentifier": "Q_PET_NAMES",
"answer": "Woofy"
},
{
"questionIdentifier": "Q_PET_FEATURES",
"answer": [
"1",
"3"
]
}
]
},
{
"questionnaireIdentifier": "customer_advisor_form_02",
"answers": []
}
]

GET Dossier Answers​

This service can be used to retrieve all the answers applicable for the dossier.
These can be questions that are asked via dossier questionnaires, but also questions who are asked on an information exchange flow (also known as the investor flow)

Response examples​

[
{
"questionIdentifier": "Q_HAS_PETS",
"answer": true
},
{
"questionIdentifier": "Q_PET_NAMES",
"answer": "Woofy"
},
{
"questionIdentifier": "Q_PET_FEATURES",
"answer": [
"1",
"3"
]
}
]

Put Dossier Answers​

This service can be used to update answers applicable for the dossier.
It’s advised to use the update strategy APPEND to avoid losing answers of questions who are not defined in the body of the message (see more details in the OpenApi spec).
The formatting of the answer depends on the answer type of the question.

Request body examples​

[
{
"questionIdentifier": "Q_HAS_PETS",
"answer": true
},
{
"questionIdentifier": "Q_PET_NAMES",
"answer": "Woofy"
},
{
"questionIdentifier": "Q_PET_AGE",
"answer": 13
},
{
"questionIdentifier": "Q_PET_FEATURES",
"answer": [
"1",
"3"
]
}
]

GET Flow completion results​

This service can be used to retrieve the results of the flow completion performed by the responsible person(s) of the dossier.
Retrieving the flow completion results using a front-office requires the Investor flow module to be enabled on that front-office.
Retrieving the flow completion results using a back-office requires the Investor results module to be enabled on that back-office.

Response examples​

[
{
"status": "COMPLETED",
"timeCompleted": "2020-01-01 22:22:22Z0",
"flowDocuments": [
{
"partyIdentifier": {
"externalIdentifier": "person_00001"
},
"documents": [
{
"type": "INVESTOR_FLOW",
"url": "https://cdn.myharmoney.eu/…"
}
]
}
],
"profiles": [
{
"partyIdentifier": null,
"type": "INVESTMENT",
"profile": "DYNAMIC",
"score": 80
}
]
}
]

POST Flow completion results​

This service can be used to create a flow completion result for a dossier. Creating a flow completion result requires the Investor flow module to be enabled on the front-office.
The creation of a flow completion result is only possible for dossiers that don’t already have existing flow completion results and is limited to one profile for each profile type.
Created flow completion results through this endpoint will always have the status EXTERNAL.

Request body examples​

{
"timeCompleted": "2024-01-24",
"profiles": [
{
"type": "INVESTMENT",
"profile": "DEFENSIVE"
}
]
}

GET Flow completion questionnaire answers​

This service can be used to retrieve all the answers of a flow completion performed by the responsible person(s) of the dossier.
Retrieving the flow completion results using a front-office requires the Investor flow module to be enabled on that front-office.
Retrieving the flow completion results using a back-office requires the Investor results module to be enabled on that back-office.

For each questionnaire, only the questions are returned for which an answer has been provided.

Response examples​

[
{
"questionIdentifier": "Is_PEP",
"answer": "1",
"createdFor": {
"externalIdentifier": "597076"
}
},
{
"questionIdentifier": "Is_PEP_since",
"answer": "2020-01-01",
"createdFor": {
"externalIdentifier": "597076"
}
},
{
"questionIdentifier": "Is_PEP_still_active",
"answer": "true",
"createdFor": {
"externalIdentifier": "597076"
}
}
]

Party services​

GET Party​

Use this API-gateway service call to retrieve a party from a front-office. Based on the provided query params, more or less data will be added to the response. There are 2 options, either provide the expanded param that is true (everything is included) or false (minimal data is provided). To have a more controlled way to determine which data should be included, the includes param can be used. An overview of the includes options is available in the Gateway OpenAPI docs. Combining the query parameters is not possible.

HTTP Request​

MethodGET
URL../financial-sps/{front-office-identifier}/parties/{party-identifier}

Response examples​

  • ../financial-sps/{front-office-identifier}/parties/{party-identifier}?expanded=false
{
"party": {
"externalIdentifier": "partyIdentifier",
"internalIdentifier": "ePO4/F3aaxzFkTb+owGpBQ=="
}
}
  • ../financial-sps/{front-office-identifier}/parties/{party-identifier}?expanded=true
{
"party": {
"externalIdentifier": "partyIdentifier",
"internalIdentifier": "ePO4/F3aaxzFkTb+owGpBQ==",
"individual": {
"firstName": "john",
"lastName": "doe",
"address": {
"fullStreet": "Central Park 9/A",
"postalCode": "1234",
"city": "Gent",
"country": "BE"
}
},
"relatedParties": [
{
"identifier": {
"externalIdentifier": "relatedPartyIdentifier",
"internalIdentifier": "MBfdr31Odc+sgT/lZ08ebQ=="
},
"relationType": "CHILD"
}
],
"taxInformations": [
{
"tin": "12345678901",
"isPrimary": true,
"useResidentialAddress": true
},
{
"tin": "12345678999",
"isPrimary": false,
"useResidentialAddress": false,
"address": {
"fullStreet": "Groenplaats",
"postalCode": "2000",
"city": "Antwerp",
"country": "BE"
}
}
],
"metadata": {
"KEY": "value"
},
"externalInfo": {
"metadata": {
"METADATA_RISK": "High",
"METADATA_RELATION": "Medium"
}
}
},
"associatedParties": [
{
"externalIdentifier": "relatedPartyIdentifier",
"internalIdentifier": "MBfdr31Odc+sgT/lZ08ebQ==",
"individual": {
"firstName": "related",
"lastName": "to john doe",
"address": {
"fullStreet": "Avenue 15",
"postalCode": "2000",
"city": "Antwerp",
"country": "BE"
}
},
"metadata": {}
}
]
}
  • ../financial-sps/{front-office-identifier}/parties/{party-identifier}?includes=[β€œPARTY_INFO”]
{
"party": {
"externalIdentifier": "partyIdentifier",
"internalIdentifier": "ePO4/F3aaxzFkTb+owGpBQ==",
"company": {
"name": "ExampleCompany",
"companyNumber": "0000000000",
"address": {
"fullStreet": null,
"postalCode": null,
"city": null,
"country": null
}
},
"metadata": {},
"postalAddress": {
"fullStreet": null,
"postalCode": null,
"city": null,
"country": null
}
}
}

PUT party​

This API-gateway service call creates or updates a party for a front-office.
The party will only be created/updated if the user is authorized to do so for the provided front office.

Additional information:

  • When mandatory fields are not provided, the request will not be valid.
  • When parties are created, they must have one and only one type-specific property (e.g., individual, company, …)
    • Individual: An individual is a specific type of party which can only exist of 1, also known as a person.
      e.g. β€œHomer Simpsons” is a specific individual.
    • Company: A company is a specific type of Party that forms a legal entity by a group of parties to engage in and operate a business -commercial or industrial- enterprise.
      e.g. β€œHomer Simpsons” works at the β€œSpringfield Nuclear Power Plant” company.
    • Indivision: An indivision is a specific type of party which can exist out of multiple persons.
      e.g., The family β€œThe Simpsons” can be seen as an indivision.
    • Partnership: A partnership is a company of common law.
  • When the party identifier is not known in the system, the party will be created.
  • When the party identifier is known in the system, the party will be updated and the previous state is overwritten.
  • When the party is already known in the system (based on the identifier), the provided party data will be updated.

Request Body examples​

  • Individual
{
"party": {
"externalIdentifier": "partyIdentifier",
"individual": {
"firstName": "Homer",
"lastName": "Simpson",
"address": {
"fullStreet": "Central Park 9/A",
"postalCode": "1234",
"city": "New York",
"country": "US"
}
},
"relatedParties": [
{
"identifier": {
"externalIdentifier": "relatedPartyIdentifier"
},
"relationType": "CHILD"
}
],
"taxInformations": [
{
"tin": "12345678901",
"isPrimary": true,
"useResidentialAddress": true
},
{
"tin": "12345678999",
"isPrimary": false,
"useResidentialAddress": false,
"address": {
"fullStreet": "Groenplaats",
"postalCode": "2000",
"city": "Antwerp",
"country": "BE"
}
}
]
},
"associatedParties": [
{
"externalIdentifier": "relatedPartyIdentifier",
"individual": {
"firstName": "Marge",
"lastName": "Simpson",
"address": {
"fullStreet": "Groenplaats 15",
"postalCode": "2000",
"city": "Antwerp",
"country": "BE"
}
}
}
]
}
  • Company
{
"party": {
"externalIdentifier": "partyIdentifier",
"company": {
"name": "Springfield Nuclear Power Plant",
"companyNumber": "0405450102",
"companyType": "PUBLICLY_LISTED",
"nace": "C.12.0",
"owners": [
{
"externalIdentifier": "ownerIdentifier",
"percentage": 55.0,
"uboType": "OWNERSHIP"
}
],
"address": {
"country": "BE"
}
},
"relatedParties": [
{
"identifier": {
"externalIdentifier": "shareholder"
},
"relationType": "DIRECT_SHAREHOLDER",
"directSharePercentage": 50.25,
"totalSharePercentage": 50.25
}
]
},
"associatedParties": [
{
"externalIdentifier": "shareholder",
"individual": {
"firstName": "share",
"lastName": "holder",
"address": {
"country": "BE"
}
}
},
{
"externalIdentifier": "ownerIdentifier",
"individual": {
"firstName": "Marge",
"lastName": "Simposon",
"address": {
"country": "BE"
}
}
}
]
}
  • Indivision
{
"party": {
"externalIdentifier": "partyIdentifier",
"indivision": {
"name": "Fund X",
"members": [
{
"externalIdentifier": "ownerIdentifier",
"percentage": 55.0,
"uboType": "OWNERSHIP"
}
],
"bankAccounts": {
"IBAN": "BE123456789012",
"Name": "Name of IBAN"
}
},
"relatedParties": [
{
"identifier": {
"externalIdentifier": "shareholder"
},
"relationType": "Contact person",
"directSharePercentage": 50.25,
"totalSharePercentage": 50.25
}
]
},
"associatedParties": [
{
"externalIdentifier": "shareholder",
"individual": {
"firstName": "Marge",
"lastName": "Simpson",
"address": {
"country": "BE"
}
}
},
{
"externalIdentifier": "ownerIdentifier",
"individual": {
"firstName": "Homer",
"lastName": "Simpson",
"address": {
"country": "BE"
}
}
}
]
}
  • Partnership
{
"party": {
"externalIdentifier": "partyIdentifier",
"partnership": {
"name": "Example partnership",
"members": [
{
"externalIdentifier": "ownerIdentifier",
"percentage": 55.0
}
],
"bankAccounts": {
"IBAN": "BE123456789012",
"name": "Example"
}
},
"relatedParties": [
{
"identifier": {
"externalIdentifier": "shareholder"
},
"relationType": "Contact person",
"directSharePercentage": 50.25,
"totalSharePercentage": 100
}
]
}
}

GET Party Answers​

This service can be used to retrieve all the answers applicable for the party.
These can be questions that are asked via dossier information exchange flow (also known as the investor flow) from a linked dossier.

Response examples​

[
{
"questionIdentifier": "Q_HAS_PETS",
"answer": true
},
{
"questionIdentifier": "Q_PET_NAMES",
"answer": "Woofy"
},
{
"questionIdentifier": "Q_PET_FEATURES",
"answer": [
"1",
"3"
]
}
]

Put Party Answers​

This service can be used to update answers applicable for the party.
It’s advised to use the update strategy APPEND to avoid losing answers of questions who are not defined in the body of the message (see more details in the OpenApi spec).
The formatting of the answer depends on the answer type of the question.

Request body examples​

[
{
"questionIdentifier": "Q_HAS_PETS",
"answer": true
},
{
"questionIdentifier": "Q_PET_NAMES",
"answer": "Woofy"
},
{
"questionIdentifier": "Q_PET_AGE",
"answer": 13
},
{
"questionIdentifier": "Q_PET_FEATURES",
"answer": [
"1",
"3"
]
}
]