Application API Photos photos latest

#/photos/latest [POST]

Return “search results” based on recently-approved photos - protected.

Parameters

• member_type (string) [optional] - should be "all", "connections", or "matches"; if omitted, defaults to "all"
• new_since (int) [optional] - number of days back to look for new photos; if omitted, defaults to 7; maximum value is 7

In addition, standard pagination and sorting options are available as for all searches (note that sorting is based on profile information, not on the recency of the photos):

• page (numeric) [optional: default 1] - in conjunction with pagesize, returns next set of results
• pagesize (numeric) [optional: default 15] - the number of results to return per page
• sortby (string) [optional: default "latest"] - can also be "age", "activity" (based on last login in descending order), "newest" (based on registration date in descending order), or "username"; for legacy compatibility, "activitydate" is accepted as an alias for "activity" and "likesdate" is accepted as an alias for "latest"

Response Messages

200 OK - success

The result contains the following fields:

• users - an array of user status information for members that had recently-approved photos and matched basic search criteria (such as gender/preference etc); each row will have a "new_photo" element representing a recently-approved photo with the same structure as the "photo" element (which will be the member’s primary photo, if any):

{
  "users" : [
    { user status information },
    { user status information },
    ...
  ]
}

Note: it is possible (but very unlikely) that some status information rows may be missing the "new_photo" element – fallback to the "photo" element in those cases (the primary photo).