Rate limits for Twitter For Websites

[Roy_CTAR]

Hi all,

Update: I found this old question that seems to say there is no rate limit for widgets. I will leave this question up though because it would be good to get confirmation of this again 7 years later in case things have changed, and also to confirm about oEmbed as well.
old question

I have spent a lot of time reading through documentation and the developer agreement and policy, and I want to make sure I understand correctly. Am I right to think that there are no rate limits for Twitter for Websites usage?

Specifically I’m just looking to use widgets.createTweet() and/or the oEmbed API and possibly widgets.load(). I want to display user-uploaded text urls as full tweet widgets on a forum-style website.

It’s not clear if this is subject to rate limits. The developer agreement says that everyone using a “Twitter API” must create a developer account and state their use case, so I did, but I can also see that using the features I mentioned doesn’t actually require an API key, so those function calls aren’t associated with the account. And the developer agreement defines “Twitter API” as all of twitter’s apis, so that surely includes Twitter for Websites, not just Twitter API v2 which I know is separate.

The free and basic plans have tweet pull caps of 0 and 10,000 respectively. Are oEmbed calls and widgets.createTweet() not considered pulls?

Any help would be greatly appreciated, and please tell me how you know the answer if you provide one, as this is a legal issue I don’t want to just go off hunches/estimations/personal interpretations.

Many thanks for reading