1 · English source
429 — Rate limit exceeded. You have sent too many requests in a given amount of time. Retry after the value (in seconds) of the Retry-After response header. Consider implementing exponential backoff with jitter.
403 — Forbidden. The API key is valid but lacks the required scope. Check the np_scope claim in your JWT, or regenerate the key from the dashboard.
2 · Italian translation
429 — Limite di frequenza superato. Hai inviato troppe richieste in un dato intervallo di tempo. Riprova dopo il valore (in secondi) dell'header di risposta Retry-After. Valuta l'implementazione di un backoff esponenziale con jitter.
403 — Accesso negato. La chiave API è valida ma non ha l'ambito richiesto. Controlla il claim np_scope nel tuo JWT, oppure rigenera la chiave dalla dashboard.
3 · Terminology decisions
| EN | IT | Why |
|---|---|---|
| rate limit | limite di frequenza | Established Italian rendering in HTTP documentation; 'limite di velocità' is wrong (that's speed), 'limite di tariffa' is a false friend. |
| Forbidden (403) | Accesso negato | Matches the reason phrase Italian developers already see in browsers and tools — ecosystem consistency beats literal fidelity. |
| scope | ambito | OAuth2 terminology as localised in AGID/PA guidelines; not 'scopo', which in Italian means 'purpose'. |
| exponential backoff | backoff esponenziale | Technique name stays English (like 'retry'); describing it in Italian would break searchability across docs and Stack Overflow. |