INinfobip
channels
webrtc-calls
call-link
call-link-recordings

Get call link recordings

Use this method to filter and retrieve call link recordings.

get/call-link/1/recordings

Request

  • Base URL
    https://api.infobip.com (the document declares no server; this is the origin it was published from)
  • Auth
    • OAuth 2
      Client credentials
      Token URL: https://api.infobip.com/auth/1/oauth2/token
    • or API key in header Authorization
    • or API key in header Authorization
    • or HTTP basic

Query parameters

sortBy'DESTINATION_DATA' | 'DESTINATION_TYPE' | 'CALL_LINK_CONFIG_ID' | 'CALL_LINK_ID' | 'START_TIME_BEFORE' | 'START_TIME_AFTER'

Field that will be used for sorting.

sortDirection'ASC' | 'DESC'

Order in which files will be sorted based on sortBy field.

destinationDatastring

Destination the call was made towards. For WEBRTC calls, this is the WebRTC identity. For PHONE calls, this is the phone number. For ROOM calls, this is the room name.

destinationType'ROOM' | 'WEBRTC' | 'PHONE'

Destination type.

Type of call link destination.

callLinkConfigIdstring

ID of the call link configuration used to establish the recorded call.

callLinkIdstring

ID of a call link used to establish the recorded call.

startTimeAfterstring date-time

Date and time when the (first) call recording started.

startTimeBeforestring date-time

Date and time when the (last) call recording started.

location'SAO_PAULO' | 'BOGOTA' | 'FRANKFURT' | 'JOHANNESBURG' | 'JOHANNESBURG_1' | 'NEW_YORK' | 'PORTLAND' | 'MOSCOW' | 'SINGAPORE' | 'ISTANBUL' | 'KUALA_LUMPUR' | 'JAKARTA' | 'MUMBAI' | 'HONG_KONG_1' | 'HONG_KONG' | 'RIYADH' | 'CHENNAI'

Recording location.

pageinteger

Page number for pagination, starting from 0.

sizeinteger

Number of items per page, maximum is 100.

Response

Success.

Changes

No recorded changes to this operation across all 1 revision of this API.