Open jamesefhawkins opened 1 week ago
+1 ticket - interested in increasing rate limits for the query endpoint.
+1 interested in more granularity for the session recordings API. We are B2b and we help customer analyze and understand their session recordings. They want to grant us access to specific session recordings and, sometime, they ask us not to access person data.
Feature request
DON'T WORK AT POSTHOG? IF YOU ARE READING THIS - would love feedback on APIs you'd like reliable access too.
This will let our customers build analytics into their product.
The most common use case is b2b2c companies wanting to offer a usage dashboard to their business customers, but we also see it in b2b.
We have repeatedly had users trying to build on top of our API and hitting issues with rate limiting for example. We can't just increase rate limits as it will cause us a huge increase in infra costs. This will give a reliable, scalable way of accessing PostHog's API, where we can help users hit our API in a way that is cost effective on both sides.
We think the right starting point is:
But we can see lots of other use cases:
Any we are missing?
Debug info