Beginning Friday evening (US time), a critical endpoint in this API has broken. The endpoint creates long-lived access tokens, so it is in the critical path for almost any company using the API.
I find it disappointing that a leading technological company does not acknowledge a bug that's been reported to them several times more than 24 hours ago, even if to say that's it's being investigated.
The endpoint: https://developers.facebook.com/docs/instagram-basic-display-api/guides/long-lived-access-tokens#get-a-long-lived-token
Currently the API returns a Bad Request with a wrong error message (the endpoint should support "GET"): ``` { "message": "Unsupported request - method type: get", "type": "IGApiException", "code": 100, "fbtrace_id": "AuDYqK74IrT9Yt2Sx51UlP6" } ```
I have opened a bug report but received no response. Facebook's status page shows all green in the API section: https://metastatus.com/ There are several Meta Developers Community threads with no response
Hopefully not their entire product. The first rule is don't build your company on the back of another, but I think the most important part is that if you do use another company, make sure you're fine if they disappear one day.
The last time Facebook made major changes (ostensibly as a response to the Cambridge Analytica stuff, but that was just an excuse) a bunch of people got burned.
My company did too but we always kept ourselves in a place where if it vanished we'd be - at worst - inconvenienced.
This approach came because early on I was burned by Twitter changes that were more impactful.
Most recent Twitter changes prove that even paying for access provides no guarantees.
I did cage it by saying make sure your whole company doesn't collapse if one API gets shut down.
"Free market for thee, but not for me" is not a strong argument in any context.
By now I feel like it’s better to build on top of an API, be aware that it might go away one day but make money while it lasts, which can be many years.
I do not understand how the idea of not building a company on the back of another is possible. We rely on other companies for deployments, hosting, reporting, monitoring, payments, billing and security etc. Some may be less critical than others but how can you avoid your reliance on other companies at all?
If your payment provider stops offering payments, it’s annoying but not existential. If your whole business is reselling a single artist and they die or switch to a different gallery, you’re done.
What's the over-under on # of companies built on AWS?
OP - is there a way to contact you? Drop me a DM on ig Instagram.com/i386 I may be able to help with a workaround
I don't mind it though, long term that's good news as it'll let us remove any dependencies we have on FB.
Easier to tell a developer they’re crazy and their code was wrong than to admit to downtime and violate any SLAs.
You cut non-essential folks firstly and critical operational personnel lastly.
As long as the GET requests returns the same or equivalent API data every time they make total sense. For an access token, that's perfectly fine, assuming they don't generate a new token with every request of course.
If your users are professional/business you should be using the graph API - this is much better supported/tested. To me the display/basic API feels like something that isn’t that integral to FB and could be dropped at any time.
https://developers.facebook.com/support/bugs/743806503999661
Will you people ever learn.
Don't build on platforms, build on protocols.
