# Filtering object properties with python client API

**URL:** <https://community.hubspot.com/t/filtering-object-properties-with-python-client-api/125448>\
**Category:** APIs & Integrations\
**Tags:** python, companies, professional\
**Created:** [February 5, 2025, 11:28am UTC](https://community.hubspot.com/t/filtering-object-properties-with-python-client-api/125448 "2025-02-05T11:28:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![NRIO](https://avatars.discourse-cdn.com/v4/letter/n/57b2e6/32.png) [@NRIO](https://community.hubspot.com/u/NRIO)\
**Post date:** [February 5, 2025, 11:28am UTC](https://community.hubspot.com/t/filtering-object-properties-with-python-client-api/125448/1 "2025-02-05T11:28:34Z")

</div>

I need to retrieve company properties through the API in a python script. I want to filter the results and only get the following properties : name,fieldType,createdAt,updatedAt

When I test on the API doc website with my private app token, everything works well and I only get the requested properties :

 ![api-doc.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/7/7eda67e8c170d2fcc2e31d2ff12fcbb3f2cf286d.png)  
the result when using the doc (works)

But when I copy-paste the code in my editor and run it, the filter doesn’t work.

 ![properties.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/f/d/fda4cb7606834133eb07c4b5373c8b588cc9320e.png)  
the result in my code (doesn’t work)

Since the code ad the API are the same, I suspect it might come from a difference in the library used locally and on the website?

For reference, I use version hubspot package 0.1.14.dev0 and hubspot-api-client 11.1.0.

Also, when I used cURL and used the following URL, it works well : [https://api.hubapi.com/crm/v3/properties/company?archived=false&properties=name,fieldType,createdAt,updatedAt](https://api.hubapi.com/crm/v3/properties/company?archived=false&properties=name,fieldType,createdAt,updatedAt)

Has anyone else experienced this?

---

<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:** [February 5, 2025, 10:00pm UTC](https://community.hubspot.com/t/filtering-object-properties-with-python-client-api/125448/2 "2025-02-05T22:00:58Z")

</div>

Hi, @NRIO 👋 Thanks for posting, Welcome to our community! I’d like to ask a few of our community champions if they have any troubleshooting suggestions — hey @SteveHTM @ChrisoKlepke, do you have any Python wisdom you can share with @NRIO?

Thank you very much for taking a look! — Jaycee

---

<div class="post-metadata">

**Author:** ![SteveHTM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stevehtm/32/22074_2.png) [@SteveHTM](https://community.hubspot.com/u/SteveHTM)\
**Post date:** [February 6, 2025, 3:14am UTC](https://community.hubspot.com/t/filtering-object-properties-with-python-client-api/125448/3 "2025-02-06T03:14:27Z")

</div>

@NRIO - I suspect that you are correct in identifying a potential difference in the HubSpot library use here. For my own sanity, I typically use the “bare metal” request/response calls where the actual URL being used in the base API call is front and center rather than being obscured by a layer of API code.

I can definitely vouch that the base API call itself works to specifically return the requested properties.

Hope this helps,

Steve