Tracking down excessive API requests and potential webhook integration issue.

Our API requests have skyrocketed. We're using the js client with CDN enabled, so not sure where these requests could come from. Is there a way to track down where the requests are coming from?

CDN requests sitting at 7k

You developing at the same time on the project?

and we haven't updated content often enough to warrant the CDN to have cleared

not that dataset, no

we have separate production and dev datasets

I don't think we're doing enough dev work to warrant 100k extra requests

Does the

sanity dataset export

affect this API usage ?

Interesting that your spike of activity is on the 7th of April, which coincides with the spike I am seeing on that same day of (unexpected) bandwidth usage… https://sanity-io-land.slack.com/archives/C9Z7RC3V1/p1617952768000500

Hey User, the following could be causing your spike:• previews
• active local development
• increased content activity (editors working in the studio)
• low incremental static regeneration settings (e.g. setting to 1s).
If you share your project id we can take a look and give you more specifics.

Thanks Doesn't look like development, it's going up the same amount of requests per day and over the weekend where there was no development. Project ID is

r80nmzas

I am doing a sanity export daily, but can't see how that'd be 100k requests/day.

Thanks, User. We’ll start looking into it.

Thanks - it's an insane number of API requests, I really don't think we can be responsible for it unless something is seriously wrong in our code. If there's any info you can share on who the requester is and what the queries are, that'd help us track it down in case it is us.

It's going mental.

Looks like we're hot on the heels of the problem, it's potentially an issue with our webhook integration.Suggestion: If there were some slightly more info/stats in the sanity dashboard we probably could have narrowed this down sooner. i.e. api calls per dataset instead of just project level. Top 5 or 10 queries. Top 5 requesting IPs.

I'll review the API usage tomorrow, but at the moment it looks like we found the cause 👍 As mentioned above, more info on the API requests (even if it's limited to top 5s for developer & advanced plans) would have helped debug this a lot sooner.

glad you’ve got it sorted. I agree that more insight into API requests would be super helpful in situations like this (and maybe help to catch problems before they blow through a plan’s limits). I definitely recommend dropping your thoughts into the ideas and feedback channel or opening a feature request on gh.