Skip to main content
This endpoint allows you to create a Customer Related Party (CRP) using an existing profile. This is a two-step process that involves searching for an existing profile and then creating the CRP using that profile’s data. This approach allows you to reuse existing customer data when creating related parties, ensuring data consistency while allowing for CRP-specific customizations.

Important Rules - Read Before Implementation

Profile Linkage Requirements
  • profileId and profileReferenceId must be populated from the profile search response (Step 1)
  • The profileId tells the system which existing profile to use for the new CRP
  • Without these fields, the system will not link to the existing profile
Synced Fields (Shared with Original Profile)The following fields are synced with the original customer profile. Changes to these fields will affect both the CRP and the original profile:
  • profileReferenceId: Can be changed, but changes will reflect on the original customer
  • particular: All fields within the particular object are synced including:
    • name, alias, formerName
    • email, phone, address
    • nationality, countryOfResidence, countryOfBirth
    • gender, dateOfBirth, salutation
    • identityDocumentType, identityNumber, identityIssuedDate, identityExpiryDate
Important: Any modification to these fields in the CRP will update the original profile and affect all other CRPs using the same profile.
CRP-Specific Fields (Not Synced)The following fields are specific to the CRP. Changes to these fields will NOT sync with the original profile:
  • other: All fields within the other object including:
    • industry, occupation
    • sourceOfFunds, sourceOfWealth
    • bankAccount, paymentMode
    • onBoardingMode, transactionBehaviour
    • additionalInformation, productServiceComplexity
    • natureOfBusinessRelationship
    • undischargedBankrupt, ownershipPercentage, status
These fields are carried over from the original profile during creation but are maintained separately for the CRP. You can modify them without affecting the original profile or other CRPs.

Key Differences: Creating CRP with Existing Profile vs New Profile


Two-Step Process Overview

Creating a CRP with an existing profile requires:
  1. Step 1: Search for and retrieve the existing profile using the profile search API
  2. Step 2: Create the CRP using the profile information obtained from Step 1

Step 1: Search for Existing Profile

First, search for the existing profile you want to use for the CRP.
Full API Reference: For complete API documentation, see Search Profile for CRP Creation

Endpoint

Path Parameters

Query Parameters

Headers

Sample Request

Sample Response - Success (200)


Step 2: Create CRP Using the Profile

Once you have retrieved the profile information, use it to create the CRP using the standard CRP creation endpoint.

Endpoint

Path Parameters

Headers

Sample Request Body - Individual CRP with Existing Profile

Sample Response Body - Success (200)


Complete Workflow Example

Here’s a complete example of creating a CRP with an existing profile:

1. Search for Profile

2. Extract Key Fields from Response

From the response, extract:
  • profileId: 8521
  • profileReferenceId: “sdsds342342”
  • particular: (entire object)
  • other: (entire object)

3. Create CRP Request

4. Verify CRP Creation

The response will contain the newly created CRP with:
  • New CRP id
  • Original profileId maintained
  • Linked to the main customer via parentId