SumUp · Rate Limits

Sumup Rate Limits

SumUp enforces rate limits on its REST API to ensure fair usage and platform stability. When limits are exceeded the API returns HTTP 429 Too Many Requests. Developers should implement exponential backoff when handling 429 responses. Specific numeric thresholds are not publicly documented.

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

It captures 1 rate-limit definition.

Tagged areas include Payments, Point-of-Sale, Card Readers, Checkout, and Fintech.

1 Limits
PaymentsPoint-of-SaleCard ReadersCheckoutFintechMobile PaymentsOnline Payments

Limits

Global (all endpoints)
SumUp advises retrying requests with exponential backoff when a 429 status code is received. Specific request-per-second or request-per-minute thresholds are not publicly published in the developer documentation.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/sumup-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.