Standard metadata provider works with the JSON format.

Format example:

{
  "customLongMetadata": {
    "longAttr": 123
  },
  "customDoubleMetadata": {
    "doubleAttr": 456.789
  },
  "customStringMetadata": {
    "stringAttr": "stringValue"
  },
  "direction": "Inbound",
  "callDate": 1000,
  "clientPhone": "89213312244",
  "clientFirstName": "Петр",
  "clientLastName": "Кукушкин",
  "operatorId": "kkutuzov",
  "operatorFirstName": "Константин",
  "operatorLastName": "Кутузов"
}
  • direction can be of 3 types: Unknown, Outbound, Inbound
  • callDate - call date in an instant format (i.e. timestamp in milliseconds)
  • clientPhone - of type string
  • clientFirstName - of type string
  • clientLastName - of type string
  • operatorId - of type string
  • operatorFirstName - of type string
  • operatorLastName - of type string
  • customLongMetadata - map of attributes of type long
  • customDoubleMetadata - map of attributes of type double
  • customStringMetadata - map of attributes of type string

To work from the autoprocessing folder, the JSON file should be put near the media file and have the same name.

Example:

  • media file - call_30023.ogg
  • metadata file - call_30023.json

Also, this format is used in public and internal API for job upload and call metadata update:

API model format → Standard format → CallMetaDataResult format