deepset Cloud API uses standard HTTP status codes. Here's a summary of the codes most often used.
|Everything worked OK.
|A resource was successfully created or added.
|The request is accepted for processing but the processing is not yet finished.
|The request was successfully processed and is not returning any content. One reason could be the successful deletion of a resource.
|A missing required parameter or wrong syntax.
|An invalid API key was provided.
|A missing or invalid API key.
|The resource doesn't exist.
|The resource can only create content that is unacceptable in the response.
|The server waited too long for the request.
|A resource already exists.
|Check the details in the response. Possible reasons could be that deepset Cloud is missing the required permissions to connect to the infrastructure, a resource is being used, a pipeline wasn't deployed.
|Payload too large.
|The data being uploaded exceeds the size limit. The size limit is 200 MB for files and 32766 bytes for metadata.
|Unsupported media type.
|deepset Cloud doesn't support the format of the data being uploaded. deepset Cloud supports PDF and TXT files and CSV evaluation sets.
|The request was correctly formed but couldn't be processed because of semantic errors.
|The request failed because it depends on another request, which also failed.
|Internal server error.
|The server encountered a situation it doesn't know how to handle.
|Pipeline on standby.
|The pipeline wasn't used for a while and was put on standby to save resources. Wait a while until it's activated and try again.
You can check the full list of codes at MDN docs.