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?

Inizia tracciando il modo in cui la risposta POST costruisce i link per l’endpoint annidato /locations/{location ID}/contacts e confrontali con i link /contacts/{contact ID} restituiti. Determina dove viene perso il contesto della risorsa padre e definisci test che verifichino che l'ID della location venga mantenuto nei link generati senza modificare i percorsi di risorse non correlate.