Difference between revisions of "NATS4 API Set Member Details"

From TMM Wiki
Jump to navigationJump to search
Line 29: Line 29:
 
*state
 
*state
  
Here's an example of the request:
 
<pre>
 
<?xml version="1.0" encoding="ISO-8859-1"?>
 
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="urn:natsapiadmin_wsdl">
 
<SOAP-ENV:Body>
 
<tns:set_member_details xmlns:tns="urn:natsapiadmin_wsdl">
 
<memberid xsi:type="xsd:int">88</memberid>
 
<firstname xsi:type="xsd:string">joe</firstname>
 
<lastname xsi:type="xsd:string">montana</lastname>
 
<email xsi:type="xsd:string">joe@joe.com</email>
 
<address1 xsi:type="xsd:string">301 football way</address1>
 
<address2 xsi:type="xsd:string">PO Box 123</address2>
 
<city xsi:type="xsd:string">Winslow</city>
 
<state xsi:type="xsd:string">AZ</state>
 
<country xsi:type="xsd:string">USA</country>
 
<zip xsi:type="xsd:string">12345</zip>
 
<password xsi:type="xsd:string">pantaloons</password>
 
<custom1 xsi:type="xsd:string">sometimes when we touch</custom1>
 
<custom2 xsi:type="xsd:string">the honesty&apos;s too much</custom2>
 
<custom3 xsi:type="xsd:string">and I have to close my eyes</custom3>
 
<custom4 xsi:type="xsd:string">and hide</custom4>
 
<custom5 xsi:nil="true" xsi:type="xsd:string"/>
 
</tns:set_member_details>
 
</SOAP-ENV:Body>
 
</SOAP-ENV:Envelope>
 
</pre>
 
 
You will get a response similar to:
 
<pre>
 
<?xml version="1.0" encoding="ISO-8859-1"?>
 
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
 
<SOAP-ENV:Body>
 
<ns1:set_member_detailsResponse xmlns:ns1="urn:natsapiadmin_wsdl">
 
<return xsi:type="xsd:boolean">true</return>
 
</ns1:set_member_detailsResponse>
 
</SOAP-ENV:Body>
 
</SOAP-ENV:Envelope>
 
</pre>
 
The response contains one parameter named result.
 
If the modification was successful then result will be TRUE.  If it was not successful then the result will be FALSE.
 
  
 
NuSOAP Example (continuing from [[NATS4_API#Example|main article NuSOAP Example]]):
 
NuSOAP Example (continuing from [[NATS4_API#Example|main article NuSOAP Example]]):

Revision as of 14:08, 1 February 2013

NATS 4
Members Admin
The Members Admin
View Member Details
Add Member
MySQL Auth
Mod Authn DB
Multisite Access
Member Logging
Member Password Retrieval
OpenID Connect
Mod Auth OpenIDC
ID Numbers
SOAP API
API
API Best Practices
WSDL Cache
Add Affiliate
Add Member Note
Admin Get Adtools
Adtool Categories
Adtool Types
Affiliate Get Campaigns
Bulk Import Adtools
Caching
Decode Natscode
Expire Manual Member
Get Affiliate Campaigns
Get Affiliate Hit Data
Get Affiliate Loginids
Get Affiliate Nats Codes
Get Affiliate Payout
Get Affiliate Program Campaign List
Get_Affiliate_Program_Campaign_List
Get Member Details
Get Member Instant Upgrade String
Get Member Package Upgrade String
Get Member Token Rebuy String
Get Member Upsell String
Get Payment Data
Get Payvia Rule
Get Profit Loss Report
Ping
Record Member Login
Search Affiliate Info
Search Member Info
Send Email API Function
Set Affiliate Admin Settings
Set Affiliate Customs
Set Affiliate Defaults
Set Affiliate Information
Set Affiliate Settings
Set Member Details
Set Payment Status
Set Payvia Rule
REST API
API Overview
API Best Practices
REST API PATH UPDATES
Adtools
GET /adtools/admin
GET /adtools/categories
GET /adtools/types
POST /adtools/importdump
Affiliate
GET /affiliate/campaigns
GET /affiliate/hitdata
GET /affiliate/payout
GET /affiliate/searchinfo
POST /affiliate/addaffiliate
POST /affiliate/invoice
PATCH /affiliate/setadminsettings
PATCH /affiliate/setcustoms
PATCH /affiliate/setdefaults
PATCH /affiliate/setinformation
PATCH /affiliate/setpayviainfo
PATCH /affiliate/setsettings
PATCH /affiliate/status
Member
GET /member/authstring
GET /member/details
GET /member/searchinfo
GET /suggestedcanceloffers
PATCH /member/setdetails
PATCH /member/setexpiration
POST /member/addnote
POST /member/recordlogin
PUT /member/expiremanual
PATCH /member/forget
Option
GET /option/options
GET /option/rule
PATCH /option/rule
PATCH/option/text
POST /option/rule
Payments
GET /payments/getpayments
GET /payviarule
PATCH /payments/setstatus
PATCH /payviarule
Report
GET /profitlossreport
Get /transactionpayouts
GET /report/transaction
Service
GET /service/decodenatscode
GET /service/ping
POST /service/sendemail

This feature is available as of version 4.0.71.1

set_member_details requires the following parameters:

  • memberid The nats memberid of the member being updated.

set_member_details accepts the following additional parameters (requiring at least one of these):

  • firstname
  • lastname
  • email
  • password
  • address1
  • address2
  • city
  • state
  • zip
  • country
  • custom1
  • custom2
  • custom3
  • custom4
  • custom5


If you want to remove a field you can pass in the string REMOVE and the field will be removed. The following fields have this ability:

  • Address2
  • state


NuSOAP Example (continuing from main article NuSOAP Example):

$values = array(
        'memberid' => 88,
        'password' => 'pantaloons',
        'firstname' => 'joe',
        'lastname' => 'montana',
        'email' => 'joe@joe.com',
        'address1' => '301 football way',
        'address2' => 'PO Box 123',
        'zip' => '12345',
        'city' => 'Winslow',
        'state' => 'AZ',
        'country' => 'USA',
        'custom1' => 'sometimes when we touch',
        'custom2' => "the honesty's too much",
        'custom3' => 'and I have to close my eyes',
        'custom4' => 'and hide',
);
$result = $client->call('set_member_details', $values, 'natsapiadmin_wsdl');
var_dump($result);

Output:

bool(true)