首页 > 解决方案 > DataManagement API 的实际配额和速率限制是多少

问题描述

我从这个页面知道DataManagement API 有速率限制,但我很难找到有关实际速率的任何信息。

在什么时间段内可以进行多少次 API 调用?有配额吗?

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

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

标签: autodesk-forgerate-limitingquota

解决方案


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

与此同时,根据我们的内部记录,S (50 RPM)、M (300 RPM) 和 L 尺寸 (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   

注意:以上还不是官方的,可能会在没有事先通知的情况下发生变化,所以请继续关注官方开发门户的更新


推荐阅读