Is There A Way To Identify Core Features via the API?
I'm trying to use the API to export some data on core feature usage into R for some further analysis. So far, I've figured out how to make a call that gets the data I want for a specific featureId, but there doesn't seem to be a way to identify what those relevant featureIds would be from a call to the features endpoint, i.e.:
GET https://app.pendo.io/api/v1/feature
I could manually maintain a list of the featureIds for our core events, but that seems extremely brittle, as any time we add/remove a core event that list would need to be manually updated.
Ideally, I'd like to be able to hit the above endpoint, identify and filter the results to the core events, and then use the ids from that response to make my other calls. Given how prominent the "Core" tagging is on the front end I assumed it would be a flag I'd have access to in the API but if it's there it's not jumping out at me. I suppose I could do a sort of workaround by reserving a specific color for core events, but that feels a bit hacky and could interfere with how others in my company are using them.
Am I missing something? Is there a better approach to what I'm trying to do?
Cheers.
コメント
Hi Ben Parker,
Yes there is a way to identify Core Features using API. You would do an aggregation of features but filter on a property called "isCoreEvent. You can make a query that returns a list of features where
isCoreEvent
istrue.
Please remember that core events are app specific.
I don't see the `isCoreEvent` property on the documentation for features, and it doesn't appear to be coming back on any of my calls either.

The feature documentation I'm looking at: https://developers.pendo.io/docs/?bash#the-feature-object
A screenshot just in case:
What do you mean by app specific? We are currently only running Pendo on one web app right now, so that shouldn't make a difference? Unless I need to modify how I'm making the API call in order to get that field to appear? If that's the case, how do I go about doing that?
Upon closer inspection, the isCoreEvent property is being returned when I hit the features endpoint, but something was going wonky in the R that was parsing it.
Still, it would be helpful if the online documentation showed that it existed.
Hi Ben,
Great to hear that this is working for you, and yes I will work with the documentation team to have this clearer about the Core Events property.
I only mention that core events are app specific in the case that you have a multi-app subscription and may have different number of Core Events identified for different app subscriptions. Hope this helps and glad you are able to use the isCoreEvent property.
サインインしてコメントを残してください。