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?

Empieza rastreando cómo la respuesta POST construye los enlaces para el endpoint anidado /locations/{location ID}/contacts y compáralos con los enlaces /contacts/{contact ID} devueltos. Determina dónde se pierde el contexto del recurso padre y define pruebas que verifiquen que el ID de la ubicación se conserva en los enlaces generados sin cambiar las rutas de recursos no relacionados.