I have been making requests to this endpoint since at least a month, and the "profile-url" property is always present in the response whenever the contact email belongs to a registered contact. However, half an hour ago I performed made the same request and this time the "profile-url" was not present. Since that moment, I have been performing similar requests and the property is still not present in the response. I believe it should be present, if my understanding of the following documentation is correct: https://legacydocs.hubspot.com/docs/methods/contacts/contacts-overview
I checked the Developers Announcement board and I didn't found any information related to any change in this endpoint. However, I might be wrong... Is the property being removed from the endpoint?
Property "profile-url" is missing in the response to my request to the Contacts API
SOLVE
I think I have addressed this in places where all three of you are, but just in case. When we removed the profile-token, the consequence was that it also eliminated the profile-url which is dependent upon the token. We made the poor assumption that this was known. We will strive to be more clear in the future and I, personally, will try to overcommunicate upcoming changes as @Jacob02 suggested in another post.
Property "profile-url" is missing in the response to my request to the Contacts API
SOLVE
I have the same issue. We used the profile-url to populate it in the CRM lead record, so that sales rep can go straight to the specific Hubspot contact page.
Is there any other way to build the url with what is being included in the contacts response data?
Property "profile-url" is missing in the response to my request to the Contacts API
SOLVE
I think I have addressed this in places where all three of you are, but just in case. When we removed the profile-token, the consequence was that it also eliminated the profile-url which is dependent upon the token. We made the poor assumption that this was known. We will strive to be more clear in the future and I, personally, will try to overcommunicate upcoming changes as @Jacob02 suggested in another post.