Implement POST on /register #1

Closed
opened 2026-02-25 06:17:35 +00:00 by charlie · 0 comments
Owner

Create a POST endpoint for /register

Request

The Request body should look like the following

{
  email: string,
  pass: string,
  fname: string,
  lname: string,
  phonenbr: string,
  clubid: number
}

Response

Success

  • If the user exist and the password is correct the Response must have status code 200 and include a payload following this model
{
  message: "Please wait admin approval"
}

Failure

  • If the Request is malformed the Response must return status code 400 and include this payload:
{
  message: "Request malformed"
}
# Create a POST endpoint for /register ## Request The Request body should look like the following ```json { email: string, pass: string, fname: string, lname: string, phonenbr: string, clubid: number } ``` ## Response ### Success - If the user exist and the password is correct the Response must have status code 200 and include a payload following this model ```json { message: "Please wait admin approval" } ``` ### Failure - If the Request is malformed the Response must return status code 400 and include this payload: ```json { message: "Request malformed" } ```
charlie self-assigned this 2026-02-25 06:17:35 +00:00
charlie changed title from Implement handler for post request on /register to Implement POST on /register 2026-02-25 06:57:48 +00:00
charlie added this to the Working AUTH milestone 2026-02-26 10:48:19 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ULFSII/phoenix_api#1
No description provided.