From 893b32007078cc6197f2c66ce0588c1a2a8c44dd Mon Sep 17 00:00:00 2001 From: Zak Wilcox Date: Tue, 20 Jan 2015 17:19:56 +0000 Subject: [PATCH] Explicitly say event order is newest-first That's what I've observed, and it helps to know you can avoid a defensive sort. --- content/v3/activity/events.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/v3/activity/events.md b/content/v3/activity/events.md index d038c63d23..8753cf2a85 100644 --- a/content/v3/activity/events.md +++ b/content/v3/activity/events.md @@ -31,6 +31,8 @@ Events support [pagination](/v3/#pagination), however the `per_page` option is unsupported. The fixed page size is 30 items. Fetching up to ten pages is supported, for a total of 300 events. +Events are always returned in newest-first order. + Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).