The one thing you don’t want clients doing is “hard coding” any expectations of what APIs are synchronous and what APIs are asynchronous. In other words, someone writing to the enStratus API should not think “the POST Server API is asynchronous, but the POST Firewall API is synchronous”. They should instead build their clients to look at the status code returned from the POST. If it is a 202, the client should expect a Job resource in the body representing an asynchronous operation. If it is a 201 (Created), the client should look for identifying information about the created object in the
...more
