Events

Most 10DLC status changes are asynchronous, you can create a webhook subscription to listen to status change events (see API details here)

10dlc supports three status change event webhook types

• 10dlc.brand

• 10dlc.campaign

• 10dlc.vetting

10dlc.brand

This event refers to the brand status changes (you can read more about brand status here ) .

To get more information about the reason forREJECTED brand status it is possible to fetch the rejection reason by getting the brand object. Rejection reasons are not always available for all brand rejections.

  "rejection": {
    "description": "text"
  }

Rejection descriptions are part of the brand objects but NOT the brand status events

10dlc.campaign

This event refers to the campaign status changes (you can read more about campaign status here ) .

To get more information about the reason for DECLINED the campaign status it is possible to fetch the rejection reason by getting the campaign object

For rejected campaigns only campaigns with DECLINED status are eligible to be resubmitted. All other campaign rejections will require a new campaign to be created.

Campaign rejections are always accompanied by a reason (the full list of reasons can be found here);

  "rejection": {
    "description": "text"
  }

Rejection descriptions are part of the campaign objects but NOT of the campaign status events

10dlc.vetting

This event refers to brand vetting status changes (you can read more about vetting status here ) .

To get more information about the reason forREJECTED vetting status it is possible to fetch the rejection reason by listing all vetting for a given brand

  "rejection": {
    "description": "text"
  }

Rejection descriptions are part of the Vetting objects but NOT of the rejection events