Final Reminder: Instagram Legacy API Platform will be disabled on March 31, 2020
March 30, 2020 Update: We understand these are challenging times for our developer community, so we are postponing disabling the Instagram Legacy API Platform by 90 days to June 29, 2020. Remaining endpoints on the Legacy API will no longer be available after this date and your app’s users may lose functionality. We urge you to migrate to the Instagram Basic Display API without delay so that Instagram users of your app have time to transition as well. Please see below for tips on getting through our App Review process.
As we previously shared, we’d like to remind you that the final Instagram Legacy API permission (“Basic Permission”) will be disabled on March 31, 2020. Any apps that remain on the Legacy API as of March 31 will no longer have access. As of March 31, developers previously using the Legacy API should instead rely on Instagram Basic Display API and Instagram Graph API.
Migrating off the Legacy API
To avoid disruption of service to your app and business, please apply for permissions to Basic Display API via App Review and migrate Legacy API calls before March 31. Note that App Review submissions can take up to a week or longer to process. Check our developer documentation for Basic Display API and App Review to learn more.
App Review Tips
Please take a moment to review some common mistakes we’ve seen in App Review submissions for Basic Display API that can lead to rejection:
Mistake #1: Your app uses Basic Display API for authenticating users
Instagram Basic Display API is not an authentication tool and cannot be used to authenticate or log users into your app.
Tips
- Make sure your app provides a login option that does not use Basic Display API, such as your own in-house login flow or Facebook Login. If implementing Facebook Login, refer to this sample App Review submission for guidance.
- Show the user a button to connect their Instagram account only after the user has logged into your app.
- Ensure your app clearly shows that the authorization process has been completed, such as displaying the Instagram account’s username or media within your app.
Mistake #2: Your App Review submission does not clearly demonstrate your use case
Your submission will be rejected if it does not clearly show how your app uses the requested permissions.
Tip
- Make sure the video screencast you submit in the App Review submission is clear, detailed, and easy to follow so that our App Reviewers are able to reproduce your use case. For guidance, refer to our best practices for recording a screencast.
For more tips and tools, please refer to our App Review Rejection Results Guide, Common App Review Rejection Reasons, and Developer Tools page.
Note
If you’re using the Legacy API to simply display your personal Instagram Feed on your personal website, you may use the User Token Generator on the Instagram Basic Display API. The User Token Generator does not require App Review, but it will only work for your owned Instagram accounts (i.e. accounts for which you know the login credentials). Please refer to the User Token Generator developer documentation to learn more.
As always, thank you for being part of our developer ecosystem and helping make Instagram a vibrant community for people, businesses, and creators.
Updating Special Ad Audiences for housing, employment, and credit advertisers

On June 21, 2022 we announced an important settlement with the US Department of Housing and Urban Development (HUD) that will change the way we deliver housing ads to people residing in the US. Specifically, we are building into our ads system a method designed to make sure the audience that ends up seeing a housing ad more closely reflects the eligible targeted audience for that ad.
As part of this agreement, we will also be sunsetting Special Ad Audiences, a tool that lets advertisers expand their audiences for ad sets related to housing. We are choosing to sunset this for employment and credit ads as well. In 2019, in addition to eliminating certain targeting options for housing, employment and credit ads, we introduced Special Ad Audiences as an alternative to Lookalike Audiences. But the field of fairness in machine learning is a dynamic and evolving one, and Special Ad Audiences was an early way to address concerns. Now, our focus will move to new approaches to improve fairness, including the method previously announced.
What’s happening: We’re removing the ability to create Special Ad Audiences via Ads Manager beginning on August 25, 2022.
Beginning October 12th, 2022, we will pause any remaining ad sets that contain Special Ad Audiences. These ad sets may be restarted once advertisers have removed any and all Special Ad Audiences from those ad sets. We are providing a two month window between preventing new Special Ad Audiences and pausing existing Special Ad Audiences to enable advertisers the time to adjust budgets and strategies as needed.
For more details, please visit our Newsroom post.
Impact to Advertisers using Marketing API on September 13, 2022
For advertisers and partners using the API listed below, the blocking of new Special Ad Audience creation will present a breaking change on all versions. Beginning August 15, 2022, developers can start to implement the code changes, and will have until September 13, 2022, when the non-versioning change occurs and prior values are deprecated. Refer below to the list of impacted endpoints related to this deprecation:
For reading audience:
- endpoint gr:get:AdAccount/customaudiences
- field operation_status
For adset creation:
- endpoint gr:post:AdAccount/adsets
- field subtype
For adset editing:
- endpoint gr:post:AdCampaign
- field subtype
For custom audience creation:
- endpoint gr:post:AdAccount/customaudiences
- field subtype
For custom audience editing:
- endpoint gr:post:CustomAudience
Please refer to the developer documentation for further details to support code implementation.
First seen at developers.facebook.com
Introducing an Update to the Data Protection Assessment

