Call

Call details

You need to know the unique_id of the considered call and request GET on the endpoint /calls/{unique_id}.

The value of unique_id is available at the root-level of each Call when getting a response from
Call list endpoint.

Trying to access the details URL of a missing Call will return a
404 status code.

Call metadata

Available from this details endpoint as well as from the Call list endpoint, the key metadata contains all the input you might have passed within the JSON file when using our SFTP JUpload product.

Please note that as of now, these metadata can only be processed by JUpload via JSON files, and not CSV ones.
See JUpload documentation for more details.

Call audio

Call audio (redacted according to your configuration) are available for download as MP3 files. You need to know the unique_id of the considered call and request GET on the endpoint /calls/{unique_id}/audio. The value of unique_id is available at the root-level of each Call when getting a response from Call list endpoint.

In order to comply with the GDPR, audio (and other data for that matter) must be pruned after a while.

From the Call list, the key audio_state will tell you if the audio is either available or missing.

Trying to access the audio URL of a missing Call will return a 451 status code.