TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Has anyone managed to pass Meta's Access Verification?

24 pointsby hipgrave3 days ago
After spending a few months building out a new project that relies on the Instagram Graph API I&#x27;m struggling to pass Meta&#x27;s Access Verification for Tech Providers.<p>We passed the app verification and business verification fairly easily, but we&#x27;re stuck getting access verification. It feels like Meta is automatically denying us access without telling us explicitly what they are looking for or what we are missing from our answers. We keep getting knocked back with the same reply asking for:<p><pre><code> 1. Add details about how your business will use Platform Data (i.e., any info or data you obtain from us) to enable a product or service on behalf of your clients. 2. Describe how your clients use your product or service. </code></pre> All we really need is to use Instagram OAuth to retrieve the username from the authorised user. My replies have gone into depth explaining this to Meta, including how we use the username (we save it against a user model in our database) and instructions for users to delete their accounts. But nothing seems to be enough.<p>Has anyone had experience with this and can shed some light on what I might be doing wrong?<p>Thanks!

4 comments

vintagedave3 days ago
Upvoting because you&#x27;re struggling with a faceless megacorp.<p>&gt; how we use the username (we save it against a user model in our database)<p>But what are you doing with that data? If I got that explanation, I&#x27;d ask again too. From what you wrote, I have no idea why you use IG, why you even need usernames, and definitely not how they are used after they are saved against other data.
评论 #43896805 未加载
评论 #43896684 未加载
评论 #43897126 未加载
snowwrestler3 days ago
We recently built out a simple web app and eventually just gave up on Login with Facebook. It was by far the most complex and inscrutable process of all the platforms, with at least one step obviously broken. So now when you go to create an account in our app, your options are:<p>- Continue with Google<p>- Continue with Apple<p>- Continue with LinkedIn<p>- Username&#x2F;password<p>My totally uninformed, vibe-based reading of the situation is that Meta no longer prioritizes, or maybe even is actively sunsetting, 3rd party integrations that access any Meta user data.
评论 #43897618 未加载
hariwb3 days ago
Commenting because I went through this maddening and incomprehensible process last year and got rejected a bunch as well. The thing that I <i>believe</i> worked for me was that I completed domain verification via my business manager account (which was also a journey in and of itself). Once that came through, my Tech Provider application was approved within the next day or two.
评论 #43898024 未加载
nikolas-3 days ago
I&#x27;ve previously gone through review for IG basic + messaging permissions, it took several months of constant submissions to get approved. I&#x27;m not sure if their process has changed (got approval ~1 year ago), but we quickly realized Meta&#x27;s entire review team has been outsourced to external contractors that just don&#x27;t care. We&#x27;d get random rejections relating to functionality and check access logs to discover they hadn&#x27;t even opened the app.<p>What ended up working for us was just keeping consistent &amp; simple responses to the usage questions, and whenever we received a rejection with a valid concern, we&#x27;d address it at the top of our existing response with something like &quot;In response to the latest rejection: ...&quot;. Unfortunately it seems unless you get a competent reviewer, you&#x27;re out of luck, so just keep submitting as soon as rejection comes in and eventually you&#x27;ll get through.
评论 #43898196 未加载