Yes, WAV files are supported. I successfully created another engagement on this contact record with a WAV file and it plays.
I used the following body:
{
"engagement": {
"active": true,
"ownerId": "",
"type": "CALL",
"timestamp": 1546871864663
},
"associations": {
"contactIds": [2101],
"companyIds": [ ],
"dealIds": [ ],
"ownerIds": [ ]
},
"metadata" : {
"toNumber" : "1234567890",
"fromNumber" : "(987) 654-3210",
"status" : "COMPLETED",
"durationMilliseconds" : 38000,
"recordingUrl" : "https://cdn2.hubspot.net/hubfs/2676635/Temporary%20Files%20for%20Testing/Sample_Classical_WAV_File.wav",
"body" : "This is a test call with a WAV file as the recordingUrl."
}
}
I think the issue may be that your recordingUrl is HTTP instead of HTTPS. Since HubSpot contact records are secure and use HTTPS, they will likely not play files hosted on an insecure HTTP protocol.
If you can enable SSL on that domain or upload the files to your HubSpot account's file manager with this API, your recordings should play.
Yes, WAV files are supported. I successfully created another engagement on this contact record with a WAV file and it plays.
I used the following body:
{
"engagement": {
"active": true,
"ownerId": "",
"type": "CALL",
"timestamp": 1546871864663
},
"associations": {
"contactIds": [2101],
"companyIds": [ ],
"dealIds": [ ],
"ownerIds": [ ]
},
"metadata" : {
"toNumber" : "1234567890",
"fromNumber" : "(987) 654-3210",
"status" : "COMPLETED",
"durationMilliseconds" : 38000,
"recordingUrl" : "https://cdn2.hubspot.net/hubfs/2676635/Temporary%20Files%20for%20Testing/Sample_Classical_WAV_File.wav",
"body" : "This is a test call with a WAV file as the recordingUrl."
}
}
I think the issue may be that your recordingUrl is HTTP instead of HTTPS. Since HubSpot contact records are secure and use HTTPS, they will likely not play files hosted on an insecure HTTP protocol.
If you can enable SSL on that domain or upload the files to your HubSpot account's file manager with this API, your recordings should play.
The users you tagged are not associated with HubSpot, so I deleted your second post.
There could be a number of things going on here. To troubleshoot effectively, I will need to know your Hub ID and the response you received from this endpoint.