Call Recordings

List all recording transcriptions

Returns a list of your recording transcriptions.

get/recording_transcriptions

Query parameters

sizeinteger

The size of the page.

numberinteger

The page number to load.

Consolidated page parameter (deepObject style). Originally: page[size], page[number]

recording_idstring uuid

If present, transcriptions will be filtered to those associated with the given recording.

Filter recording transcriptions by various attributes.

{
  "recording_id": "428c31b6-7af4-4bcb-b7f5-5013ef9657c1",
  "created_at": {
    "gte": "2019-03-29T11:10:00Z",
    "lte": "2019-03-29T11:10:00Z"
  }
}

Response

A response listing multiple recording transcriptions.

Example response

{
  "data": [
    {
      "created_at": "2018-02-02T22:25:27.521Z",
      "duration_millis": 60000,
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "recording_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "record_type": "recording_transcription",
      "status": "completed",
      "transcription_text": "Good morning, how may I help you?",
      "updated_at": "2018-02-02T22:25:27.521Z"
    }
  ],
  "meta": {
    "cursors": {
      "after": "v1:g3QAAAADZAAKdGVsbnl4X2lkc2wAAAABbQAAACRlYmRiYzdkNi1kZWRmLTExZWQtYTM3MS0wMjQyMGFlZjAwYjRqZAAJdGltZXN0YW1wbggA8Le4pGhpVxdkAAR0eXBlZAAFYWZ0ZXI=",
      "before": "v1:g3QAAAADZAAKdGVsbnl4X2lkc2wAAAABbQAAACRlYmRiYzdkNi1kZWRmLTExZWQtYTM3MS0wMjQyMGFlZjAwYjRqZAAJdGltZXN0YW1wbggA8Le4pGhpVxdkAAR0eXBlZAAFYWZ0ZXI="
    },
    "next": "/v2/recording_transcriptions?page[after]=v1:g3QAAAADZAAKdGVsbnl4X2lkc2wAAAABbQAAACRlYmRiYzdkNi1kZWRmLTExZWQtYTM3MS0wMjQyMGFlZjAwYjRqZAAJdGltZXN0YW1wbggA8Le4pGhpVxdkAAR0eXBlZAAFYWZ0ZXI=",
    "previous": "/v2/recording_transcriptions?page[before]=v1:g3QAAAADZAAKdGVsbnl4X2lkc2wAAAABbQAAACRlYmRiYzdkNi1kZWRmLTExZWQtYTM3MS0wMjQyMGFlZjAwYjRqZAAJdGltZXN0YW1wbggA8Le4pGhpVxdkAAR0eXBlZAAFYWZ0ZXI="
  }
}

Changes

Changed in 3 of the 99 revisions of this API.9

    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    This revision also has 34 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • ▲

      the // response's property type changed from integer to string, and format from int32 to no format for status

      response-property-type-changed

    • ▲

      the // response's property type changed from integer to string, and format from int32 to no format for status

      response-property-type-changed

    • ▲

      the // response's property type changed from integer to string, and format from int32 to no format for status

      response-property-type-changed

    This revision also has 64 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    • ▲

      the // response's property type changed from string to integer, and format from no format to int32 for status

      response-property-type-changed

    This revision also has 41 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Of the 99 revisions, 1 has no diff computed.