API field naming inconsistent with README docs — register expects 'name' not 'username' #25

New issue

Closed

opened 2026-05-14 14:30:16 +00:00 by Mark · 1 comment

Mark commented

2026-05-14 14:30:16 +00:00

Owner

Bug

The auth register endpoint expects the field name but frontend developers naturally send username.

Evidence

username field → 400: {"error":"Email, password, and name are required"}
name field → 201: Success

Similarly, subscription creation expects billingDate and amount instead of more intuitive price and billingCycle.

Impact

Two issues: (1) the error message doesn't tell the caller which field name to use, and (2) the API surface doesn't match common conventions.

Severity

BLUE Low — Works with correct field names, but confusing for new API consumers. Missing field name in error response makes debugging harder.

## Bug The auth register endpoint expects the field `name` but frontend developers naturally send `username`. ## Evidence `username` field → 400: `{"error":"Email, password, and name are required"}` `name` field → 201: Success Similarly, subscription creation expects `billingDate` and `amount` instead of more intuitive `price` and `billingCycle`. ## Impact Two issues: (1) the error message doesn't tell the caller which field name to use, and (2) the API surface doesn't match common conventions. ## Severity BLUE **Low** — Works with correct field names, but confusing for new API consumers. Missing field name in error response makes debugging harder.