{"id":75,"date":"2018-07-14T19:39:57","date_gmt":"2018-07-14T10:39:57","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/%ec%9d%b8%ec%8a%a4%ed%83%80%ea%b7%b8%eb%9e%a8-open-api%ec%9d%98-%ec%97%85%eb%8d%b0%ec%9d%b4%ed%8a%b8%ec%99%80-instagram-graph-api\/"},"modified":"2026-11-15T18:46:49","modified_gmt":"2026-11-15T09:46:49","slug":"instagram-open-api-updates-and-graph-api","status":"publish","type":"post","link":"https:\/\/www.studio-jt.co.kr\/en\/instagram-open-api-updates-and-graph-api\/","title":{"rendered":"Instagram API: Instagram Open API Updates and the Instagram Graph API"},"content":{"rendered":"<p>Instagram is one of the most popular social networks in the world, and pulling Instagram posts into a personal blog or website has become commonplace.<br \/>\nRecently, however, more and more Instagram feed plugins have stopped working and started returning errors. This post explains the cause and what to do about it.<\/p>\n<h2>Where the Change Began<\/h2>\n<p>In March 2018, Facebook had an incident in which the personal data of 50 million people was leaked.<br \/>\nFacebook said the privacy breach happened because user data collected through its &#8220;Open Graph API for developers&#8221; was passed to third-party sites.<br \/>\nOnce the issue became public, Facebook placed strict limits on the use of its public APIs, and Instagram, which Facebook acquired in 2012, also faced major restrictions on API use as a result.<\/p>\n<p><b>* Note: <\/b> As Instagram prepared to launch the &#8220;Instagram Graph API,&#8221; it planned to phase out support for the existing Instagram API Platform gradually. But when the Facebook data leak became a hot topic, it rolled out an emergency patch in April 2018. This post is based on the April update.<\/p>\n<p><b><span>* Note: <\/span><\/b> <span>Information on the Instagram Legacy API end-of-support schedule and the new Basic Display API was added as of February 2020.<\/span><\/p>\n<p><b><span style=\"color: #ff0000;\">* 2020.03.27 update: <\/span><\/b> <span>We&#8217;ve added a <a target=\"_blank\" href=\"\/en\/instagram-graph-api-integration-log\/\" rel=\"noopener\">guide to using Basic Display<\/a>, the new Instagram API!<\/span><\/p>\n<h2>Current Status and Future Plans<\/h2>\n<h3>Instagram Today<\/h3>\n<p>In April 2018, Instagram began an emergency update of its API. The key changes are as follows.<\/p>\n<ul>\n<li>The media request limit dropped from 5,000 to 200 per hour.<\/li>\n<li>The ability to fetch media from public users was removed.<br \/>\n(You can only request media from the account that was issued the access token.)<\/li>\n<li>Media collection based on hashtags and locations was removed.<\/li>\n<\/ul>\n<p>As a result, it is no longer possible to request media from regular users other than the account issued the access token, and with the tight limit of 200 calls per hour, websites began failing to load their Instagram posts properly.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-691321\" src=\"https:\/\/www.studio-jt.co.kr\/wp-content\/uploads\/2018\/07\/unable_instagram_03.jpg\" alt=\"\" width=\"1254\" height=\"946\"><\/p>\n<h3>Instagram&#8217;s Future Plans<\/h3>\n<p>Instagram announced that it would gradually end support for the existing API over three further updates. Starting in July 2018, official support for the existing Instagram API is scheduled to end in the first half of 2020. The detailed update schedule is as follows.<\/p>\n<p><b><del>Update scheduled for July 31, 2018<\/del><\/b><\/p>\n<ul>\n<li><del>The ability to read or modify follower and following lists will be discontinued.<\/del><\/li>\n<li><del>The ability to post or delete comments on public users&#8217; media will be discontinued.<\/del><\/li>\n<\/ul>\n<p><b><del>Update scheduled for December 11, 2018<\/del><\/b><\/p>\n<ul>\n<li><del>The ability to post or delete comments on media will be discontinued entirely.<\/del><\/li>\n<li><del>The ability to load public users&#8217; information and media will be discontinued.<\/del><\/li>\n<li><del>The ability to like or unlike media will be discontinued.<\/del><\/li>\n<li><del>Notifications sent when media is uploaded will be discontinued.<\/del><\/li>\n<li><del><span style=\"color: #ff0000;\">All features for reading public users&#8217; media will be discontinued.<\/span><\/del><\/li>\n<\/ul>\n<p><b><del>Update scheduled for the first half of 2020<\/del><\/b><\/p>\n<ul>\n<li><del>All features for reading users&#8217; profile information and media will be discontinued.<\/del><\/li>\n<li><del><span style=\"color: #ff0000;\">All media requests will be discontinued.<\/span><\/del><\/li>\n<\/ul>\n<p><b><del>Instagram Legacy API support scheduled to end on March 31, 2020<\/del><\/b><\/p>\n<blockquote><p><del>As we previously shared , we will be disabling the final Instagram Legacy API permission (&#8220;Basic&#8221;) on March 31, 2020. As of March 31, 2020, all Legacy API capabilities will be fulfilled by the Instagram Graph API and the Instagram Basic Display API.<\/del><br \/>\n<del>(Support for the Legacy API is scheduled to end on March 31, 2020, and the existing features can be replaced using the new Instagram APIs.)<\/del><\/p><\/blockquote>\n<p><b>Instagram Legacy API support ended on June 29, 2020<\/b><\/p>\n<blockquote><p>The remaining Instagram Legacy API permission (&#8220;Basic Permission&#8221;) was disabled on June 29, 2020. As of June 29, third-party apps no longer have access to the Legacy API.<br \/>\n(The Instagram Legacy API was disabled on June 29, 2020. Since June 29, third-party apps can no longer access the Legacy API.)<\/p><\/blockquote>\n<h2>How to Respond<\/h2>\n<h3>What STUDIO-JT Did<\/h3>\n<p><b>Ending hashtag-based collection<\/b><br \/>\nMany of the websites STUDIO-JT manages collected data based on hashtags, so we replaced all of them with each site&#8217;s official account.<\/p>\n<p><b>Call limit reduced to 200<\/b><br \/>\nTo keep in real-time sync with Instagram, STUDIO-JT used to send a request to the Instagram API every time a user visited a page. Keeping that approach within the new limit of 200 calls was very difficult.<\/p>\n<p>So we moved the work to the server side. Once an hour, the server sends a media request for the designated account and saves the returned data in our own database. The pages users see load media from that database, so they are not affected by the call limit and run smoothly.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-691322\" src=\"https:\/\/www.studio-jt.co.kr\/wp-content\/uploads\/2018\/07\/insta-now.jpg\" alt=\"\" width=\"1254\" height=\"920\"><\/p>\n<h3>STUDIO-JT&#8217;s View<\/h3>\n<p>With Instagram ending support for its Open API in 2020, existing services will need to move to the new Graph API. But that still comes with many problems.<\/p>\n<p><b>Instagram Graph approval process<\/b><br \/>\nTo use the new Instagram Graph API, you must pass Instagram&#8217;s business verification process. However, Instagram does not provide clear access requirements, so getting approval is not easy.<\/p>\n<p><b>Replacing existing API features<\/b><br \/>\nThe public_content endpoint of the old Open API has no replacement, which greatly limits what you can do. (public_content is used to access public posts by tag, location, search and so on.)<\/p>\n<p>We hope the Instagram Graph API will be opened to all developers or that its access requirements will become clear, and we will keep a close eye on future update releases.<\/p>\n<h2>2020 News<\/h2>\n<p>Following Instagram&#8217;s recommendations, STUDIO-JT is migrating the Instagram Legacy API we use to the Instagram Basic Display API.<br \/>\n<del>We&#8217;ll organize the relevant information and share it in a helpful post.<\/del><\/p>\n<p>A guide to using the Instagram Basic Display API has been added!<br \/>\nRead the guide: <a target=\"_blank\" href=\"\/en\/instagram-graph-api-integration-log\/\" rel=\"noopener\">Instagram Basic Display API guide<\/a><a><\/a><\/p>\n<p><a><\/a><\/p>\n<p><a><\/p>\n<h2>References<\/h2>\n<p><\/a><a><\/a><\/p>\n<ul><a><br \/>\n<\/a><\/p>\n<li><a>Instagram update announcement: <\/a><a href=\"https:\/\/developers.facebook.com\/blog\/post\/2018\/01\/30\/instagram-graph-api-updates\/\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/developers.facebook.com\/blog\/post\/2018\/01\/30\/instagram-graph-api-updates\/<\/a><\/li>\n<li>Instagram API changelog: <a href=\"https:\/\/www.instagram.com\/developer\/changelog\/\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/www.instagram.com\/developer\/changelog\/<\/a><\/li>\n<li>Instagram rate limiting information: <a href=\"https:\/\/developers.facebook.com\/docs\/instagram-api\/overview\/#rate-limiting\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/developers.facebook.com\/docs\/instagram-api\/overview\/#rate-limiting<\/a><\/li>\n<li>Instagram official API page: <a href=\"https:\/\/developers.facebook.com\/products\/instagram\/\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/developers.facebook.com\/products\/instagram\/<\/a><\/li>\n<li>Instagram Graph API information: <a href=\"https:\/\/developers.facebook.com\/docs\/instagram-api\/overview\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/developers.facebook.com\/docs\/instagram-api\/overview<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>An overview of the Instagram Open API updates<br \/>\nand the new Instagram Graph API.<\/p>\n","protected":false},"author":1,"featured_media":146,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[13],"class_list":["post-75","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dev"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/posts\/75","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/comments?post=75"}],"version-history":[{"count":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/posts\/75\/revisions"}],"predecessor-version":[{"id":2275,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/posts\/75\/revisions\/2275"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media\/146"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=75"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/categories?post=75"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}