For users who primarily rely on the API for data access rather than order execution, it would be valuable to introduce a safeguard or configuration option that disables order placement through a given API key.
For instance, a user seeking data access for approximately 18,000 symbols is currently required to maintain two API keys, both of which retain order execution privileges. This creates an unnecessary level of risk and redundancy. Providing a data-only API key option would enhance security, improve usability, and better align the platform with the needs of data-focused users.
With the paid version of Kite Connect, access includes live market data, historical data endpoints, as well as order-related endpoints as part of a single offering.
From a security standpoint, this does not inherently create additional risk, as access is granted only after proper authentication. The primary concern would arise only if API credentials are shared or not handled securely.
At present, a separate data-only API key or configuration to disable order placement is not supported. Our subscription plans are currently structured based on common usage patterns and broader user requirements.
From a security standpoint, this does not inherently create additional risk, as access is granted only after proper authentication. The primary concern would arise only if API credentials are shared or not handled securely.
At present, a separate data-only API key or configuration to disable order placement is not supported. Our subscription plans are currently structured based on common usage patterns and broader user requirements.