Request

Response

    Forma: Files API Rate Limits

    The Forma Files API observes a set of rate limits to ensure that all clients get sufficient service and that runaway applications don’t consume excessive resources. You’ll find general information about rate limits in APS Rate Limits and Quotas.

    Each endpoint of the Files API has its own independent rate limit. Both of these rate limits apply per application (specified by client ID):

    EndpointsLimit (requests/minute)Scope
    POST /projects/{project_id}/exports 100 Per application (specified by client ID)
    GET /projects/{project_id}/exports/{export_id} 200 Per application (specified by client ID)
    GET /projects/{project_id}/published-versions/{version_id}/linked-files 200 Per application (specified by client ID)
    GET /projects/{project_id}/packages 200 Per application (specified by client ID)
    GET /projects/{project_id}/packages/{package_id}/resources 200 Per application (specified by client ID)
    GET /projects/{project_id}/custom-attribute-definitions 2000 Per application (specified by client ID)
    GET /projects/{project_id}/custom-attribute-definitions/{customAttributeDefinitionId}/items 2000 Per application (specified by client ID)

    Violation Notification

    If an application makes a Files API request that exceeds these rate limits, the Files service returns an HTTP 429 error (described in detail in APS Rate Limits and Quotas).

    Changing Limits

    APS Rate Limits and Quotas describes how to request rate limit changes for APS APIs.