Upload a Personal recording

POST /v1/recordings/own

Summary:
Allows an authenticated user (via GUI) to manually request an upload operation.

Security:

Bearer Authentication required.

Request Body:
JSON object including:

fileName: (string) File name including extension.
speakers: (integer, optional) Number of speakers (min 2, max 10). If not provided, auto-detected.
language: (string, optional) Language code (from a fixed list) or auto-detected.
callData: Object with:
- direction: (string) One of IN, OUT, or UNKNOWN (default is UNKNOWN).
- localParty: Object with username and number.
- remoteParty: Object with username and number.
recordingDate: (string) ISO date-time for the recording (UTC).
contentMd5: (string) Base64-encoded MD5 hash.

Example:

CODE

{
  "fileName": "file_Name.mp3",
  "contentMd5": "Dz0RIM96f8B1QA0wkhfXyg==",
  "speakers": 2,
  "language": "it-IT",
  "recordingDate": "2019-08-24T14:15:22Z",
  "callData": {
    "direction": "IN",
    "localParty": { "username": "user1", "number": "123" },
    "remoteParty": { "username": "user2", "number": "+39 456 789" }
  }
}

Response:

200 OK:
Returns a JSON object with a presignedUrl used for the PUT upload.
400, 401, 403, 500: Error responses with details.

File Upload Note:
For the PUT request to the presigned URL, the client must include headers for all file metadata (e.g. direction, filename, language, speakers, recording date, party numbers/userId) as well as content-md5.