EDIS Details

This API allows you to fetch the holding authorisations you have already completed.

USE CASE

Check which holdings are authorised for sale, with the quantity authorised and the quantity already used.

Details

This API provides information about holding authorizations that have been successfully completed.
The request takes no parameters. Send only the Authorization header.
Only authorisations that were completed successfully are listed. You can sell only authorised holdings.
qty is the quantity authorised and qtyUtlize is the part of it already used.
startDate, endDate and noOfDays show how long the authorisation stays valid. The CDSL page states that an authorisation is valid till the end of the day, whether or not the sell is completed.
status and reason describe the outcome of the transaction. errCode is NA when there is no error and errorCount gives the number of errors.
transactionId is the ID to use with EDIS Inquiry. source is a code for where the transaction was started (W in the sample response).
Rate limits differ between the Standard and Prime plans. See Plans & rate limits.

Response Attributes

Attribute	Data Type	Description
`clientId`	string	Client ID of the account for which the holding authorization was processed.
`isin`	string	ISIN of the security for which the holding authorization was completed.
`qty`	float	Quantity of the security authorized.
`qtyUtlize`	float	Quantity of the authorized holding that has been utilized.
`entryDate`	string	Date and time on which the authorization entry was created.
`startDate`	string	Start date of the authorization's validity period.
`endDate`	string	End date of the authorization's validity period.
`noOfDays`	int	Number of days for which the authorization remains valid.
`source`	string	Source through which the authorization was initiated (e.g. `W` for web).
`status`	string	Status of the authorization transaction, e.g. `SUCCESS`.
`reason`	string	Description of the outcome of the authorization transaction.
`internalTxnId`	string	Internal transaction ID generated by FYERS for the authorization.
`dpTxnId`	string	Depository Participant (DP) transaction ID associated with the authorization.
`errCode`	string	Error code returned for the transaction, if any (`NA` when none).
`errorCount`	string	Count of errors encountered while processing the transaction.
`transactionId`	string	Unique transaction ID for the holding authorization, usable to query status via the Inquiry API.

Python is not available for this example. Showing cURL instead.

RequestcURL

curl --location --request GET 'https://api.fyers.in/api/v2/details' \
 --header 'Authorization: app_id:access_token'

{"s": "ok", "code": 200, "message": "", "data": [{"clientId": "DXXXX4", "isin": "INE313D01013", "qty": 1.0, "qtyUtlize": 0.0, "entryDate": "07/06/2021 13:58:56", "startDate": "07/06/2021", "endDate": "07/06/2021", "noOfDays": 1, "source": "W", "status": "SUCCESS", "reason": "eDIS Transaction done successfully", "internalTxnId": "915485", "dpTxnId": "0706202171316317", "errCode": "NA", "errorCount": "0", "transactionId": "915484108176"}]