The first RedX API version is implemented behind authenticated accounts and production safety gates: transactional sending, hosted email verification, scoped keys, quotas, idempotency, and authorization-code Sign In with PKCE.
Send transactional text or HTML email through an authenticated RedX mailbox with recipient-based quotas, request IDs, and idempotent retries.
Issue expiring verification links, store only token hashes and encrypted destinations, and poll completion through a separate read scope.
Add the glowing RedX login button through an authorization-code flow with mandatory PKCE S256 and exact redirect-URI matching.
Receive delivery, bounce, complaint, verification, and authentication events with signatures and retry handling.
The production button uses a black surface, blood-red outline, red glow, and centered RedX mark. Customer applications receive a short-lived authorization code—not the user's password—and exchange it with a mandatory PKCE verifier.
GET /oauth/authorize?client_id=rx_client_...scope=openid profile emailcode_challenge_method=S256One email unit equals one recipient. Paid checkout remains disabled until Stripe billing, bounce handling, sender reputation controls, and capacity safeguards pass their own production tests.
The account sender uses the API owner's authenticated hosted RedX mailbox. The optional managed sender is fixed to verification@red-xai.com and remains unavailable until red-xai.com has a real Stalwart domain, mailbox, TLS, MX, SPF, DKIM, DMARC, reputation, and abuse controls.
Existing verified RedX accounts can use the developer console while public registration and paid billing remain safely gated.
Open developer console