RESTful API design - multiple identifiers for a resource

I am designing REST API and I'm wondering if its fine to have same resource accessible under two different identifiers like in such scenario:

There are three resources Team, Player, TeamInvitation. Players can be invited to the team. I think of such design:

/teams list of teams

/teams/1 concrete team

/teams/1/invitations invitations for players to concrete team

And now I would like to make it easy to get list of team invitations for concrete player:

/players list of players

/players/1 concrete player

/players/1/invitations team invitations for concrete player

Is that design ok? Or maybe following design would be more restful:

/invitations

With query parameters for team and player.