The thing that annoys me is the response. It should return status 201 created and the id of the new resource for future delete/update operations. Instead it returns 200 ok and some clear text. Wouldn’t want to work with such an API.
/serious Well, yes, most APIs are meant for system-to-system interaction, that’s kind of a given. But since this particular API is clearly meant for human-to-system interaction, returning a human-readable response is adequate. Yes, a better design would probably allow the client to specify additional parameters about the desired response.
/back-to-jokes Yeah, well this kind of sums up most of my job applications. I send an application and the recruiting people are all like “OK”.
Here’s an article about it: https://dev.to/maggiecodes_/how-i-applied-to-a-tech-job-using-a-post-request-193d
The thing that annoys me is the response. It should return status 201 created and the id of the new resource for future delete/update operations. Instead it returns 200 ok and some clear text. Wouldn’t want to work with such an API.
/serious Well, yes, most APIs are meant for system-to-system interaction, that’s kind of a given. But since this particular API is clearly meant for human-to-system interaction, returning a human-readable response is adequate. Yes, a better design would probably allow the client to specify additional parameters about the desired response.
/back-to-jokes Yeah, well this kind of sums up most of my job applications. I send an application and the recruiting people are all like “OK”.
At least you do get a response.