What do AmpliFund error codes mean?

AmpliFund uses HTTP response status codes for some of our error messages. 

Code Number	Code Text	Description
100	Continue	This interim response indicates that the client should continue the request or ignore the response if the request is already finished.
102	Processing	This code indicates that the server has received and is processing the request, but no response is available yet.
400	Bad Request	The server cannot or will not process the request due to something that is perceived to be a client error.
401	Unauthorized	The client must authenticate to get the requested response.
403	Forbidden	The client does not have access rights to the content.
404	Not Found	The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist.
405	Method Not Allowed	The request method is known by the server but is not supported by the target resource. For example, an API may not allow calling DELETE to remove a resource.
408	Request Timeout	This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.
409	Conflict	This response is sent when a request conflicts with the current state of the server.
429	Too Many Requests	The user has sent too many requests in a given amount of time ("rate limiting").
500	Internal Server Error	The server has encountered a situation it does not know how to handle.
502	Bad Gateway	This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.
503	Service Unavailable	The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.
504	Gateway Timeout	This error response is given when the server is acting as a gateway and cannot get a response in time.