Consolidated Account Statement (CAS) Parser

This API parses two types of CAS - NSDL and CAMS (Refer Portfolio Tracking for more info). Files are uploaded against the same API and the API is intelligent enough to detect the type of file uploaded. Outputs also differ based on the type of file uploaded as the information provided in both the CAS has some differences.

RapidAPI key generation

In order to start using our APIs you will have to signup with RapidAPI. On registering with RapidAPI you will receive a X-RapidAPI-Key (for Ex. a980asd621fgh1a2a74737fc10afp18b4a6jsn3b6f0lkj2poi). This needs to be passed in the header of every http call you make to avail our service.

Request

Method	Endpoint	Description
`POST`	/prod/docs_parser	`multipart/form-data` with keys `password` and `file`

Shell

curl --request POST \
    --url https://wealth-management.p.rapidapi.com/prod/docs_parser \
    --header 'Accept: application/json' \
    --header 'X-RapidAPI-Host: wealth-management.p.rapidapi.com' \
    --header 'X-RapidAPI-Key: Your API key generated from RapidAPI' \
    --header 'content-type: multipart/form-data' \
    --form password=password_to_open_file \
    --form file=@path_to_file_including_extension

key	Description
`file`	fully qualified path to file including it's filetype
`password`	password to open the uploaded file

Try out Parser API

Response

CAMS Parser

There are 2 types of CAMS report that can be generated by a customer - Summary and Detailed. In summary report will not provide the transaction details of the individual funds. API supports both Summary and Detailed Reports. Let's see how the response is for a detailed report:

Detailed Report

{
    "reportType": "MutualFund",
    "report": [
        {
            "ISIN": "inf090i01iq4",
            "fundName": "Franklin India Smaller Companies Fund - Direct Plan - Growth",
            "isinConfidence": 100,
            "reportDate": "07-Jun-2022",
            "reportDayNAV": "90.4414",
            "reportDayValuation": "0.00",
            "reportOpeningUnits": "0.000",
            "schemeCode": "FTI478",
            "advisor": "0000000000",
            "folioNumber": "21529948",
            "pan": "XXXXXXXX",
            "totalUnits": "0.000",
            "transactions": [
                {
                    "date": "28-May-2018",
                    "xnType": "OTHERS",
                    "rawDescription": "***Registration of Nominee***"
                },
                {
                    "date": "29-May-2018",
                    "amount": "100000.00",
                    "balanceUnits": "1572.011",
                    "nav": "63.6128",
                    "units": "1572.011",
                    "xnType": "PURCHASE",
                    "rawDescription": "Purchase"
                },
                {
                    "date": "29-May-2018",
                    "amount": "40.00",
                    "xnType": "STAMP_DUTY",
                    "rawDescription": "*** Stamp Duty ***"
                },
                {
                    "date": "10-Feb-2020",
                    "amount": "-87544.92",
                    "balanceUnits": "0.000",
                    "nav": "55.6904",
                    "units": "-1572.011",
                    "xnType": "REDEMPTION",
                    "rawDescription": "Redemption Of Units , less STT"
                },
                {
                    "date": "10-Feb-2020",
                    "amount": "1.00",
                    "xnType": "STT",
                    "rawDescription": "*** STT Paid ***"
                }
            ],
            "unitsIntegrityMaintained": true,
            "amountIntegrityMaintained": true
        }
    ]
}

key	Description
`reportType`	For CAMS this field's value will be `MutualFund`
`report`	Array representing all the individual mutual funds details
`ISIN`	ISIN is a 12-digit alphanumeric code that uniquely identifies a specific Mutual Fund. Radiowire is deriving this value based on MF details. This is not provided by CAMS. This is unique internationally and can be used to fetch any other details of the fund including but not limited to NAV
`fundName`	Name of the fund as provided in CAMS report
`isinConfidence`	Represents confidence in the correctness derived value of ISIN. We are deriving ISIN based on available details. Sometimes we will not be able to derive it correctly. In such cases thie value will be less than 100.
`reportDate`	Date on which this mutual fund details (NAV) are based on. Generally all MFs in a report will have same date but there can be exceptions.
`reportDayNAV`	NAV of the mutual fund on the `reportDate` as given in the CAMS report
`reportDayValuation`	Total value of mutual fund holding for a particular ISIN
`reportOpeningUnits`	Units of mutual fund at the start of the report duration
`schemeCode`	Scheme code of the fund as provided in the CAMS report
`advisor`	In case of regular funds, the ARN of the advisor as given in CAMS report. This is wrong ARN sometimes.
`folioNumber`	folioNumber of the fund as provided in the CAMS report
`pan`	PAN of the investor. Under one report there can be multiple PANs in cases where investor has used multiple PANs under same email id while investing
`totalUnits`	Units of mutual fund in hand at the end of the report duration. If the report is generated for the duration 01-01-1990 to 01-01-2022, then this represents the total units in hand on 01-01-2022
`transactions`	Array representing all the transactions under one `ISIN`
`date`	date of transaction
`amount`	amount of transaction
`balanceUnits`	after the transaction how much total units are in balance. This will be available only `PURCHASE` and `REDEMPTION` `xnType`s.
`nav`	NAV of the fund at the time of transaction. This will be available only `PURCHASE` and `REDEMPTION` `xnType`s.
`units`	units being transacted. This will be available only `PURCHASE` and `REDEMPTION` `xnType`s.
`xnType`	There are multiple types of transactions that can happen - `PURCHASE`, `REDEMPTION`, `STAMP_DUTY`, `STT`, `OTHERS`
`rawDescription`	Description given by RTA for this transaction.
`unitsIntegrityMaintained`	This is a flag given by radiowire to check if the total units of a particular fund matches the overall mutual fund transactions. If this value is `false`, then it means that the total units doesn't match the units in transaction and the parsing is incorrect.
`amountIntegrityMaintained`	This is a flag given by radiowire to check if the total amount of a particular fund matches the overall mutual fund transactions. If this value is `false`, then it means that the total units doesn't match the units in transaction and the parsing is incorrect.

Summary Report

{
    "reportType": "MutualFund",
    "report": [
        {
            "ISIN": "inf846k01ew2",
            "fundName": "Axis Long Term Equity Fund - Direct Growth",
            "isinConfidence": 100,
            "reportDate": "13-Jun-2022",
            "reportDayNAV": "64.4339",
            "reportDayValuation": "139100.35",
            "schemeCode": "128TSDGG",
            "folioNumber": "91064610821/0",
            "totalUnits": "2158.807",
            "unitsIntegrityMaintained": true,
            "amountIntegrityMaintained": true
        }
    ],
    "totalValueMatched": true
}

In a summary report, the only difference is that there are no transactions mentioned in this report. From an API response standpoint there is one additional field:

key	Description
`totalValueMatched`	This is a flag given by radiowire to check if the document parsing is complete. This flag being `false` means that overall parsed data has some discrepancy even if individual funds are parsed correctly.
All other fields are same as that in Detailed Report

NSDL Parser

API already working. Detailed documentation coming soon

You can try out the API with NSDL CAS and it will successfully respond back. If you know how to comprehend NSDL CAS then API response is self-explanatory.