It’s technically not rate limited. However, like with all aspects of the API you have to use it with respect – I wouldn’t barrage it with parellel requests for example – keep things serial. Make sure you’re responding to any kinds of error conditions, especially 40X and 50X – and back off exponentially when they happen.
Eventually, I would expect this method to have a rate limit associated with it – not for the app/user combo necessarily, but more for the user itself – like most of our write allowances. So if you want to accomodate that, you could pre-emptively handle a 429 as well.