We need API changes to accommodate Non-Household Beneficiaries-

1. Beneficiary Registration API: POST {TMC_BASE_URL}/tm-api/registrar/registrarBeneficaryRegistrationNew -
   nullable parameters: {      "placeOfCurrentLiving": "Railway Platform", {String}
       "nameOfInstitution": "ABC Hostel", {String}
   }
   For household beneficiaries, these should be null or omitted.

1. 2. Beneficiary Sync API: POST {TMC_BASE_URL}/identity-api/rmnch/syncDataToAmrit
   Request envelope: 
   Unknown macro: {     "beneficiaryDetails"}
2. And we will need this data in downsync APIs as well.

The backend should update:

1. Beneficiary request DTO for both endpoints.
2. Beneficiary database/entity model.
3. Insert/update service logic.
4. Sync processing logic for beneficiaryDetails.
5. Database migration adding nullable columns, for example:
   • place_of_current_living
   • name_of_institution
6. Response DTOs and download mapping, if these fields must sync back to the app.

One important contract decision is needed: for the "Other" option, should the server receive:

 

{{

{ "placeOfCurrentLiving": "Custom location" }

}}

or retain both the category and custom text:

 

{{

{ "placeOfCurrentLiving": "Other", "otherPlaceOfCurrentLiving": "Custom location" }

}}