Successfully created a new allocation.

This usually occurs because of a missing or malformed parameter. Check the documentation and the syntax of your request and try again.

A valid authentication token was not provided with the request, so the API could not associate a user with the request.

The request was valid, but the queried object or object mutation specified in the request is above your current premium level.

The authentication and request syntax was valid but the server is refusing to complete the request. This can happen if you try to read or write to objects or properties that the user does not have access to.

Either the request method and path supplied do not specify a known action in the API, or the object specified by the request does not exist.

There was a problem on Asana’s end. In the event of a server error the response body should contain an error phrase. These phrases can be used by Asana support to quickly look up the incident that caused the server error. Some errors are due to server load, and will not supply an error phrase.