Skip to content
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.

Email confirmation RESTful api #56

Open
hsklia opened this issue Nov 16, 2018 · 1 comment
Open

Email confirmation RESTful api #56

hsklia opened this issue Nov 16, 2018 · 1 comment

Comments

@hsklia
Copy link

hsklia commented Nov 16, 2018

I'm trying to create a new endpoint for confirming email after registering new user but I doubt if it's right or not?
Here is what I have in my mind :

/users/{id}/confirmations/{token}

  • "confirmation" or "confirmations" ?
  • When the endpoint is a resource? is "confirmation" a resource?
@kinlane
Copy link

kinlane commented Nov 16, 2018

confirmations.

I would consider confirmations a resource. You can POST new one, and you can GET the details of one at any point in the future.

Confirmations are a resource on their own, as well as a sub-resource of users.

Hope that helps you in your journey....

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants