Pass a methods list to the route decorator, then branch on request.method inside the view. Without that list, a route answers only GET.
@app.route('/api/users', methods=['GET', 'POST'])
def handle_users():
if request.method == 'POST':
return create_user()
return get_users()
@app.route('/api/users/<int:user_id>', methods=['PUT', 'DELETE'])
def handle_user(user_id):
if request.method == 'PUT':
return update_user(user_id)
elif request.method == 'DELETE':
return delete_user(user_id)
Flask adds HEAD for you whenever GET is allowed, and it answers OPTIONS requests on its own. A request with any other method gets 405 Method Not Allowed, and the view never runs.
One view for several methods suits code that shares setup. Separate views are often easier to read, and Flask has shortcut decorators such as @app.get() and @app.post() for them. For a whole resource, MethodView maps each HTTP method to a class method with the same name, such as get or delete.
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The interactive diagram is below the answer - jump to diagram ↓ · Below it, the related concept . Jump to it ↓
The diagram below the answer is the concept . Jump to it ↓