This is an old discussion, so it's not true anymore that the routes have the :uuid convertor.

I tried and it works correctly with Beanie and ObjectId, which is the default on the provided example: https://github.com/fastapi-users/fastapi-users/tree/master/examples/beanie

It doesn't work with sqlalchemy tho.

@SnoozeFreddo I don't know if you already checked this, but for me the pitfall was that I let FastAPI-Users register its routes before I registered the routes of my own application. I had to make sure it happens the other way around, so a DELETE on /users/me first matches my custom endpoint if possible and then falls through to the /users/<id> endpoint of FastAPI-Users.

Makes sense, u mean that you use app.include_router before the auth_router and you do not define your custom endpoind on the auth_router ( get_auth_router) but a custom one?

My super quick workaround was to have it on a completetly different name

users_router = fastapi_users.get_users_router(...)

@users_router.delete('/delete/me',status_code=status.HTTP_204_NO_CONTENT)
async def delete_my_account(
        request: Request,
    user_manager: UserManager = Depends(get_user_manager),
    user: User = Depends(current_active_verified_user),

):
    await user_manager.delete(user, request)
    return 204

Exactly, I have a couple of different routers, including a custom users router with multiple endpoints (DELETE /users/me, GET /users for paginated users search, etc.). Then I register them in order.

# register my app's routers
for router in _some_func_that_returns_all_my_routers():
    app.include_router(router)
# register FastAPI-Users' routers
# ...

Your solution looks very intuitive to me, I might have even tried the same back then, but when declaring your /users/me endpoint on the users_router you get from FastAPI-Users, the internal /users/<id> endpoint is already there and takes precedence.