For a given customer Email address or name, the CustomerContentSearch operation returns matching customer IDs, names, nicknames, and residence information (city, state, and country). In general, supplying an Email address returns unique results whereas supplying a name more often returns multiple results.
Often you use CustomerContentSearch to find a customer ID that you can use in the CustomerContentLookup operation, which returns more extensive customer information.
The following table describes the request parameters for CustomerContentSearch. Parameter names are case sensitive.
| Parameter | Definition | Req'd? | Valid Values |
|---|---|---|---|
CustomerPage
| A positive integer that specifies the page of customer IDs to return. Up to twenty customer IDs are returned per page. Up to twenty pages of results can be viewed. By default, the first page is returned. | Yes | Integers 1 to 20. |
Email
| A valid Email of a customer whose ID you want to find. | Either Email or Name are required. | Valid Email address. |
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. | Either Email or Name are required. | String |
ResponseGroup
| Specifies the types of values to return. You can specify multiple response groups in one request by separating them with commas. | No |
Request (Default) CustomerInfo (Default) |
CustomerContentSearch also accepts the parameters that all operations can use. For more information, see, Common Request Parameters
The following table describes the default response tags included in CustomerContentSearch responses.
| Element Tag | Definition |
|---|---|
City
| City where the customer lives. |
Country
| The country in which the customer lives. |
Customer
| Containter 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
Use CustomerContentSearch in the following ways:
Find a customer ID by supplying the customer’s Email address.
http://ecs.amazonaws.com/onca/xml? Service=AWSECommerceService& AWSAccessKeyId=[Access Key ID]& AssociateTag=[Your Associate ID Here]& Operation=CustomerContentSearch& Email=GeorgeWashington%40ISP.com
Note that the @ sign in the Email address is URL-encoded as %40. The response to this request is shown in, Response to Sample Request below.
Find a customer ID by supplying the customer’s name.
http://ecs.amazonaws.com/onca/xml? Service=AWSECommerceService& AWSAccessKeyId=[Access Key ID]& AssociateTag=[Your Associate ID Here]& Operation=CustomerContentSearch& Name=George%20Washington
Note that blank spaces must be URL-encoded, as shown in this example.
The following XML is a snippet of the full response to the first sample request above.
<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.