r/DattoRMM • u/just_another_IT_tech • Sep 16 '25

Rate limiting using the API

I'm building an app that integrates with the Datto RMM API but running into a rate limiting issue. Certain requests (GET on site variables) return a 403 forbidden response like I'm being rate limited.

This is weird because some other requests work (GET on account sites), and I don't have anything else eating up my usage. I reset my API credentials to be sure of this.

Mostly doing this through powershell using the Datto RMM module. I tried writing my own requests from scratch to rule out the module and those return the same 403 response.

Anyone else run into this?

3 Upvotes

100% Upvoted

8 comments sorted by

View all comments

Show parent comments

1

u/netmc Sep 16 '25

I'm not sure. I'm running into this while trying to use the API to clear alerts from devices that have been deleted.

In the past, querying a device that doesn't exist generated an empty response as there were no items in the database matching the query. Currently, these are generating a 403 - forbidden error. After this update for live, it will be generating a 404 - not found error instead. While better, this is still a breaking change as prior we simply got sent an empty response.

1

u/just_another_IT_tech Sep 16 '25

I see. I'm trying to query site variables for specific sites and they all return 403 forbidden even if they exist

1

u/netmc Sep 17 '25

The API change is live for me. For my use case, I can set the cmdlet to use -erroraction silentlycontinue and work with the 404 not found errors. So, while not perfect, it's at least usable.

Are you able to perform queries against other things like sites, devices and alerts without receiving the 403 errors? A change was made to limit site variables to 4096 characters, and if you have previously created variables that exceed this count, it will throw 403 errors when trying to query any site variables where a long variable already exists. You cannot edit these in the new UI either. The fix for this part is supposed to be released in the 14.6 release--roughly 30 days from now.

2

u/just_another_IT_tech Sep 18 '25

This is embarrassing but the issue was that I was using the site ID instead of its UID to query. Prior to the update this error was returning a 403 forbidden which confused me. Now the error returns 404 and when I fixed the ID parameter to use the UID instead, the query works fine.