Out-of-time API / Search / Endpoint API Results

Question

I am currently using the Instagram API interface / endpoint using the following sample configuration:

curl -XGET 'https://api.instagram.com/v1/media/search? lat=1.3058866783157643&lng=103.88191223144531&distance=5000& min_timestamp=1394615197&max_timestamp=1394615227& access_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' 

Highlights of this team:

• min_timestamp = 1394615197
• max_timestamp = 1394615227

The results I got have the following created_time fields: (I did not set the original result because it will consume a lot of space. I use jq ( http://stedolan.imtqy.com/jq/ ) to extract the created_time field).

• "1394615279" * external tag parameters
• "1394615277" *
• "1394615270" *
• "1394615268" *
• "1394615251" *
• "1394615248" *
• "1394615246" *
• "1394615243" *
• "1394615241" *
• "1394615239" *
• "1394615232" *
• "1394615217"
• "1394615214"
• "1394615204" *
• "1394615204" *
• "1394615187" *
• "1394615180" *
• "1394615180" *
• "1394615179" *
• "1394615178" *

As you can see, there are results (I put an asterisk) that are created outside the timestamp parameters that I use. So, is this the expected behavior of the media search API? Or is it because something is wrong with my timestamp parameter (the range is too close, maybe note that the difference between the maximum and minimum timestamp is only 30 seconds).

Answer 1

I believe Instagram rounds up time limits to the nearest minute. Min rounding And max. Thus, the time ranges in your request span two minutes. So your query window is actually 120 seconds. You will have to filter out additional features yourself.

Keep in mind that a media search will return a maximum of 20 results. Thus, you can split this query into two separate queries for each of the 60 second windows that it covers. I do not think that media search results use pagination to display additional results. That way, you really don't know how much data you are losing.