DataManagement API 的实际配额和速率限制是多少

What are the actual quotas and rate limits for the DataManagement API

我从 this page 得知 DataManagement API 有速率限制,但我很难找到有关速率实际是多少的任何信息。

什么时间段可以拨打多少API次? 有配额吗?

我希望找到类似 this 的描述,用于设计自动化 API 的速率限制和配额,但我没有成功。

我们知道我们可以在超过速率限制时处理 429 错误。目前处理错误不是我们关心的。我们想知道实际的限制,以便判断最好的方法来做我们想做的事情,并判断 Forge 对于我们的应用程序的长期可行性。

感谢您告知我们,并将告知门户团队填写速率限制信息。

同时,根据我们的内部记录,S (50 RPM)、M (300 RPM) 和 L-size (800 RPM) 限制适用于以下 DM 端点:

GET /projects/{project_id}/folders/{folder_id}  M   
GET /projects/{project_id}/folders/{folder_id}/parent   S   
GET /projects/{project_id}/folders/{folder_id}/contents M   
GET /projects/{project_id}/folders/{folder_id}/refs S   
GET /projects/{project_id}/folders/{folder_id}/relationships/refs   S   
GET /projects/{project_id}/folders/{folder_id}/relationships/links  S   
GET /projects/{project_id}/items/{item_id}  M   
GET /projects/{project_id}/items/{item_id}/parent   S   
GET /projects/{project_id}/items/{item_id}/refs M   
GET /projects/{project_id}/items/{item_id}/relationships/refs   S   
GET /projects/{project_id}/items/{item_id}/relationships/links  S   
GET /projects/{project_id}/items/{item_id}/tip  S   
GET /projects/{project_id}/items/{item_id}/versions L   
GET /projects/{project_id}/versions/{version_id}    M   
GET /projects/{project_id}/versions/{version_id}/item   S   
GET /projects/{project_id}/versions/{version_id}/refs"  S   
GET /projects/{project_id}/versions/{version_id}/relationships/refs S   
GET /projects/{project_id}/versions/{version_id}/relationships/links    S   
GET /projects/{project_id}/versions/{version_id}/downloads  S   
GET /projects/{project_id}/versions/{version_id}/downloadFormats    S   
GET /projects/{project_id}/jobs/{job_id}    M   
GET /projects/{project_id}/downloads/{download_id}  M   
GET /projects/{project_id}/folders/{folder_id}/search   M   
POST    /projects/{project_id}/storage  M   
POST    /projects/{project_id}/items    S   
POST    /projects/{project_id}/versions M   
POST    /projects/{project_id}/folders/{folder_id}/relationships/refs   S   
POST    /projects/{project_id}/items/{item_id}/relationships/refs   S   
POST    /projects/{project_id}/versions/{version_id}/relationships/refs S   
PATCH   /projects/{project_id}/items/{item_id}  S   
PATCH   /projects/{project_id}/versions/{version_id}    S   
POST    /projects/{project_id}/downloads    S   
POST    /projects/{project_id}/commands M   
POST    /projects/{project_id}/versions/{version_id}/relationships/links    S   
PATCH   /projects/{project_id}/versions/{version_id}/relationships/links/{link_id}  S   
POST    /projects/{project_id}/folders  S   
PATCH   /projects/{project_id}/folders/{folder_id}  S   
GET /hubs   S   
GET /hubs/{hub_id}  S   
GET /hubs/{hub_id}/projects S   
GET /hubs/{hub_id}/projects/{project_id}    S   
GET /hubs/{hub_id}/projects/{project_id}/hub    S   
GET /hubs/{hub_id}/projects/{project_id}/topFolders M   

注意:以上内容尚未正式发布,可能会更改w/o,请提前通知,因此请继续关注官方开发门户的更新