Scribd
Upload
16 views

Nesl API Doc

The NESL Web Service API processes JSON requests by validating them against a predefined JSON schema. If the input JSON is valid, the same JSON is returned as a response; if invalid, an error code and message are provided. The API includes various models for different sections of the request, detailing the structure and required fields for successful processing.

Uploaded by

sakshi.tyagi152
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
16 views

Nesl API Doc

The NESL Web Service API processes JSON requests by validating them against a predefined JSON schema. If the input JSON is valid, the same JSON is returned as a response; if invalid, an error code and message are provided. The API includes various models for different sections of the request, detailing the structure and required fields for successful processing.

Uploaded by

sakshi.tyagi152
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

NESL Web Service

Overview

This Nesl API basically used to process json request.It accepts a json input and then
validates it against a json schema,if the json is validated successfully we will be
getting the same request json as a response. But if the input json does not validate
as per the defined json schema it returns error code along with the message which
will provide the reasons why the json is not processed successfully.

API Details

Request URL: http://localhost:8080/nesl-0.0.1-SNAPSHOT/nesl/neslRequestwithValidation


Request Method : POST
API Name : neslRequestwithValidation
Input : NeslRequestVO
Output : NeslRequestVO

Models

1. NeslRequestVO
String regType
String txnID
String signFlag
String estampFlag;
String f2f;
String state;
String brname;
String braddr;
List<EstampSection> eStampDtls;
List<ParticipantSection> participantDtls;
List<LoanDetails> loadDtls;
List<SecurityDetails> securityDtls;
List<ESignCoordinatesDetails> esignDetails;
List<DocumentDetails> docDetails;
List<EntityDetails> entityDtls;

2. EstampSection :
String firstparty
String secondparty
Double stampDutyAmount
Double considerationPrice
String descriptionofDocument
String stampdutyPaidby
Integer articleCode

3. ParticipantSection
Integer prtcptenttyId
String fulnm
List<Reltocntrct> reltocntrct
String emlid
Integer cntrprtycntmobno
String altemlid
Integer altmobno
String is_individual
String doi
List<Lglcnstn> lglcnstn
String panno
List<Ovdtype> ovdtype
String ovdid
String comaddr
Integer pin
String signatoryGender
List<Integer> documentIds
Integer seqno
Integer entityID

4. Reltocntrct
String creditor
String debtor
String guarantor
String co_Obligant
String beneficiary

5. Lglcnstn
String resident

6. Ovdtype
String panno_OvdType
String driving_license_OvdType
String voter_id_OvdType
String passport_OvdType
String others_OvdType

7. LoanDetails
String loanno
Double snctnamt
List<Ntrofcrdt> ntrofcrdt
List<Fundtyp> fundtyp
List<Currofsanc> currofsanc
List<Crdtsubtyp> crdtsubtyp
String fcltynm
Integer toutstndamt
List<String> currofdebt
List<String> isacctclosed
List<String> event
String expiry_date
String remarkparta

8. Ntrofcrdt
String Financial
String Operational
9. Fundtyp
String funded
String non_fund

10. Currofsanc
String iNR

11. Crdtsubtyp
String Credit_Facility
String propertyBuyer
String nPL
String gRNT
String mFNL
String gOLD
String aGRL
String jLGL
String sHGL

12. SecurityDetails
String Credit_Facility
String propertyBuyer
String nPL
String gRNT
String mFNL
String gOLD
String aGRL
String jLGL
String sHGL

13. ESignCoordinatesDetails
Integer prtcptenttyId
Integer documentID
Integer coordinates

14. DocumentDetails
Integer documentID
String docData

15. EntityDetails
String entty_pan
String entty_name
String doiForIncorp
String eml_id
Long cntct_no
String reg_addr
String reg_pin
String comm_addr
String comm_pin
Integer entityID
List<String> lgl_cnstn

Required Input Json Schema


Output Scenarios

Case 1: When the json request is processed successfully

Input Json

Response Json

Case 2 : When the input json is not valid


Input Json

Response Json

You might also like