Switch Customer Classification

post

https://api.cloud.mbanq.com/v1/v1/clients/{clientId}?command=switchclassification

Dynamically optimize customer service delivery by adjusting their institutional classification. This endpoint allows for the strategic categorization of customers based on their evolving value, profile, and financial needs. By refining these classifications, you can unlock tailored services, adjusted fee structures, and personalized interactions that align with each customer's specific standing within your ecosystem.

Function	Webhook Reference
Switch Classification	Switch Customer Classification Webhook

Path Params

clientId

integer

required

Defaults to 123

The associated Customer Id.

Body Params

classificationId

integer

required

Defaults to 658

Client Classification Identifier
This field specifies the classification type for the client based on whether they are registered as a person or entity.
Example Values:

Client Person: 681 - Default (Client Person Classification)

Retrieving Valid Classification Codes
To obtain all available classification codes, use the API Get Code Value with code name ClientClassification-PERSON.
For Client Entities: /v1/codeValues?codeName=ClientClassification-ENTITY
For Client Persons: /v1/codeValues?codeName=ClientClassification-PERSON
Example: 658

expectedApplicableDate

string

The expected applicable date.The date format should be as per the format mentioned in the dateFormat parameter.
Pattern: 'XXX'
Example: '14 February 2024'

dateFormat

string

If the field 'expectedApplicableDate' is passed, then this parameter is mandatory. It specifies the dataformat, that's being used.
Pattern: 'XXX'
Example: 'dd MMMM yyyy'

locale

string

Defaults to en

The locale of the client. 'en' will be passed as default.
Pattern: 'XX'
Example: 'en'

Headers

tenantId

string

required

The ID of your banking instance visible in the MBANQ Console.

Responses

Language

Credentials

Bearer

JWT

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200The Customer Classification is updated successfully.

400The request fails if the name details are missing.

401Authentication credentials were missing or incorrect.

403Client Legal Form is not linked to the product.

404The specified client or classification does not exist.