Endor Labs · Rate Limits

Endor Labs Rate Limits

The Endor Labs REST API applies per-tenant request throttling and enforces pagination on list endpoints to protect the platform. List responses are paged via list_parameters.page_size and page_token, and large result sets must be retrieved page by page. Specific numeric request-per-minute or request-per-second limits are not published; throttled requests are expected to return HTTP 429. Per-tenant values are governed by the customer agreement and are visible to administrators.

Endor Labs Rate Limits is the machine-readable rate-limit profile for Endor Labs on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests and objects.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Security, Software Supply Chain, SCA, Reachability, and AppSec.

2 Limits Throttle: 429
SecuritySoftware Supply ChainSCAReachabilityAppSecAI SecurityRate LimitingQuotasThrottling

Limits

Requests Per Tenant tenant
requests
see provider documentation
Per-tenant request throttling; specific numeric value not published.
List Page Size request
objects
see provider documentation
List endpoints paginate via list_parameters.page_size and page_token.

Policies

Pagination
Use list_parameters.page_size and list_parameters.page_token to page through large result sets rather than requesting all objects at once.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and honor any Retry-After header.
Field Masking
Use list_parameters.mask to request only needed fields and reduce response size and load.

Sources