Request

Response

    BIM 360: Assets API Rate Limits

    The BIM 360 Assets 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.

    Rate Limits

    The Asset service applies three different rate limits to Asset API requests. In general:

    These rate limits determine the number of requests the Assets service can accept per APS user account (specified in a 3-legged token).

    Note that this rate is not a service guarantee. In the uncommon case where total service use is too high across all clients, the accepted request rate might drop until traffic subsides.

    Data-Reading Endpoints

    This rate limit applies to all endpoints that read data.

    Data-Modification Endpoints

    This rate limit applies to all endpoints that modify (create, update, or delete) data.

    Relationship Endpoints

    This rate limit applies to all endpoints that modify (add or delete) relationships.

    EndpointsLimit (requests/minute)Scope
    This rate limit applies to these endpoints combined:

    50 Per APS user account

    Scope

    Each rate limit is measured across the entire combined set of that rate limit’s API endpoints for each APS user account. As an example, if during one minute one application makes 600 requests of GET v2/projects/:projectId/assets under user account X, and a second application makes 500 requests of POST v1/projects/:projectId/categories:batch-get under the same user account X, their combined rate is 1100 requests per minute, which exceeds the data-reading endpoint rate limit.

    Violation Notification

    If an application makes an Assets API request that exceeds this rate limit, the Assets 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.