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?

Beginne damit nachzuverfolgen, wie die POST-Antwort Links für den verschachtelten /locations/{location ID}/contacts-Endpunkt erstellt, und vergleiche sie mit den zurückgegebenen /contacts/{contact ID}-Links. Ermittle, an welcher Stelle der Kontext der übergeordneten Ressource verloren geht, und definiere Tests, die überprüfen, dass die location ID in generierten Links erhalten bleibt, ohne Pfade anderer Ressourcen zu ändern.