MediaValet · Rate Limits

Mediavalet Rate Limits

MediaValet does not publish fixed numeric rate limits for its Open API. The API is fronted by Azure API Management, which enforces throttling per subscription key; when limits are exceeded the gateway returns HTTP 429 Too Many Requests. MediaValet also provides a Bulk endpoint that batches multiple operations into a single HTTP request, which is the recommended way to reduce request volume for high-throughput workflows such as mass metadata updates. Verify any account- or plan-specific request quotas with MediaValet.

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

It captures 3 rate-limit definitions, measuring requests, operations, and records.

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

Tagged areas include Digital Asset Management, DAM, Media, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Digital Asset ManagementDAMMediaRate LimitingQuotas

Limits

API Requests per Subscription Key subscription
requests
not published
Throttled by Azure API Management per subscription key; exact numbers are not documented.
Bulk Batch Size request
operations
configurable per bulk request
The Bulk endpoint packs multiple operations into one HTTP call to reduce request count.
Search / List Pagination request
records
paged
List and search endpoints return paginated results via offset/count style parameters.

Policies

Throttling
The Azure API Management gateway returns HTTP 429 when a subscription key exceeds its allowance.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.
Batching
Use the Bulk endpoint to combine multiple operations into a single request for high-volume metadata work.

Sources