API rate limits

How our rate limits for the Print.com API work.

This article describes the rate limits of the Print.com API: the limit per endpoint, what happens when a limit is exceeded, how to build an integration that stays within the limits, and how to request a higher limit. Rate limits keep the platform fast and available for all customers and protect it against abuse, such as automated login attacks.

Key facts

  • /login: maximum 100 requests per minute, per account.
  • Price, suppliers and orders endpoints: maximum 1,000 requests per 5 minutes, per account.
  • Requests above a limit are rejected. Repeatedly exceeding a limit can lead to a temporary block of the account.
  • When a rate limit is hit, status code 429 Too many request is returned.
  • Call /login once to obtain a token and reuse that token until it expires. Do not log in before every API request.
  • The /login limit was recently lowered to protect against login spam attacks. The other limits are unchanged.
  • Higher limits are available on request. The customer pays for the additional infrastructure costs.
  • Rate limits apply to Production enviroments: https://platform.print.com and https://api.print.com
  • The also apply to Staging enviroments: https://platform.stg.print.com and https://api.stg.print.com

Current limits

Limits are counted per account.

EndpointLimitWindow
/login100 requests1 minute
Price endpoints1,000 requests5 minutes
Suppliers endpoints1,000 requests5 minutes
Orders endpoints1,000 requests5 minutes

On average, 1,000 requests per 5 minutes equals about 3 requests per second. All applications, scripts and servers that use the same account share the same limit.

When you exceed a limit

Requests above the limit are rejected until the time window resets. Repeatedly exceeding a limit can lead to your account being blocked temporarily.

When a request is rejected:

  1. You'll receive a status code 429 Too many request.
  2. Stop sending requests to that endpoint.
  3. Wait before retrying, and increase the wait time with every failed attempt (exponential backoff).
  4. Resume at a lower request rate once requests succeed again.
    Retrying immediately in a loop makes the problem worse: it keeps your integration above the limit for longer.

Rules for staying within the limits

Integrations, including code written or generated by AI assistants, should follow these rules.

  1. Reuse the token. Call /login only to obtain a token. Store the token and reuse it for all subsequent requests until it expires. Do not call /login before every API request.
  2. Share one token per account. Do not let parallel processes, workers or servers each log in separately. They all count toward the same /login limit of 100 requests per minute.
  3. Cache prices. Store price responses for products and configurations you request often. Refresh them on a schedule, not on every page view or quote.
  4. Cache supplier data. Supplier information changes rarely. Retrieve it periodically, not per request.
  5. Throttle batch jobs. When syncing catalogues or orders, spread requests evenly so the total stays below 1,000 requests per 5 minutes (about 3 requests per second on average).
  6. Back off on rejection. When a request is rejected because of a rate limit, wait before retrying and double the wait time on each attempt. Never retry immediately in a loop.
    Example of token reuse and exponential backoff (illustrative pseudocode, not an official SDK):

    token = None
    
    def get_token():
        global token
        if token is None or token.is_expired():
            token = login()  # counts toward the /login limit: 100 requests per minute
        return token
    
    def call_api(request):
        delay = 1  # seconds
        for attempt in range(5):
            response = send(request, token=get_token())
            if not is_rate_limited(response):
                return response
            sleep(delay)
            delay *= 2  # 1, 2, 4, 8, 16 seconds
        raise RateLimitError("Rate limit still exceeded after 5 attempts")

Recent changes

The limit on /login was recently lowered to protect the platform against automated login (spam) attacks. The limits for the price, suppliers and orders endpoints are unchanged. Integrations that request a new token for every API call are most likely to be affected. Requesting a token once and reusing it until it expires usually resolves this.

Frequently asked questions

What are the rate limits for /login and for the price, suppliers and orders endpoints?

/login allows 100 requests per minute per account. The price, suppliers and orders endpoints allow 1,000 requests per 5 minutes per account.

Have the rate limits changed recently?

Yes, the /login limit was recently lowered to protect the platform against login spam attacks. The limits for the price, suppliers and orders endpoints have not changed.

Why is my integration hitting /login limit?

The most common cause is an integration that logs in before every API request. Request a token once and reuse it until it expires.

My account is blocked. Can it be unblocked?

Contact Print.com per email with the endpoints involved. Before resuming traffic, make sure your integration reuses tokens and backs off on rejected requests, so the block does not recur.

Can I get a higher limit, for example for price requests?

Yes, on request. Higher limits require extra infrastructure capacity, and the customer pays for those additional costs. Contact Print.com with your expected request volume and use case.