☰
Login
Signup
Home
›
API clients
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Sign In
Register
Categories
Recent Discussions
Activity
Categories
13.9K
All Categories
0
Incidents
156
Node JS client
40
Go client
793
.Net API client
380
Kite Publisher
537
.Net / VBA / Excel (3rd party)
457
Algorithms and Strategies
998
Java client
1.1K
API clients
404
PHP client
4K
Python client
347
Mobile and Desktop apps
1.4K
Market data (WebSockets)
3.3K
General
In this Discussion
February 2019
sujith
February 2019
connectmike
February 2019
arjunkw3
Historical API - How to buy subscription?
connectmike
February 2019
in
API clients
Hi, I can't see the option to take historical API subscription in my developer account?
Tagged:
historical API
historical data
API Subscription
Historic data subsciption
arjunkw3
February 2019
edited February 2019
Same issue here. When trying to make calls for historical data, then getting insufficient permission error.
PHP Fatal error: Uncaught PermissionException (403) 'Insufficient permission for that call.'
Went to my app permissions section, can't see the access to candle data.
arjunkw3
February 2019
After looking around in deep,, i found out that Historical Data is an addon service of 2000 credits. Its available in your app page.
connectmike
February 2019
Okay, It means it will be visible once I take Kite connect subscription.
Is there any documentation page for Historical Candle API which mentions restrictions on API calls, features etc?
sujith
February 2019
You can check out
API documentation here
.
connectmike
February 2019
Do we have any restrictions on candle API?
sujith
February 2019
You can check out
FAQs here
.
connectmike
February 2019
Thanks
@sujith
This discussion has been closed.
PHP Fatal error: Uncaught PermissionException (403) 'Insufficient permission for that call.'
Went to my app permissions section, can't see the access to candle data.
Is there any documentation page for Historical Candle API which mentions restrictions on API calls, features etc?