I have a login API endpoint
It checks if the phone number has been validated. If not it will call
POST http://127.0.0.1:8080/api/account/sendsms country_code=1, phone_number=1234567
How can I prevent abuse to requesting sms? (It'll cost money on my part. I also have throttle function)
I only want sms to be sent if
/login failed (at this point email has been validated)
The way I do is to send a custom header
X-TOKEN-SMS which acts like an authorization header with jwt token. X-TOKEN-SMS jwt token is created at
/login if phone number is not validated = True.
/sendsms decodes the jwt without error, proceed with requesting sms.
If jwt decodes with error then the front-end will redirect to
Is this method a good practice?
How do you allow an API endpoint to be accessed only if some endpoint has been accessed?
Let's say I have an endpoint that can only be accessed by an authorized user
The user can GET points(retrieve all of his/her points) POST points (create a new point) or PATCH (update a point)
How can I prevent an authorized user from abusing the POST /points? They might add points as they please, which is not what my app want it to be. Adding points should be handled by the app logic.
If adding point should not be consumed by REST API, then create a new row directly to the db is more secure?
I found a similar question asked before Secure Rest api from authenticated user But couldn't seem to understand it.