Plumma · Rate Limits
Plumma Rate Limits
Plumma Rate Limits is the machine-readable rate-limit profile for Plumma on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions.
Limit state is signalled in the published, observed, and note response headers.
Tagged areas include Telecommunications, Network APIs, Italy, Europe, and GSMA Open Gateway.
3 Limits
publishedobservednote
Transcribed from the provider's documentation on 2026-09-07 — connect.plumma.it/plumma-connect-docs/ — documents `guide....
View Source
TelecommunicationsNetwork APIsItalyEuropeGSMA Open GatewayCAMARAAPI AggregatorFraud PreventionIdentity VerificationSIM SwapKYCAge VerificationNumber VerificationTelco IntelligenceSoftware Development
Limits
per-api-key
2/1s
Enforced per API key and expressed by the provider in requests per second (RPS).
per-api-key
5/1s
"The production rate limit can be increased upon request." The SLA (Art. 4.1) adds that a default limit may be applied at Plumma's discretion to protect the infrastructure and that the agreed threshold is set in the Technical Addendum.
per-api-key
180/1d
Counted in COMMANDS executed across all requests in a calendar day, not in API calls — one request carrying 18 commands consumes 18 of the budget. The limit is unchanged after an account goes live. CONFLICT, recorded as published: the Terms of Service (Art. 2.3a) states "a maximum API call limit 20/day … could be increased asking your account manager" for the same sandbox, while the Technical Guide and Integration Guide both state 180 commands/day.
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.