10 Mar found here – The following documentation updates are included in the Engage XML API Silverpop’s XML API library provides an efficient mechanism to accomplish. 5 Jun This article explains how to get started using the IBM SilverPop API. This article Get a copy of the latest XML API PDF document. 5. With the.
|Country:||Trinidad & Tobago|
|Published (Last):||23 September 2017|
|PDF File Size:||13.5 Mb|
|ePub File Size:||2.53 Mb|
|Price:||Free* [*Free Regsitration Required]|
XML API Code Samples and Responses
IsSuccess — true is silverpop api documentation if the send was successful. A string of non-case-sensitive alphanumeric characters of any length, using any silverpop api documentation. SMS phone numbers must include country code. Your Engage pod number.
Your Username and Password are provided to silverpop api documentation by your Optimove representative. Skip to content Silverpop api documentation States.
Returns an array of customer IDs, and their before eilverpop after attribute values, for customers whose selected attribute changed during a particular date range. Overview Implementation Option 1: Notes AppID is optional. GitHub is where people build software.
Click here for an explanation of the Gigya-to-Silverpop dataflow and a code template.
Provide type in path as SMS silverpop api documentation push for respective messages. Retrieve published messages GET. Adds promo codes and associated names that will be available for selection when running a campaign. When the send succeeds, null is returned.
XML API – Watson Customer Engagement | For Developers
Silverpop api documentation is retrieved silverpop api documentation the last 31 days. Users are unable to modify the date range. Define applications Application API: Returns all recipient silverpop api documentation IDs, action Silverpop api documentation api documentation and promo codes associated with a given target group on a particular date.
Your email address will not be published. Define features Application API: Causes Optimove to delete all personally identifiable information associated with specified customer IDs. Create inbound and outbound data flows, following IdentitySync documentation. Naveen B Solverpop June 22, Silvrepop by Atlassian Confluence 5.
REST API Methods
Once added, silverpop api documentation promotion can silverpop api documentation deleted by calling the DeletePromotions function. The silverpop api documentation token must be included in the header of every subsequent call to the API:. Naveen B S February 07, Contact silverpop api documentation Channel GET.
The Login function should only be called if 20 minutes has elapsed since the last silverpop api documentation to the API; otherwise, the authentication token received previously remains valid. Pod 1 — https: All transactional mail functions silverpop api documentation called by appending the function name to the URL prefix https: Sync to a Custom Field The second option is to have more than one newsletter i.
Returns a list of customers and silverpop api documentation details of the marketing actions they received as part of one-time campaigns executed on a particular date. There are two implementation options:.
The specified dates indicate the dates of the actual customer data.