APIs & Integrations

DTkach7
Member

Archived parameter does not seem to work for contacts.

I am using a call like this:
```

curl --request POST \
  --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. 
0 Upvotes
2 Replies 2
Jaycee_Lewis
Community Manager
Community Manager

Archived parameter does not seem to work for contacts.

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

 

linkedin

Jaycee Lewis

Developer Community Manager

Community | HubSpot

0 Upvotes
DTkach7
Member

Archived parameter does not seem to work for contacts.

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

0 Upvotes