MODIVO · Rate Limits
Modivo Rate Limits
Modivo Rate Limits is the rate-limit profile for MODIVO on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the ratelimit_standard, legacy_x_headers, retry_after, and observed_on response headers.
Tagged areas include Company, Consumer, Fashion, E-Commerce, and Retail.
0 Limits
ratelimit_standardlegacy_x_headersretry_afterobserved_on
Read from the provider's live responses on 2026-08-12 — Live unauthenticated responses from modivo.pl/rest/V1/dir....
View Source
Limits
MODIVO publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
MODIVO publishes no rate limits for any API surface, and neither surface returns a rate-limit header. Full response headers were captured on both: the REST response carried date, content-type, set-cookie, vary, x-frame-options, cache-control, x-cache, age, strict-transport-security, cf-cache-status, server and cf-ray; the GraphQL response added x-magento-cache-id, x-route, x-content-type-options, x-xss-protection, x-correlation-id, x-causation-id, x-request-id and access-control-allow-credentials. No RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, X-RateLimit-*, or Retry-After appeared on any response. A consumer therefore receives no runtime budget signal at all and must self-throttle blind.
CompanyConsumerFashionE-CommerceRetailMarketplaceRetail MediaCommerceCheckoutCatalogGraphQLAdobe CommerceMagentoPolandCentral Europe
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.