Create Case
POST/cases
Opens a new support case.
The case must identify the equipment concerned, either by its serial number or by its service identifier. It must also carry the contract covering that equipment, your own case reference, a severity and a description of the problem.
Send the case on its own as JSON, or use the multipart form to open the case and attach a first file in a single call. A file sent this way ends up in the shared folder for the case, exactly as it would through the attachment endpoint.
When the multipart form is used and the case is created but the file cannot be stored, the
response is a 207 carrying the case number and a warning: the case exists and the file can
be attached again afterwards.
Request
Responses
- 201
- 207
- 400
- 500
The case has been opened.
The case has been opened, but something secondary to it did not go through. The case number
is valid in every case, and the warning says what to do about the rest.
Three situations produce it. The file sent with the case could not be stored, and can be attached again with a separate call. Or the name given to that file is not one we can store, in which case rename it and send it again. Or the equipment named in the request could not be attached to the case, because the serial number given is currently covered for another customer — the case is open on your service and our teams have been notified, so there is nothing to retry on that one.
Whether the file made it is told by id, not by the status: a 207 carrying an id means the
file is stored and the warning is about something else.
Both can happen on the same call, in which case warning carries the two messages one after
the other. Read it in full rather than matching on its beginning.
A required value is missing, malformed, or the equipment and contract do not match.