README: orgs, invites, password reset, receipts, SMTP env, renewal (part of #80) #10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of Cairn #80. The README's endpoint table, config, and data model predated everything that shipped for the customer area.
Added to the endpoints table (paths taken verbatim from the
mux.HandleFuncregistrations, not guessed):PATCH /v1/licenses/{id}(label),POST /v1/account/password,POST /v1/password-reset+/confirm, the seven org endpoints (GET /v1/org,POST /v1/org/name,POST /v1/org/invites,DELETE /v1/org/invites/{email},POST /v1/invites/accept,POST /v1/org/members/{email}/role,DELETE /v1/org/members/{email}), and the two receipts endpoints.Config gained
PADDLE_API_KEY(receipts) and the fullSMTP_*set (SMTP_HOST/PORT/USER/PASS/FROM, withSMTP_PASSWORD/MAIL_FROMaliases), with the degrade-quietly behaviour whenSMTP_HOSTis unset — matchingemail.go.The webhook row now notes that a subscription renewal refreshes the same license id rather than issuing a duplicate, and the data model paragraph documents the
orgsandinvitesmaps plus the per-licenselabel/orgId.Verified every path and env var against the source in a read-only inspection run before writing — no invented endpoints.
reasonfield #23