# Latest source/drill downs not updating for API calls

**URL:** <https://community.hubspot.com/t/latest-source-drill-downs-not-updating-for-api-calls/63843>\
**Category:** APIs & Integrations\
**Created:** [August 26, 2022, 4:35pm UTC](https://community.hubspot.com/t/latest-source-drill-downs-not-updating-for-api-calls/63843 "2022-08-26T16:35:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![JustinDowty](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/justindowty/32/63860_2.png) [@JustinDowty](https://community.hubspot.com/u/JustinDowty)\
**Post date:** [August 26, 2022, 4:35pm UTC](https://community.hubspot.com/t/latest-source-drill-downs-not-updating-for-api-calls/63843/1 "2022-08-26T16:35:33Z")

</div>

I would like to use the latest source/drill down properties for detecting whether or not an update to a contact record was done by my own integration or not, to avoid circular updates back and forth. I came across this article, and it is recent so this looks to be a new feature: [Understand Original and Latest traffic source properties](https://knowledge.hubspot.com/contacts/understand-source-properties). Through testing I noticed that the latest source/drill down 1 values do not update to Offline Sources/API \> contacts-upsert as it seems they should be according to that document. Since this is a new feature, maybe this is a bug report. I am aware that one option could be to pull individual contact records using propertiesWithHistory, but it would be much more streamlined to have the latest source/drill down property update and be available in the way described in that article.

---

<div class="post-metadata">

**Author:** ![Jaycee\_Lewis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaycee_lewis/32/61352_2.png) [@Jaycee\_Lewis](https://community.hubspot.com/u/Jaycee_Lewis)\
**Post date:** [August 29, 2022, 4:14pm UTC](https://community.hubspot.com/t/latest-source-drill-downs-not-updating-for-api-calls/63843/2 "2022-08-29T16:14:33Z")

</div>

Hey, @JustinDowty 👋 I am not 100% sure, and I’d love to try to get us more information. Can you provide any additional details about the following:

- the specific endpoint you are using
- an example or sample request and response
- any additional context

Thank you! — Jaycee

---

<div class="post-metadata">

**Author:** ![JustinDowty](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/justindowty/32/63860_2.png) [@JustinDowty](https://community.hubspot.com/u/JustinDowty)\
**Post date:** [August 29, 2022, 4:27pm UTC](https://community.hubspot.com/t/latest-source-drill-downs-not-updating-for-api-calls/63843/3 "2022-08-29T16:27:39Z")

</div>

Hi Jaycee,

Here would be a basic example. Using a Private App token, I can update a contact record using the PATCH /crm/v3/objects/contacts/{contactId} endpoint. A sample payload for updating the city property of the contact:

```lia-code-sample
{
 "properties": {
 "city": "Grand Rapids"
 }
}

```

This will update the city property for that contact. This works fine, however the Latest Source, Latest Source Date, and Latest Source Drill-Down 1 properties do not update. When I check the contact record after updating the record with the above call, you can see these properties not changing, where I would expect Latest Source to be Offline Sources, and Latest Source Drill-Down 1 to be API, per this [Understand Original and Latest traffic source properties](https://knowledge.hubspot.com/contacts/understand-source-properties).

 ![JustinDowty_0-1661790443383.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/5/0/508995c6de9717c3bf8e7fab8554ffb44b555b1b.png)

---

<div class="post-metadata">

**Author:** ![PSomarouthu](https://avatars.discourse-cdn.com/v4/letter/p/46a35a/32.png) [@PSomarouthu](https://community.hubspot.com/u/PSomarouthu)\
**Post date:** [August 20, 2023, 9:21pm UTC](https://community.hubspot.com/t/latest-source-drill-downs-not-updating-for-api-calls/63843/4 "2023-08-20T21:21:38Z")

</div>

Even My latest souce values are set to orignal source value. And after updating them using integration doesn’t change the latest source time.

---

<div class="post-metadata">

**Author:** ![LGuitton](https://avatars.discourse-cdn.com/v4/letter/l/96bed5/32.png) [@LGuitton](https://community.hubspot.com/u/LGuitton)\
**Post date:** [July 31, 2023, 1:12pm UTC](https://community.hubspot.com/t/latest-source-drill-downs-not-updating-for-api-calls/63843/5 "2023-07-31T13:12:44Z")

</div>

Couldn’t make it work either. Here is what I’ve tried:

- make sure I’m updating fields that are not automatically updated by Hubspot [HubSpot's default contact properties](https://knowledge.hubspot.com/contacts/hubspots-default-contact-properties)

- go to the properties settings and find the property slug from the URL: e.g. hs\_latest\_source and hs\_latest\_source\_data\_1

---

<div class="post-metadata">

**Author:** ![PSomarouthu](https://avatars.discourse-cdn.com/v4/letter/p/46a35a/32.png) [@PSomarouthu](https://community.hubspot.com/u/PSomarouthu)\
**Post date:** [August 20, 2023, 9:19pm UTC](https://community.hubspot.com/t/latest-source-drill-downs-not-updating-for-api-calls/63843/6 "2023-08-20T21:19:18Z")

</div>

How did you solve this? I am facing the same now.

---

<div class="post-metadata">

**Author:** ![EDalton6](https://avatars.discourse-cdn.com/v4/letter/e/7ea924/32.png) [@EDalton6](https://community.hubspot.com/u/EDalton6)\
**Post date:** [October 9, 2023, 8:38pm UTC](https://community.hubspot.com/t/latest-source-drill-downs-not-updating-for-api-calls/63843/7 "2023-10-09T20:38:01Z")

</div>

Was there a resolution to this?