36360learning
Group contents

Path sessions added to groups catalog

Sent to your endpoint when path sessions are added to one or more groups' catalog in your platform. If the action triggering this event impacts a lot of groups and path sessions, you can receive the impacted group IDs and path session IDs spread in several events.

postWebhookgroups.catalog.path.sessions.added

Headers

webhook-signaturestring required
Example:v1,4UHnozIIxoqswxyYsplgMpo1w5JaUjaPDlg5dm8n1SE=

The signature of the event payload, used to verify the authenticity of the event. If multiple signatures are present, they are space delimited.

webhook-idstring required
Example:msg_35bE2UOtsaBIqUl7VW4mLuR9q2B

The unique identifier of the event. It is the same ID for the retry attempts of the same event.

webhook-timestampstring required
Example:1763370163

The date and time when the event was emitted, in the Unix epoch format (number of seconds that have elapsed since January 1, 1970).

Payload

type'groups.catalog.path.sessions.added' required

The type of the event.

timestampinteger required

The date and time when the event was triggered in your platform, in the Unix epoch format (number of milliseconds that have elapsed since January 1, 1970).

Example payload

{
  "type": "groups.catalog.path.sessions.added",
  "data": {
    "groupIds": [
      "507f1f77bcf86cd799439011"
    ],
    "pathSessionIds": [
      "507f1f77bcf86cd799439011"
    ]
  }
}

Response

The event is considered as accepted for any 2xx response code.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.