Instagram/v1/tags/{tag-name}/media/recent端点不会在分页块中返回min_tag_id [英] Instagram /v1/tags/{tag-name}/media/recent endpoint doesn't return min_tag_id in pagination block

问题描述

根据 https://www.instagram.com/developer/endpoints/tags/，我们用来在

According to https://www.instagram.com/developer/endpoints/tags/, we used to get the min_tag_id in the pagination part of the https://api.instagram.com/v1/tags/tag-name/media/recent?access_token=ACCESS-TOKEN response which we then used in the request to poll for newer posts.

截至今天早上，我们看到Instagram改变了分页响应的形式.现在看起来像:

As of this morning, we saw that Instagram changed the form of the pagination response. It now looks something like:

"pagination": {
"next_max_tag_id": "AQBy529IMOAlOvp6EI5zrYZRZbUbNW2oGQjgdvfVi5I_7wTIKzqE2nfsSBHvCkPmWOMKV7kmNcMPErenGJsbDtIk013aPZ_xo4vFYuXqtDGz3ZS0ZBrnTSjtuGjtnEOHiDJlAp8lI99AuwAgObnaf6tYhkoiDajEkg5E2zOFuDZFfQ",
"next_url": "https://api.instagram.com/v1/tags/enplug/media/recent?access_token=1573931388.852f6fb.2ee7fb644c5341dd813bd3bbc4c687ec&max_tag_id=AQBy529IMOAlOvp6EI5zrYZRZbUbNW2oGQjgdvfVi5I_7wTIKzqE2nfsSBHvCkPmWOMKV7kmNcMPErenGJsbDtIk013aPZ_xo4vFYuXqtDGz3ZS0ZBrnTSjtuGjtnEOHiDJlAp8lI99AuwAgObnaf6tYhkoiDajEkg5E2zOFuDZFfQ",
"deprecation_warning": "next_max_id and min_id are deprecated for this endpoint; use min_tag_id and max_tag_id instead",
"next_max_id": "AQBy529IMOAlOvp6EI5zrYZRZbUbNW2oGQjgdvfVi5I_7wTIKzqE2nfsSBHvCkPmWOMKV7kmNcMPErenGJsbDtIk013aPZ_xo4vFYuXqtDGz3ZS0ZBrnTSjtuGjtnEOHiDJlAp8lI99AuwAgObnaf6tYhkoiDajEkg5E2zOFuDZFfQ"
}

min_tag_id 是否已弃用?开发人员文档未提及任何内容.

Is min_tag_id now deprecated? The developer docs don't mention anything about this.

推荐答案

似乎这是Instagram API的临时问题，现已解决.

It seems this was a temporary issue with the Instagram API and has now been resolved.

这篇关于Instagram/v1/tags/{tag-name}/media/recent端点不会在分页块中返回min_tag_id的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！