GET
/api/auth/google
Start Google OAuth. Redirects the browser to Google, then back to the callback.
No body. Sets short-lived OAuth state in KV.
Endpoints powering authentication, domain workflows, subscriptions, and account data on RegisterMySite. Base URL depends on your deployment host.
https://registermysite.com
JSON request & response bodies
Session cookie or Bearer token where noted
Start Google OAuth. Redirects the browser to Google, then back to the callback.
No body. Sets short-lived OAuth state in KV.
Start GitHub OAuth. Same pattern as Google with GitHub authorize URL.
OAuth callback. Query: code, state. Creates/finds user in D1, opens Durable Object session, sets session cookie, redirects to /dashboard.
GitHub OAuth callback — same session flow as Google.
Current user from session cookie. 401 if logged out.
{
"user": {
"id": "uuid",
"email": "[email protected]",
"name": "Jane Doe",
"avatar_url": "https://…",
"provider": "google"
}
}
Destroys Durable Object session and clears the session cookie.
Protected. Requires valid session. Returns welcome payload and user profile for the dashboard UI.
{
"message": "Welcome back, Jane!",
"user": { "id": "…", "email": "…", "name": "…", "provider": "github" }
}
Creates a subscription for a pricing plan. Body fields from the checkout form.
Integrate with Stripe (or similar) on the server; return clientSecret or redirectUrl.
Request body
{
"plan": "starter" | "growth" | "pro",
"firstName": "Jane",
"lastName": "Doe",
"email": "[email protected]",
"company": "Acme" | null,
"country": "US",
"postal": "90210"
}
Plans
Interactive domain search and WHOIS-style checks are primarily implemented in the Domain Search UI (including client-side availability checks). Server-side registration handoff can target:
Additional tool pages (QR, TLD search, payments demos) are served as static/app routes under
/tools/…. Extend this reference as you expose dedicated JSON endpoints for those tools.
Liveness check for monitoring and deploy verification.
{
"ok": true,
"timestamp": "2026-07-26T11:00:00.000Z"
}
| Status | Meaning |
|---|---|
| 400 | Missing or invalid parameters |
| 401 | Not authenticated / invalid session |
| 403 | Authenticated but not allowed |
| 404 | Route or resource not found |
| 500 | Server error (check Worker logs) |
Error bodies typically include {"message": "…"}.
APIs run on Cloudflare Workers with
D1 (users), KV (OAuth state),
and Durable Objects (sessions). Deploy and manage with
wrangler. You own the project code and data bindings in your account.
Need a custom endpoint for domains, billing webhooks, or your client dashboard? We implement APIs in-house and hand off the source.