Getnada Developer Policy

This Developer Policy governs use of the Getnada API and programmatic access to temporary email inboxes. It forms part of our Terms of Service and Acceptable Use Policy. Technical documentation lives on the Developers page.

• Guest API use is limited to public endpoints and guest-tier temp mail domains.
• Member API keys require a verified Getnada account in good standing.
• API keys must not be shared publicly, embedded in client-side code, or committed to public repositories.
• Session cookies for account routes are for browser use — automate with API keys instead.

We enforce rate limits on inbox open, message fetch, account key creation, and related routes. Plan tiers (guest, member, premium) define domain access, API key counts, and private inbox quotas. Excessive or abusive traffic may be throttled or blocked.

• Use HTTPS for all production API calls.
• Store API keys and inbox JWTs securely; rotate keys if compromised.
• Prefer X-API-Key or Authorization headers over query-string keys when logs may capture URLs.
• Validate responses and handle errors without retry storms.

• Credential stuffing, account takeover, or bypassing bans on other services.
• Bulk creation of inboxes to harvest third-party data or send abuse.
• Circumventing rate limits via distributed attacks or key sharing rings.
• Reselling API access without written authorization from Getnada operators.
• Any use that violates the Acceptable Use Policy or applicable law.

We may update API behavior, endpoints, and this Developer Policy. Integrators should monitor the Developers page and plan for backward-compatible migrations where possible.

Developer policy questions: [email protected]. Contact support · API documentation.