Send one campaign to a specified mailing list (database), tag (list) or segment. As with the webapp UI, you may specify more than one list, tag, or segment, but you may only send to one category (i.e. you may not mix-and-match sending to lists and segments in the same XML request).


When specifying the recipient type ID, priority is given in reverse order. Segment IDs will be acknowledged before tag IDs, which will be acknowledged before list IDs. Essentially, the more specific recipient type ID will take precedence. If you include, for instance, a list ID, a tag ID, and a segment ID in the same XML call, the segment ID will be used to process the campaign send, and the list ID and tag ID will be ignored.


Regarding the Send From fields of the request, if you do not explicitly set any of these fields, they will be automatically populated from list (Database) settings. If you do not specify a list ID, then the first list associated with a subscriber from any specified segment or tag IDs will be used to populate the send data. If you want to use a particular list's Send From fields, but send to a tag or a segment, you may still specify a list ID - it will be ignored in favor of any segment or tag IDs when it comes to generating the recipient list, as described in the paragraph above.


XML Request Example - Sending to a single list ID:      

<?xml version="1.0" encoding="UTF-8"?>
<xmlrequest>
   <username>admin</username>
   <usertoken>abc123abc123abc123abc123abc123abc123abc123abc123</usertoken>
   <requesttype>newsletter</requesttype>
   <requestmethod>SendCampaign</requestmethod>
   <details>
      <campaignid>18</campaignid>
      <listid>69</listid>
   </details>
</xmlrequest>


XML Request Example - Sending to multiple tag IDs:      

<?xml version="1.0" encoding="UTF-8"?>
<xmlrequest>
   <username>admin</username>
   <usertoken>abc123abc123abc123abc123abc123abc123abc123abc123</usertoken>
   <requesttype>newsletter</requesttype>
   <requestmethod>SendCampaign</requestmethod>
   <details>
      <campaignid>18</campaignid>
      <tagid>70</tagid>
      <tagid>71</tagid>
   </details>
</xmlrequest>


<xmlrequest> elements


Field NameDescription
usernameUsername used to login to Pinpointe
usertokenUnique token assigned to Pinpointe account
requesttypenewsletter
requestmethodsendcampaign


<details> elements


Field NameDescription
campaignidID of campaign to send.
listidID of list (database) that will receive campaign. (optional - at least one list, tag, or segment ID must be specified)
tagidID of tag (list) that will receive the campaign. (optional - at least one list, tag, or segment ID must be specified)
segmentidID of segment that will receive the campaign. (optional - at least one list, tag, or segment ID must be specified)
sendfromnameThe name to be displayed in the email "Sent From" field. (optional - will auto populate from list data)
sendfromemailThe email address the campaign will appear to be "Sent From". (optional - will auto populate from list data)
replytoemailThe email address the campaign will use for the "Reply To" field. (optional - will auto populate from list data)
bounceemailThe email address the campaign will use for the bounce email address header. (optional - will auto populate from list data)


Successful Response:


<response> element


Field NameDescription
statusWill return SUCCESS if user was successfully added
dataWill return 1 if contact was located


Unsuccessful Response:


<response> element


Field NameDescription
statusWill return ERROR if unsuccessful
errormessageText explaining why request failed