DeepL · DeepL Terms and Conditions · View original document ↗

API Requests Exceeding Rate May Be Limited with 429 Error

Medium severity Explicitdocumentlanguage Common · 107 of 352 platforms
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity DeepL recorded 17 documented changes in the last 30 days.
Start monitoring updates
Monitor governance changes for DeepL Create a free account to receive the weekly governance digest and monitor one platform for governance changes.
Create free account No credit card required.

This analysis describes what DeepL's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

How other platforms handle this

GitHub Medium

You may not share API tokens to exceed GitHub's rate limitations.

Runway Medium

Your Applications made available to end users must prominently display "Powered by Runway" and link to runwayml.com on applicable user interfaces and in accordance with our Branding Guidelines.

GOAT Medium

GOAT grants to you a limited non-exclusive, non-transferable, revocable license, with no right to sublicense, to download and install the Apps on your personal computers, mobile devices, tablets, wearable devices, and/or other devices...

See all platforms with this clause type →

Monitoring

DeepL has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
DeepL API Growth and DeepL API Developer are designed to process at least 600 characters per minute and per Customer; exceeding use may be limited, and Customers may encounter a 429 "Too Many Requests" error message.

— Excerpt from DeepL's DeepL Terms and Conditions

Applicable regulations

CFAA
United States Federal

Provision details

Document information
Document
DeepL Terms and Conditions
Entity
DeepL
Document last updated
May 5, 2026
Tracking information
First tracked
May 20, 2026
Last verified
May 20, 2026
Record ID
CA-P-045091
Document ID
CA-D-00449
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
d1609857ce95917e69ae41f91e9eb648d2a71d4094bc790166b60a2ddd87b296
Analysis generated
May 20, 2026 23:29 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: DeepL
Document: DeepL Terms and Conditions
Record ID: CA-P-045091
Captured: 2026-05-20 23:29:36 UTC
SHA-256: d1609857ce95917e…
URL: https://conductatlas.com/platform/deepl/deepl-terms-and-conditions/provision/CA-P-045091/api-requests-exceeding-rate-may-be-limited-with-429-error/
Accessed: July 12, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Get Compliance

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does DeepL's API Requests Exceeding Rate May Be Limited with 429 Error clause do?

The clause states: “DeepL API Growth and DeepL API Developer are designed to process at least 600 characters per minute and per Customer; exceeding use may be limited, and Customers may encounter a 429 "Too Many Requests" error message.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 107 platforms. See the full comparison.

Is ConductAtlas affiliated with DeepL?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by DeepL.