Hey @user929, if you use the operator "=" with the contact_ids parameter, it will only return conversations that only include that contact_id and no others.
If you want to return all conversations that contain at least one instance of that contact_id, you'll need to use the operator "~".
You can read more about the operators that you can use with our API here.
Hey Eric, thanks for responding. Unfortunately, my problem seems to be unrelated to that. Apologies if my earlier post was unclear.
Like I mentioned, I have two types of conversations with a specific user: those initiated by our team via the Intercom UI and those initiated by the user and created via the API.
Both types of conversations include the correct contact_id – they are all associated with the specific user. When I retrieve each conversation via the `conversations/id` endpoint, I can clearly see that each conversation is associated with the user and that the conversation is marked as open.
Unfortunately, when I POST against `conversations/search` with the `contact_ids` value set to the relevant Intercom user id and the filter set to either `=` or `IN`, only the conversations initiated by the user and created via the API are returned. No conversations created by our team are returned.
The issue seems to be that conversations opened by our team aren't returned by the `conversations/search` endpoint despite being associated with the relevant `contact_id`
Setting the value to the Intercom user id and the filter to `~` doesn't seem to work, either.
If you have any further suggestions or need more information, let me know.
Hello @user929 , I will jump into this conversation, You are right, this is how Intercom's API are working.
It's not possible to retrieve admin initiated conversations via search API.
To retrieve admin initiated conversations, best way will be to save Conversation Id's in database *During creation) and then retrieve via API:
https://api.intercom.io/conversations/ID
You can also get list of admin initiated conversations by using export API, more information can be found here.