Skip to main content
The user’s matched event history, newest first. One call backs both the events tab and the event detail screen.

Request

Response

Reading it

  • Newest first, cursor-paginated. total is the user’s full matched-event count and may be omitted on later pages; page with has_more and next_cursor, not with total.
  • media is included and complete, so opening an event detail screen costs no extra request. It is not capped; a heavy event can carry hundreds of entries, so pass include_media=false on views that do not need it. Each entry echoes the thumbnail_url you submitted, when you submitted one.
  • media_id echoes the id you originally submitted, so you can resolve each one back to the local asset on the device. FanFeed stores metadata only; it does not host the images. Rendering a photo means loading it from the user’s own camera roll by that id.
Two things are filtered out of this list and will not appear:
  • Hidden events. An event hidden from a profile disappears from these responses. If an event vanishes between pages or syncs, this is usually why.
  • Events not licensed for redistribution. As in The response: the photos still exist, but the event is never returned.