Developer documentation for Agave, Abaco, and other TACC APIs

Status Codes

The API uses the following response status codes, as defined in the RFC 2616 on successful and unsuccessful requests.

Success Codes

Response Code Meaning Description
200 Success The request succeeded
201 Created The request succeeded and a new resource was created. Only applicable on PUT and POST actions
202 Accepted The request has been accepted for processing, but the processing has not been completed. Common for all async actions such as job submissions, file transfers, etc
206 Partial Content The server has fulfilled the partial GET request for the resource. This will always be the return status of a request using a Range header
301 Moved Permanently The requested resource has been assigned a new permanent URI. You should follow the Location header, repeating the request
304 Not Modified You requested an action that succeeded, but did not modify the resource

Error Codes

Response Code Meaning Description
400 Bad request Your request was invalid
401 Unauthorized Authentication required, but not provided
403 Forbidden You do not have permission to access the given resource
404 Not found No resource was found at the given URL
405 Method Not Allowed You tried to access a resource with an invalid method
406 Not Acceptable You requested a response format that isn’t supported