# AutoCDSL 3.0 is now Free!

{% hint style="info" %}
**The problem :** Usually, once you authorize the stock for debit with CDSL using TPIN, the authorizations will remain valid only for one day. This means you have to re-authorize the stock with CDSL TPIN in case the sell transaction didn't complete on the same day. Since it is a daily grind for retail investors and sometimes we might be left out causing us not able to sell stocks and stock also might get reversed while completing authorization. 

Also, remembering the TPIN and entering the OTP number can also be a tedious process. To overcome all these problems, AutoCDSL will be of great help.
{% endhint %}

{% hint style="info" %}
How AutoCDSL **can save 24hr** in your life in a year ?

There are **253** trading days in a year

Imagine you take **6** min every day to perform this OTP authentication

253\*6 = **1513** minutes

1513/60 = **25.3** hours (more than a day)

lol ! Thus automation can save a day.
{% endhint %}

{% hint style="info" %}
Zerodha Kite web-based login no longer supports pin based authentication and is replaced by Two-Factor-Authentication (2FA), AutoCDSL has also updated with the same, please visit Configuring 2FA section in the documentation
{% endhint %}

## Getting Started

After successfully testing 5 months with no charges

{% embed url="<https://youtu.be/gu2Cd09zqtw>" %}

Live Demo Video&#x20;

<https://youtu.be/YAaXSB_-O8s>

{% embed url="<https://youtu.be/YAaXSB_-O8s>" %}

You can watch a step-by-step video here , AutoCDSL is FREE !

<https://www.youtube.com/watch?v=y91eHEk7CHM>

{% embed url="<https://youtu.be/y91eHEk7CHM>" %}
AutoCDSL 3.0
{% endembed %}

{% hint style="info" %}
**Inorder to successfully setup AutoCDSL 3.0 you will require the following files**

* **LambdaFunction.zip**
* **LambdaLayer.zip**
* **gmail.py**
* **token.json and credentials.json (to be generated by user)**

AutoCDSL 3.0 is now **Free !**

**Download at** [**https://github.com/CasCard/AutoCDSL**](https://github.com/CasCard/AutoCDSL)
{% endhint %}

### Guides: Jump right in

Follow our handy guides to get started on the basics as quickly as possible:

{% content-ref url="setup/1.setting-up-gmail-api" %}
[1.setting-up-gmail-api](https://abelcheruvathoor.gitbook.io/autocdsl/setup/1.setting-up-gmail-api)
{% endcontent-ref %}

{% content-ref url="setup/2.-generating-token-json" %}
[2.-generating-token-json](https://abelcheruvathoor.gitbook.io/autocdsl/setup/2.-generating-token-json)
{% endcontent-ref %}

{% content-ref url="setup/3.setting-up-aws-lambda" %}
[3.setting-up-aws-lambda](https://abelcheruvathoor.gitbook.io/autocdsl/setup/3.setting-up-aws-lambda)
{% endcontent-ref %}

{% hint style="info" %}
**Important Note:** Unauthorized distribution of any file, via any medium is strictly prohibited, proprietary and confidential.

You may modify the code only for your personal purposes

**None of the user credentials or OTP are stored by this application or transmitted. Entire power of the application is under the user as the entire is setup is done based on the user's email.**
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://abelcheruvathoor.gitbook.io/autocdsl/autocdsl-3.0-is-now-free.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.