Do asset URL's incur the same rate limiting that the API does?

We are building an app that intends to read PDF’s uploaded into webflow for products to be used for editing and customizing books with images and text.

Currently we are calling an API to get those asset urls, and then downloading the ArrayBuffers from them and attempting to store them in local storage, this was done becuase of the 60/min rate limit on the API.

If we ran this one time and stored the PDF asset urls instead and then just pulled the ArrayBuffer fresh each time we come back to the page is it going to hit the same rate limit or are those accessed as a direct connection to that asset in some external storage?

Hey @Jordan_Riser! Welcome to the forum!

Hitting the asset URL directly does not have any rate limits like the API.

Asset URLs will count towards the sites bandwidth, however.