Maybe I'm looking in the wrong place. I have dived into the code and looked around but I can't find any place to get the rate limiting headers.
Because I'm wrapping the official SDK in my own layer of control for the oAuth passing, inits, etc. I want a centralized way to handle 429 errors and prevent hitting daily limits over and over again.
I already have a way to throttle and also handle 429 errors. However I need the extra information about the rate limiting to know what limit I'm hitting, the short term one or the long term one.
The idea is this, if the connected oAuth user has less than 100 tokens left for that day, I need to save the date when it's going to reset so meanwhile I can let the user know they've hit API limits instead of spamming the Pipedrive API with repeated 429s.
Any feasable way to do this? The only other issue I see on this is here from 2017 and I can't follow where all of that went, looks pretty dated: #27
Maybe I'm looking in the wrong place. I have dived into the code and looked around but I can't find any place to get the rate limiting headers.
Because I'm wrapping the official SDK in my own layer of control for the oAuth passing, inits, etc. I want a centralized way to handle 429 errors and prevent hitting daily limits over and over again.
I already have a way to throttle and also handle 429 errors. However I need the extra information about the rate limiting to know what limit I'm hitting, the short term one or the long term one.
The idea is this, if the connected oAuth user has less than 100 tokens left for that day, I need to save the date when it's going to reset so meanwhile I can let the user know they've hit API limits instead of spamming the Pipedrive API with repeated 429s.
Any feasable way to do this? The only other issue I see on this is here from 2017 and I can't follow where all of that went, looks pretty dated: #27