api versioning strategy: endpoint path versus headers?

hey everyone, i'm trying to decide on the best way to handle api versioning for a new microservice. should we go with the classic /v1/users and /v2/users approach, or is using custom headers like Accept: application/vnd.myapp.v1+json more flexible in the long run? curious about the trade-offs you've encountered with each, especially regarding client adoption and ease of maintenance