We’re currently using the /conversations and /questions endpoints for some automations. The drawback of these endpoints is that they’re very basic in that they return all entries of their respective type. Today I’m looking at using the /topics endpoint instead and this is promising as it does indeed allow to grab topics created between a specific date range (perfect), however, the resulting data is missing key properties that the other endpoints have, that we currently use. For example, seoCommunityUrl, pinnedReplyId, and answer.
It would be helpful to align the result properties of the /topics endpoint with the properties of the /conversations and /questions endpoints.
