Pulse

Get Pulse configuration

Returns the current Pulse settings for all slots, along with how many slots are currently in use. Handy when you need to decipher actual Pulse data, as pulse events types are identified by their configuration slot.

Note that slots are enumerated starting from an index of 1 (one).

get/v1/meetings/{meetingId}/pulse/metadata

Request

Base URL: https://app.meet.ps/api
URL: https://app.meet.ps/api/v1/meetings/{meetingId}/pulse/metadata
Auth: none required

Path parameters

meetingIdstring required

A canonical meeting ID string that's generated automatically for new meetings. Normally consists of just alphanumericals; legacy meetings can have dashes and underscores.

Example:kr9gui27

Meeting name string

Response

Pulse configuration object

Example response

{
  "result": {
    "config": {
      "1": {
        "caption": "Love",
        "icon": "heart",
        "background": "#f0f"
      },
      "2": {
        "caption": "Love",
        "icon": "heart",
        "background": "#f0f"
      },
      "3": {
        "caption": "Love",
        "icon": "heart",
        "background": "#f0f"
      },
      "4": {
        "caption": "Love",
        "icon": "heart",
        "background": "#f0f"
      },
      "5": {
        "caption": "Love",
        "icon": "heart",
        "background": "#f0f"
      },
      "6": {
        "caption": "Love",
        "icon": "heart",
        "background": "#f0f"
      },
      "7": {
        "caption": "Love",
        "icon": "heart",
        "background": "#f0f"
      },
      "8": {
        "caption": "Love",
        "icon": "heart",
        "background": "#f0f"
      },
      "9": {
        "caption": "Love",
        "icon": "heart",
        "background": "#f0f"
      }
    }
  }
}

Changes

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