Links

Webhook events and notifications

Via Partner API

After your Webhook URL is set, you will start receiving Webhook events regarding your client's accounts.
The events shared today are:

Client Account created

This event is submitted to a partner's webhook when a new client registers under their hub.
The field event will have client_created value set.
Example payload

Account violation

This event is submitted to a partner's webhook when a client's account is restricted.
The field event will have account_violation value set.
You will be able to identify which account was restricted by the value phone_number. There will also be violation_type, which indicates what made the account be restricted.
Example payload

Account restriction

This event is submitted to a partner's webhook when a client's account is restricted.
The field event will have account_restriction value set.
You will be able to identify which account was restricted by the value phone_number. There will also be violation_type, which indicates what made the account be restricted.
Example payload

Channel created

This event is triggered every time a new channel is created under your 360 Partner Hub. This is the first event created after the client finishes signup.
The field event will have channel_created value set.
You will be able to identify which client created this channel in the client_id and client fields. You are also able to see the phone number (phone_number field) and display name (phone_name field) registered in this channel.
Under the field created_at you can see when was the account created and under billing_started_at you can see when the billing started.
You can also see the current Business Manager status of this account under fb_account_status and the account status under status and account_mode.
Example payload

Channel submitted

This event is triggered every time a new channel is submitted to Meta for the WABA creation. It happens after the Channel is created.
The field event will have channel_submitted value set.
You will be able to identify which client created this channel in the client_id and client fields. You are also able to see the phone number (phone_number field) and display name (phone_name field) registered in this channel.
Under the field created_at you can see when was the account created and under billing_started_at you can see when the billing started.
You can also see the current Business Manager status of this account under fb_account_status and the account status under status and account_mode.
Example payload

Channel live

This event is triggered every time a new channel submitted under your 360 Partner Hub goes live.
The field event will have channel_live value set.
You will be able to identify which client created this channel in the client_id and client fields. You are also able to see the phone number (phone_number field) and display name (phone_name field) registered in this channel.
Under the field created_at you can see when was the account created and under billing_started_at you can see when the billing started.
You can also see the current Business Manager status of this account under fb_account_status and the account status under status and account_mode.
Example payload

Channel permission granted

This event is triggered every time a client grants permission for their number, meaning that you can now request the API Key for this specific channel.
The field event will have channel_permission_granted value set.
You will be able to identify which client created this channel in the client_id and client fields. You are also able to see the phone number (phone_number field) and display name (phone_name field) registered in this channel.
Example payload

Channel permission revoked

This event is triggered every time a client revokes permission for their number.
The field event will have channel_permission_revoked value set.
You will be able to identify which client created this channel in the client_id and client fields. You are also able to see the phone number (phone_number field) and display name (phone_name field) registered in this channel.
Example payload

Channel subscription was set

This event is triggered when a channel subscription is set, meaning when the billing starts for this channel.
The field event will have channel_subscription_set value set.
You will be able to identify which client created this channel in the client_id and client fields. You are also able to see the phone number (phone_number field) and display name (phone_name field) registered in this channel.
Example payload

Cancellation request

This event is triggered every time a client requests a channel cancellation.
The field event will have cancellation_request value set.
You will be able to identify which client created this channel in the client_id and client fields. You are also able to see the phone number (phone_number field) and display name (phone_name field) registered in this channel.
Example payload

Cancellation revoked

This event is triggered every time a client revokes a channel cancellation.
The field event will have cancellation_revoke value set.
You will be able to identify which client created this channel in the client_id and client fields. You are also able to see the phone number (phone_number field) and display name (phone_name field) registered in this channel.
Example payload

Cancellation processed

This event is triggered every time a client cancellation request is processed and the phone number is deleted.
The field event will have cancellation_processed value set.
You will be able to identify which client created this channel in the client_id and client fields. You are also able to see the phone number (phone_number field) and display name (phone_name field) registered in this channel.
Example payload

Channel enabled for template messaging

Right after signup, after the channel is live, it is temporarily disabled for template message sending. Each channel goes through internal 360dialog review and, if valid, will have template messaging enabled in up to 2 hours.
When a channel is enabled for template messaging, the partner will receive this event.
Field event will have template_messaging_enabled value set.
Example payload

Template approved, rejected or flagged

Quality-rating event

This event is submitted to a partner's webhook when numbers quality rating changes and we receive a callback from Meta.
Field event will have phone_number_quality_changed value set. Also in data object, there will be an extra property called current_quality_update_event to tell the type of event received from FB. Examples of events are flagged, etc.
Example payload

Via WABA

After a Webhook is set, you will be able to receive the following events:
  • "phone_number_name_update"
  • "phone_number_quality_update"
  • "account_update"
  • "account_review_update"
  • "message_template_status_update"
  • "business_capability_update"
  • "template_category_update"
  • "payment" (if eligible)