A callback entity is a registration to receive callback events to an external URL. It is identified by a CallbackID, which uniquely identifies the record. Additionally, each callback is unique for a given event type and active date range.
The following is the JSON representation of a callback entity within the APIs.
Vibes unique identifier for each callback record.
Event type to trigger this callback.
External URL to submit the callback data.
Method to submit the data to the destination URL.
Content type to set when submitting the data to the destination URL.
Valid content types:
Date this callback starts.
Date this callback ends.
No end date
Unique resource URL for the callback.
Date this callback was created.
Date this callback was last updated.
|list_id||String||Vibes unique identifier for a Subscription List.||Required|
|campaign_id||String||Vibes unique identifier for an Acquisition Campaign.||Required|
Person Event Types
The person_updated callback event is triggered when an existing Person record has been modified in the Mobile Database.
Subscription Event Types
The subscription_added callback event is triggered when a Person has been added to a Subscription List.
The subscription_removed callback event is triggered when a Person has been removed from a Subscription List.
Acquisition Campaign Event Types
The ack_participant_added callback event is triggered when a new Participant has been added to the Acquisition Campaign.
The ack_participant_changed callback event is triggered when a Participant has confirmed or declined the opt-in.
Subscription List Event Types
The subscription_list_added callback event is triggered when a new Subscription List has been created in the Mobile Database.
The subscription_list_updated callback event is triggered whenever a Subscription List has been modified in the Mobile Database.