Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to query contact id when contact is archived? #333

Open
ryan-kim-siteminder opened this issue Dec 7, 2022 · 3 comments
Open

How to query contact id when contact is archived? #333

ryan-kim-siteminder opened this issue Dec 7, 2022 · 3 comments

Comments

@ryan-kim-siteminder
Copy link

ryan-kim-siteminder commented Dec 7, 2022

To delete archived contact permanently, we need to use contact id but it seems to me that there is no way we can retrieve contact id if contact is archived. Is there any way I can retrieve contact id to use it as a parameter for deleting contact permanently? FYI, this requirement is part of PII(Personal Identifiable Information) initiative.

Version info

  • version: v3.1.4

Expected behavior

There should be a way to retrieve contact id for archived user. So archived users can be deleted permanently.

Actual behavior

I want to use email to search contact id for archived user but intercom api client does not provide that.
Tried to unarchive contact to get the contact id but to no avail because to unarchive contact it needs contact id.

@SeanHealy33
Copy link
Contributor

Hi Ryan

The api does not support listing archived contacts sadly the only way to get them is to have the id handy.

I've raised a bug to the feature team and I'll update this as I get more info

@liampulles
Copy link

Any updates on this? I'm also trying to query for the id of an archived contact in order to unarchive them.

@marcuswurster
Copy link

@SeanHealy33 We currently run into the same issue and would love to see an update here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants