Beginning on March 11, we changed some behavior to our API: we began caching repetitive API calls for one hour.
We've been monitoring this change for the last week, and we've confirmed it's behaving as expected.
- This change only impacts customers who are using our API either through API calls in snippets or explicit API calls.
- This change improves API performance on repetitive API calls; you should get a faster response time from calls that are made often.
- The caching applies to the entire query string. So if you're doing paginated API calls, for example, each page should get its own cache, since the page number is part of the query string. (You may want to ensure that paginated calls have explicit sorts.)
For example: the Release Notes section on the homepage of this knowledge base uses an API snippet to pull the most recent release notes; since anyone hitting our homepage prompts the call to be run, it's now cached for an hour. This can mean that there's a slight delay in the list updating, but the load times are faster!
We sent out advance notice of this change to our Critical Admin Updates and Product Newsletter email lists. If you didn't get the notice but would like to subscribe to one or both of those lists moving forward, you can sign up here. (Spoiler: we will have another change coming out that will impact the API in the next few weeks, so if you aren't yet subscribed, now is a good time!)
