I am working on a CRUD app where I have things called requests that can have many iterations. I have an endpoint to hit called iteration/create/requestId. When this page is hit I show an empty table with fields for the user to fill in. I take the index of the row and assign it to a field in the iteration called the iteration number. If a user were to manually enter the URL and not follow the UI then they would be able to save new iterations with duplicate iteration numbers.
My question is if I'm not following restful practices since there is assumed state that create will be called only once per request and that the iteration/edit/requestId will subsequently be called. I think I should be designing everything such that it can be hit and there will be no side effects but I'm up against a deadline and not sure what to prioritize?