Take the 2-minute tour ×
Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. It's 100% free, no registration required.

The reputation timeline aggregates activity so that only one instance of each answer or question is returned for a given timeframe. This makes it difficult to tease out reputation awarded for accepted answers because there is no way to know when the answer was accepted.

An optional return value of accepted_date on the answers/{id} call would make my life a little easier.

share|improve this question
    
+1 but there might be a problem - checks can be reversed so maybe they are not tracking when just if. but who knows. and welcome to non-lurker status. –  Sky Sanders Jun 21 '10 at 3:02
    
@code poet- Thank you, it's nice to come out of the shadows ;) I believe there must be tracking of when answers are accepted, because that information is available by clicking the envelope next to your name. On that page, upvotes on an answer are listed separately from rep awarded for an accepted answer, and the time since the answer was accepted is listed as well. –  Dave Swersky Jun 21 '10 at 14:14
add comment

2 Answers

Dave, is this resolved by the timeline_type?

  "timeline_type": {
    "description": "type of event",
    "values": "one of comment, askoranswered, badge, revision, or accepted",
    "optional": true

Lets get a check and a status-complete on this question if so.

share|improve this answer
    
The idea is that if you want to watch in real time for acceptance of a user's answers, the ability to look at a question and see when it was accepted would make the query much simpler. This method would require looking at activity of the questioner. Doable, but would require more queries. –  Dave Swersky Jul 22 '10 at 20:24
    
@dave - ok, now i see where you are going with this, but let me argue with you for a minute: if you are watching in real time, then you know within a minute or so when it was accepted, so that case doesn't support the feature-request, whereas your initial premise of correlation of posts to timeline events might. –  Sky Sanders Jul 22 '10 at 20:29
    
Obviously StackWatcher is the use case here, so: StackWatcher looks for activity and does not keep any local cache (at the moment, I may have to go there.) If I query for activity sorted by date descending, I can get answer accepts along with the other activity. No need for specific queries just for accepts, far fewer queries, and fewer total records returned overall. –  Dave Swersky Jul 22 '10 at 23:06
add comment

I'm not convinced this is needed, nor does it immediately strike me as a bad idea.

So I'm taking the easy way out and putting it on the "consider for subsequent versions" list.

share|improve this answer
add comment

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .