Links not accurate for nested resource

I'm writing a multi-tenant application where absolutely every request has to have a location ID as part of the URL or as a param. How do I make it so that when I POST to a nested resource, like to /locations/{location ID}/contacts, the item I get back includes a link that looks like /locations/{location ID}/contacts/{contact ID}? Right now the links returned from the API are just /contacts/{contact ID}, but this won't work because IDs aren't guaranteed to be unique across locations.

Is there a way for the nesting of resources to only go one way like this?

Commencez par retracer la manière dont la réponse POST construit les liens vers l’endpoint imbriqué /locations/{location ID}/contacts et comparez-les aux liens /contacts/{contact ID} renvoyés. Déterminez à quel endroit le contexte de la ressource parente est perdu et définissez des tests qui vérifient que l’ID de location est conservé dans les liens générés, sans modifier les chemins d’autres ressources.