# HubSpot Import API

**URL:** <https://community.hubspot.com/t/hubspot-import-api/136151>\
**Category:** APIs & Integrations\
**Tags:** starter\
**Created:** [July 14, 2025, 7:36am UTC](https://community.hubspot.com/t/hubspot-import-api/136151 "2025-07-14T07:36:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rakesh1003-dax](https://avatars.discourse-cdn.com/v4/letter/r/f4b2a3/32.png) [@rakesh1003-dax](https://community.hubspot.com/u/rakesh1003-dax)\
**Post date:** [July 14, 2025, 7:36am UTC](https://community.hubspot.com/t/hubspot-import-api/136151/1 "2025-07-14T07:36:10Z")

</div>

Hi everyone,

I’m using the **HubSpot Import API** to import Contacts and Companies into our HubSpot account. Everything works smoothly, but I’ve encountered an issue with tracking/filtering the imported records.

In the import JSON payload, I specify a name, and I noticed that this value gets mapped to the property **“Original Source Drill-Down 2”** on both Contacts and Companies. However, this property **cannot be used** to filter records in **Views** , **Lists** , **Reports** , or **Workflows** , which limits its usefulness.

 ![rakesh1003dax_0-1752478512049.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/5/c/5c794c489e93bed7e83b83345b57eb34539c0fba.png)

### My Question:

**Which contact or company property should I use (or populate) to reliably filter or segment the records that were imported using the Import API?**

I want to be able to:

- Create views or lists that show only records imported by the API
- Use this in workflows and reporting as a filter

Has anyone found a good workaround for this, like tagging imported records via a custom property during import, or is there a recommended way from HubSpot?

Thanks in advance for your help!

---

<div class="post-metadata">

**Author:** ![BrandonWoodruff](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/brandonwoodruff/32/61045_2.png) [@BrandonWoodruff](https://community.hubspot.com/u/BrandonWoodruff)\
**Post date:** [July 14, 2025, 1:19pm UTC](https://community.hubspot.com/t/hubspot-import-api/136151/2 "2025-07-14T13:19:24Z")

</div>

Hey there! Great question — and you’re absolutely right: the Import API writes the import name to **Original Source Drill-Down 2** , but that property is **read-only and not filterable** in Lists, Views, Workflows, or Reports. Frustrating, I know.

### Recommended Solution:

**Use a custom property as a tagging mechanism** during the import process. Here’s how:

* * *

### How to implement:

1. **Create a custom property** in HubSpot:

2. **In your import JSON payload** , include that custom property and populate it with a unique value (e.g., “api-import-july2025”).

Example snippet for a Contact record:

{ “properties”: { “firstname”: “John”, “lastname”: “Doe”, “email”: “[john.doe@example.com](mailto:john.doe@example.com)”, “import\_source”: “api-import-july2025” } }

1. **Now you can filter** :

---

<div class="post-metadata">

**Author:** ![rakesh1003-dax](https://avatars.discourse-cdn.com/v4/letter/r/f4b2a3/32.png) [@rakesh1003-dax](https://community.hubspot.com/u/rakesh1003-dax)\
**Post date:** [July 15, 2025, 4:00am UTC](https://community.hubspot.com/t/hubspot-import-api/136151/3 "2025-07-15T04:00:08Z")

</div>

Thank you, @BrandonWoodruff, for your response. Yes, your solution works; however, I’m building a solution to import data from my product into multiple HubSpot accounts of my product customers.  
Creating a custom property for each account isn’t the ideal approach for my use case. I was looking for properties that already exist in HubSpot.

I’m considering using the following existing properties:

- **For the Contact object:** Membership Notes (hs\_content\_membership\_notes)
- **For the Company object:** Description (description)

Let me know if you see any concerns with using these.