Hey @alexandra p​! Let me chat with the team who manages our API to get some more information on this for you 👍

Hey @alexandra p​, an update for you here - looks like session count was removed from the contact object in v2 of our API. Working to find out the "why" behind this for you!

Thanks a bunch @eric f11​ ! :)

@eric f11​ Did you get any new info on this? We are working on automating some reports. When exporting the users via the UI we get the session_count attribute in the emailed export.

But there is no way of getting it from the API.

Hey @user963​, we don't plan to reintroduce session count to the API export in future, for now. I would suggest that you continue to work off the CSV export for this data.

I figured I’d bump this thread because the last reply is from three years ago.

Is there any plan to add session_count to the Contact API object? I’ll note that it is available on Visitor in the API, but that seems less useful. It’s honestly a little bit surprising, and disappointing, that this field is not available for contacts.

Any update on this? The field is not available, also there’s no way to automate export users CSV to get around this. Could someone shed some light please?

Is the contact.session_count attribute still not available via API?

Hi ​@Reza Nouri 

Currently we don’t have have this feature in our Road man for this year.

What I can do is reach out to the R&D team and see if they have any plans for this next year.

​@Ebenezer.Laleye Honestly, this sounds like a joke.

4 years ago, your colleague ​@Eric Fitz took 3 months to ‘find out the “why”’ this could not be added, only to give a response that it’s not happening—and now, your response is that this might be on the roadmap for 2026.

This attribute is readily visible in the contacts list in the Intercom UI. It’s available on visitors in the REST API. Surely adding it to the contact object is trivial?

Having access to the attribute in the API would be very useful for integrating with CRM workflows and analysis.

Hey ​@Victor Andrée, Emily here from Support Engineering at Intercom

I completely hear your frustration here, and I really appreciate you taking the time to share the background and additional details. I can see how having this attribute exposed in the API would make a big difference for CRM workflows and analysis.

The best I can do for now is to pass this through as a feature request to our product team. Thanks again for highlighting the use case so clearly and hopefully we can get this implemented in the future as Intercom continues to evolve.