Facebook's API used to return 200s for everything!
Sometimes the focus on the API isn't on semantics, but just volume of data, or they're just very opinionated about how they want to surface errors to users (not semantically)
I do like a semantic API. Most of our APIs are semantic now, but some legacy ones return 200s with error codes, while we're working to phase them out.
Wow, I didn't know that since I haven't used Facebook API before. Maybe this phenomenon takes a big part in influencing these peoples 😮
Yes, legacy ones should make sense if it still likes that. But in my experience of working in a small to medium companies level in my country, I still find they use 200 OK everywhere.
If there is anyone who follows the standardized HTTP responses around me, I would be impressed.
Facebook's API used to return 200s for everything!
Sometimes the focus on the API isn't on semantics, but just volume of data, or they're just very opinionated about how they want to surface errors to users (not semantically)
I do like a semantic API. Most of our APIs are semantic now, but some legacy ones return 200s with error codes, while we're working to phase them out.
Wow, I didn't know that since I haven't used Facebook API before. Maybe this phenomenon takes a big part in influencing these peoples 😮
Yes, legacy ones should make sense if it still likes that. But in my experience of working in a small to medium companies level in my country, I still find they use
200 OKeverywhere.If there is anyone who follows the standardized HTTP responses around me, I would be impressed.
When I used to architect and build APIs, I'd follow the Richardson Maturity Model: martinfowler.com/articles/richards...