bobcodes | 2022-10-27 19:17:45 UTC | #1
What is the complete schema for the metadata files on recording exports? It seems that if certain attributes are not present in the conversation then the key for it does not exist in the metadata (rather than null or empty list as one would expect). For example a conversation which does not interact with any queues does not have the "queueIds" key in the json, instead of an empty list. In order to determine which attributes we will need to query for separately I would like to know what keys may exist in the metadata file.
jacobshaw | 2022-10-28 13:53:59 UTC | #2
Hi @bobcodes You can check the success schemas for API resources in API explorer under the "API Responses -> 200 - successful operation" tab The recording metadata schemas are here: GET /api/v2/conversations/{conversationId}/recordingmetadata/{recordingId} GET /api/v2/conversations/{conversationId}/recordingmetadata
bobcodes | 2022-10-28 14:38:41 UTC | #3
That's interesting there's another type of recording metadata, I was referring to the export metadata file actually. Another Genesys employee sent me a link to this post which is exactly what I was looking for https://community.genesys.com/digestviewer29/viewthread?MessageKey=0ecabb50-d562-4bbd-bc98-1cd7279adccc&CommunityKey=bab95e9c-6bbe-4a13-8ade-8ec0faf733d4#bm4ce91c6c-ea0c-4b1f-afde-7007d34778f6 To anyone that stumbles on this in the future, the current schema is as follows (according to the referenced post):
- aniDisplayable -> ANI in displayable form
- aniNormalized -> ANI
- conversationEndTime -> conversation's end time
- conversationId -> unique ID associated with the conversation
- conversationStartTime -> conversation's start time
- dnisDisplayable -> DNIS in displayable form
- dnisNormalized -> DNIS
- durationMs -> duration of the recording
- endTime -> end time on the recording
- filePath -> original path of the recording
- fileSize -> recording file size
- initialDirection -> Initial direction of the conversation (inbound/outbound)
- languageIds -> Identifier on the language
- mediaType -> Media Type (one of Call,Chat,Email,Message, Callback, Screen)
- messageType -> type of message platform from which the message originated, e.g., sms, twitter, line, facebook, whatsapp, webmessaging, open, instagram
- organizationId ->
- provider -> type of provider for the recording, for example edge
- queueIds -> list of queue IDs for the recording
- recordingId -> unique ID for the recording
- screenInformation -> screen specific information, includes the screen ID, X and Y position, resolution information
- startTime -> start time of the recordings
- userIds -> list of users
- wrapupCodes -> wrap-up codes for the conversation
And to any engineers that find this, I would love to see work team ids make it into this!
system | 2022-11-28 14:38:52 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 16940