Retrieve the specified subscriber by subscriber ID who may be on one or more lists, including their respective custom field data.


XML request example:


<?xml version="1.0" encoding="UTF-8"?>
<xmlrequest>
  <username>JohnDoe</username>
  <usertoken>abc123abc123abc123abc123</usertoken>
  <requesttype>Subscribers</requesttype>
  <requestmethod>GetSubscribersById</requestmethod>
  <details>
    <list>{*list_id*}</list> <!-- required -->
    <subscriberid>{*subscriber_id*}</subscriberid> <!-- required: at least one -->
    <subscriberid>{*subscriber_id*}</subscriberid>
    <customfields>{*customfield_name*}</customfields>
    <customfields>{*customfield_name*}</customfields>
    <customfields>all</customfields>
    <sort>
      <field>{*sort_field*}</field>
      <direction>{*sort_direction: asc|desc|orig*}</direction>
    </sort>
    <include_membership>{*include_membership_boolean*}</include_membership>
  </details>
  <version>4.0</version>
</xmlrequest>


<xmlrequest> element


Field NameDescription
usernameUsername used to login to Pinpointe
usertokenUnique token assigned to Pinpointe account
requesttypeSubscribers
requestmethodGetSubscribersById


Please note: ALL OPTIONAL tags that are not used should be deleted from submitted call. For example, if no <customfield> value is inserted, the <customfield> tags should be deleted. 


<details> element


Field NameDescription
list
(At least one required)
ID of list(s) to be searched for the specified contact.
subscriberid
(At least one required)
Subscriber ID(s) of contact(s) to search for.
customfieldComma-separated list of custom field IDs. Or user may use the default "all" value provided.


<details> 

<pagination> OPTIONAL


Field NameDescription
limitEnter an integer to set the numerical limit for number of master-unsubscribe subscriber records that will be returned from a single call. 
nextStarting subscriber record number for a given call. If element is deleted, default is 0 (first record).


<details>

<sort> OPTIONAL


Field NameDescription
fieldID of custom field to be added. If <sort> tag deleted, system will sort by subscribers' email address. 
directionSort order of either ascending or descending. 
 

<include_membership> element


include_membership
PieSync requirement: Setting this element's value to true, 1 or yes results in the API call adding a list of all tags that a subscriber is in as part of the returned information for that subscriber.


Successful Response:

<response> element


Field NameDescription
statusWill return SUCCESS if subscriber and list successfully found


<data>

<item> element


System will return a full dateset of subscriber attribute values on the found subscriber, 


Unsuccessful Response:


<response> element


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