我从this page知道DataManagement API具有速率限制,但是我很难找到有关速率实际值的任何信息。
在什么时间段内可以进行多少次API调用? 有配额吗?
我希望找到像this这样的描述,用于Design Automation API的速率限制和配额,但是我没有取得任何成功。
我们知道,超出速率限制后,我们可以处理429错误。目前,我们不关心处理错误。我们想知道实际的限制,以便判断最佳方法来做我们想做的事情,并判断从长远来看Forge对于我们的应用程序是可行的。
答案 0 :(得分:1)
感谢让我们知道并将让门户团队知道填写速率限制信息。
同时,根据我们的内部记录,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
注意:以上内容尚未正式发布,可能会更改,恕不另行通知,因此请随时关注官方开发人员门户的更新