I am developing and operating an application called **Scanner**, which uses Kite Connect API to access market data for stock scanning, checking live pricing, screening, charts, and related market-analysis features.
I have configured the Kite Connect application with my web address correctly
The Zerodha authorization page opens successfully, and I can reach the authorization screen. However, after clicking **Authorize**, the application fails during the callback/authentication process and returns the following error:
**{"status":"error","message":"Missing or empty field `authorize`","data":null,"error_type":"InputException"}**
Could you please help me determine whether this error is originating from the Kite Connect API or from my application's OAuth/session-generation request?
Specifically, I would appreciate your guidance on:
1. Whether the Redirect URL above is correctly configured for Kite Connect. 2. What parameters Zerodha should return to the callback after successful authorization. 3. Whether the callback should receive a `request_token` and then exchange it for an `access_token`. 4. Whether there are any current changes to the Kite Connect authentication/session-generation API that could cause this error. 5. Whether the `"authorize"` field in the error indicates an incorrect request being sent to a Kite Connect endpoint. 6. Whether there is anything specific I should verify in my Kite Connect app configuration.
You may reach for Instant Support and that will be helpful . I Paid the 500 INR for the API .
If required, I can provide sanitized request/response details, timestamps, callback information, or screenshots showing the error.
Please let me know what diagnostic information you need from my side to identify the issue.
Please ensure the API request uses Content-Type: application/x-www-form-urlencoded and sends the form parameters in the URL-encoded format specified in the documentation. Also verify that all required fields, including the request_token are correctly populated. You may refer to the similar discussion here.
Content-Type: application/x-www-form-urlencodedand sends the form parameters in the URL-encoded format specified in the documentation. Also verify that all required fields, including therequest_tokenare correctly populated. You may refer to the similar discussion here.