Status and error codes
Error handling of POST requests
An internal ingestion upload session is created on the original POST with metadata. The Location URL returned from the original request identifies this session.
For the example upload request shown in
Location: <myWFE>/api/recording/ingestion/v3/recordings/Aw8KDgcFBAoHDwQOBA8NAA
-
The upload session id (Aw8KDgcFBAoHDwQOBA8NAA) is used internally to track all files associated with this upload session. In this case, the original metadata declared that there are two related content files, an audio (wav) file and a video file (mp4). The session stays open until all content parts are uploaded or the hour timeout expires.
-
The upload session is not created unless the original metadata POST returns a 201 Created response.
-
The system automatically cleans up the sessions after an hour and the client does not need to remove abandoned ingestion sessions.
-
Each part must be uploaded individually using a PUT request. If one part fails, it can be restarted.
-
A 202 Accepted response from uploading a part indicates that this specific part is uploaded, but there are more parts that need to be uploaded for the ingestion session to be complete.
-
A 200 OK response to a content part upload indicates that all parts have been received and the ingested interaction is now successfully added to the Verint system. No further action is required for this ingestion session.