Over the coming year, some apps with access to certain types of user data on our platforms will be required to complete the annual Data Protection Assessment. We have made a number of improvements to this process since our launch last year, when we introduced our first iteration of the assessment.
The updated Data Protection Assessment will include a new developer experience that is enhanced through streamlined communications, direct support, and clear status updates. Today, we’re sharing what you can expect from these new updates and how you can best prepare for completing this important privacy requirement if your app is within scope.
If your app is in scope for the Data Protection Assessment, and you’re an app admin, you’ll receive an email and a message in your app’s Alert Inbox when it’s time to complete the annual assessment. You and your team of experts will then have 60 calendar days to complete the assessment. We’ve built a new platform that enhances the user experience of completing the Data Protection Assessment. These updates to the platform are based on learnings over the past year from our partnership with the developer community. When completing the assessment, you can expect:
- Streamlined communication: All communications and required actions will be through the My Apps page. You’ll be notified of pending communications requiring your response via your Alerts Inbox, email, and notifications in the My Apps page.
Note: Other programs may still communicate with you through the App Contact Email.
- Available support: Ability to engage with Meta teams via the Support tool to seek clarification on the questions within the Data Protection Assessment prior to submission and help with any requests for more info, or to resolve violations.
Note: To access this feature, you will need to add the app and app admins to your Business Manager. Please refer to those links for step-by-step guides.
- Clear status updates: Easy to understand status and timeline indicators throughout the process in the App Dashboard, App Settings, and My Apps page.
- Straightforward reviewer follow-ups: Streamlined experience for any follow-ups from our reviewers, all via developers.facebook.com.
We’ve included a brief video that provides a walkthrough of the experience you’ll have with the Data Protection Assessment:
Something Went Wrong
We’re having trouble playing this video.
The Data Protection Assessment elevates the importance of data security and helps gain the trust of the billions of people who use our products and services around the world. That’s why we are committed to providing a seamless experience for our partners as you complete this important privacy requirement.
Here is what you can do now to prepare for the assessment:
- Make sure you are reachable: Update your developer or business account contact email and notification settings.
- Review the questions in the Data Protection Assessment and engage with your teams on how best to answer these questions. You may have to enlist the help of your legal and information security points of contact to answer some parts of the assessment.
- Review Meta Platform Terms and our Developer Policies.
We know that when people choose to share their data, we’re able to work with the developer community to safely deliver rich and relevant experiences that create value for people and businesses. It’s a privilege we share when people grant us access to their data, and it’s imperative that we protect that data in order to maintain and build upon their trust. This is why the Data Protection Assessment focuses on data use, data sharing and data security.
Data privacy is challenging and complex, and we’re dedicated to continuously improving the processes to safeguard user privacy on our platform. Thank you for partnering with us as we continue to build a safer, more sustainable platform.
First seen at developers.facebook.com
Resources for Completing App Store Data Practice Questionnaires for Apps That Include the Facebook or Audience Network SDK

Resources for Completing App Store Data Practice Questionnaires for Apps That Include the Facebook or Audience Network SDK
First seen at developers.facebook.com
-
OTHER2 weeks ago
Meta Said to Curtail Election Misinformation Efforts as US Midterm Vote Approaches: Details
-
OTHER2 weeks ago
WhatsApp Working on Login Approval Feature to Improve Account Security: Report
-
OTHER1 week ago
Twitter Down? Company Responds as Thousands of Users Report Issues With Accessing Twitter
-
OTHER1 week ago
Facebook Parent Meta Raises $10 Billion in Its First-Ever Bond Offering
-
Uncategorized1 week ago
What are KOLs in Marketing? (And How to Work With Them)
-
OTHER2 weeks ago
Elon Musk Could Struggle with Banks, His Twitter Deal Escape Hatch, Experts Say
-
OTHER1 week ago
WhatsApp Users to Get Ability to Control Online Presence, Leave Groups Silently, and More: All Details
-
OTHER1 week ago
Elon Musk Sells Tesla Shares Worth $6.9 Billion to Avoid Twitter Fire Sale