CustomerContentSearch
Description
Often you use CustomerContentSearch
to find a customer ID that you
can use in the CustomerContentLookup
operation, which returns more
extensive customer information.
Important | |
---|---|
You must never display customer IDs publicly. You may use them in requests only to look up information. You may associate that information with a customer's name or nickname but never his or her customer ID. |
Availability
US
Request Parameters
Name | Description | Required |
---|---|---|
CustomerPage
|
A positive integer that specifies the page of customer IDs to return. Up to twenty customer IDs are returned per page. Type: Positive integer Type: String Default: 1 Valid Values: Integers 1 to 20. Constraint: Up to twenty pages of results can be viewed. |
Conditional |
e-mail
|
e-mail address of a customer whose ID you want to find. Type: String Default: None Valid Values: Valid e-mail address. Constraint: Either |
Conditional |
Name
|
A customer's name whose ID you want to find. To enter a first and last name, URL-encode the space in between with %20. Type: String Default: None Constraint: Either |
Conditional |
ResponseGroup
|
Specifies the types of values to return. You can specify multiple response groups in one request by separating them with commas. Type: String Default: CustomerInfo |
No |
CustomerContentSearch
also accepts the parameters that all operations can
use. For more information, see, Common Request
Parameters
Response
Name | Description |
---|---|
City
|
City where the customer lives. |
Country
|
The country in which the customer lives. |
Customer
|
Container for information about a Customer, for example, their NickName. |
Customers
|
Container for Customer. |
Location
|
Container for the elements State and Country. |
Nickname
|
The nickname of the customer. |
State
|
State the customer specified. |
For more information about the parent elements of these tags, see the appropriate response group in Response Groups
Examples
Find a customer ID by supplying the customer’s e-mail address.
http://ecs.amazonaws.com/onca/xml? Service=AWSECommerceService& AWSAccessKeyId=[AWS Access Key ID]
& AssociateTag=[Associate ID]
& Operation=CustomerContentSearch& e-mail=GeorgeWashington%40ISP.com
Note that the @ sign in the e-mail address is URL-encoded as %40. The response to this request is shown in, Response to Sample Request.
Find a customer ID by supplying the customer’s name.
http://ecs.amazonaws.com/onca/xml? Service=AWSECommerceService& AWSAccessKeyId=[AWS Access Key ID]
& AssociateTag=[Associate ID]
& Operation=CustomerContentSearch& Name=George%20Washington
Note that blank spaces must be URL-encoded, as shown in this example.
Sample Response
The following XML is a snippet of the full response to the first sample request.
<Customer> <CustomerId>A111111111</CustomerId> </Customer> <Customer> <CustomerId>A2222222222</CustomerId> <Nickname>WilliamShakespeare</Nickname> <Location> <City>London</City> <Country>England</Country> </Location> </Customer>
This response shows that the customer has two IDs.