# Archived parameter does not seem to work for contacts.

**URL:** <https://community.hubspot.com/t/archived-parameter-does-not-seem-to-work-for-contacts/82275>\
**Category:** APIs & Integrations\
**Tags:** contacts\
**Created:** [May 30, 2023, 4:21pm UTC](https://community.hubspot.com/t/archived-parameter-does-not-seem-to-work-for-contacts/82275 "2023-05-30T16:21:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![DTkach7](https://avatars.discourse-cdn.com/v4/letter/d/8edcca/32.png) [@DTkach7](https://community.hubspot.com/u/DTkach7)\
**Post date:** [May 30, 2023, 4:21pm UTC](https://community.hubspot.com/t/archived-parameter-does-not-seem-to-work-for-contacts/82275/1 "2023-05-30T16:21:25Z")

</div>

I am using a call like this:  
```

curl --request POST \

--url ‘[https://api.hubapi.com/crm/v3/objects/contacts/batch/read?archived=true](https://api.hubapi.com/crm/v3/objects/contacts/batch/read?archived=true)’ \

--data ‘{ “inputs”: [“12345”, “2501”] }’  
```  
The first id is bogus, and gets returned as `errors[].context.ids[]` as expected. However the other id is \_real\_, that contact does exist, and is \_not\_ archived. That data for that contact is returned in `results[]` despite the `?archived=true` parameter in the url, which is supposed to only return objects that are archived. It does work correctly for companies (returns only archived companies when archived=true), but for contacts, `?archived=true` in the url seems to make no difference - it always returns everything.

---

<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:** [May 31, 2023, 7:56pm UTC](https://community.hubspot.com/t/archived-parameter-does-not-seem-to-work-for-contacts/82275/2 "2023-05-31T19:56:03Z")

</div>

Hey, @DTkach7 👋 Thanks for flagging this. I’ll attempt to reproduce the issue on my end.

To verify my understanding, is this the gist of what you’re doing?

- Make a simple request and include ?archived=true as part of your query param
- Include a Contact ID that is active and **not** archived

Expecting — to not have the active contact returned

Experiencing — having the active contact returned in your response

Does that sound about right?

Thank you! — Jaycee

---

<div class="post-metadata">

**Author:** ![DTkach7](https://avatars.discourse-cdn.com/v4/letter/d/8edcca/32.png) [@DTkach7](https://community.hubspot.com/u/DTkach7)\
**Post date:** [May 31, 2023, 10:17pm UTC](https://community.hubspot.com/t/archived-parameter-does-not-seem-to-work-for-contacts/82275/3 "2023-05-31T22:17:20Z")

</div>

Yes, active is returned as `results`, and archived as `errors`, same as if `archived` parameter was not included.

---

<div class="post-metadata">

**Author:** ![CraigBosco](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@CraigBosco](https://community.hubspot.com/u/CraigBosco)\
**Post date:** [May 1, 2025, 3:05pm UTC](https://community.hubspot.com/t/archived-parameter-does-not-seem-to-work-for-contacts/82275/4 "2025-05-01T15:05:36Z")

</div>

Can we get an update on this? I am experiencing the same thing.