sendotp.email

Changelog

Product updates

A chronological record of customer-facing improvements to sendotp.email.

Latest updates

  • Purpose-specific email branding

    Set a distinct sender name or subject line for each OTP purpose, such as login or report access. Purposes without a custom setting continue to use your account defaults.

  • OpenAPI specification

    The API specification is now available at /openapi.json, with endpoint definitions, request and response schemas, examples, and authentication details for compatible developer tools.

  • Free-plan usage notices

    Free accounts receive a daily email notice after reaching their included monthly send allowance. OTP delivery continues normally.

Security and account protection

  • Hardened dashboard sign-in

    Dashboard login now uses an internal OTP service instead of a public API key. Legacy dashboard-login keys were revoked, and new keys cannot use that reserved name.

  • Rate limits for login requests and verification

    Dashboard sign-in now applies rate limits to both a privacy-preserving email fingerprint and the requesting client IP before a code is sent or verified.

  • Safer webhook delivery

    Webhook endpoints must use public HTTPS hostnames, signing secrets are encrypted at rest, and delivery records redact credentials and query strings.

Audit history and dashboard improvements

  • API audit history

    Review authenticated send and verify activity in the dashboard, including request outcome, API-key context, and event details. OTP codes, recipient email addresses, request bodies, and API secrets are never logged.

  • Clearer integration activity

    Integration and delivery views now make it easier to review account activity alongside the API history that produced it.

Need integration details? Read the API documentation.