[ad_1]
[ad_2]
It seems that embedding an Instagram feed on a website has become much more complicated.
With a new client I had to jump through all sorts of hoops creating an app, then a test user (why?), approving the test user through the client's account, generating an API key, etc. etc. and it took days to get access and connect a basic feed.
Then with older clients, they are suddenly no longer connected with the content about to be deleted. I try to follow similar steps with the app, test user, key, etc. but can't find it or get the right access.
Is Meta trying to make it extra burdensome to embed Instagram feeds outside of their platform? It used to be easy, but what am I missing now?
I run a small SaaS that solves this exact problem, and I can tell you that working with the Instagram APIs is a huge hassle. Poorly documented, regular bugs and outages, inconsistent errors. And that’s not even getting into the whole app review, business verification and data-use checkup stuff.
They also recently announced the deprecation of the Basic Display API, which means that only professional Instagram accounts will be able to access their own content via API. I think they basically only want their APIs to be used by businesses who might end up being advertising customers.
Yeah, I used to write my own feeds using the Facebook, Twitter, and Instagram APIs. Over the years every single one got so much worse to work with.
Now I just use Smash Balloon products when a client asks for a feed.