Miscellaneous FAQ

1. Is there, or will there be, a UI in the sandbox to view the changes we make in the API?

   There is currently no UI, and we do not have any plans to add a UI to the sandbox. You should use the API to insert, modify and extract data from our systems.

2. What are the length limits for char/string fields?

   Please see our Market-Specific values section for the char/string length limits for your market.

3. What encoding types do your web services support?

   At this time, we only support UTF-8. Most toolkits default to UTF-8, but if yours does not, you may need to explicitly toggle the encoding settings.

   You can validate this by ensuring that your request XML sent to our servers starts with:

   <?xml version="1.0" encoding="UTF-8"?>

4. Why do I get a "Page size is too large" error message when executing various 'get' commands?

   You have probably supplied the input parameters in an incorrect order. As a rule of thumb, please make sure that the order of the parameters in your request matches the order in the WSDL.

5. Why do I get odd errors about elements not being found, though I can see them in my request?

   There is probably something wrong with your namespace being specified. Remember, you have to be consistant about namespace usage, otherwise we can't tell which elements are which. While the XML might read okay to a human, a computer parser will be confused.

   Check out this w3schools primer on namespaces. Pretty good refresher.

   Bad Example:

   <ns1:somecommand xmlns:ns1="http://marketing.ews.yahooapis.com/V1">
   
   			 <sometype>
   
   			  <someelement>value</someelement>
   
   			 </sometype>
   
   			</ns1:somecommand>
   
   			

   Good Example:

   <ns1:somecommand xmlns:ns1="http://marketing.ews.yahooapis.com/V1">
   
   			 <ns1:sometype>
   
   			  <ns1:someelement>value</ns1:someelement>
   
   			 </ns1:sometype>
   
   			</ns1:somecommand>
   
   			

   Or just avoid using these additional namespaces.

6. What is the format of the dateTime type found in many of the WSDLs?

   The proper format is is the W3C standard, found here.

   Example:

   2007-07-04T14:30:00-08:00

   Which represents July 4th, 2007 at 2:30PM in the Pacific time zone.

7. Why can't I access the VaultService operations through the endpoint returned by the LocationService's getMasterAccountLocation operation?

   VaultService operations must be accessed through a specific endpoint. This endpoint is specified in the VaultService WSDL:

        Endpoint:

             https://vault.marketing.ews.yahooapis.com/services/V3/VaultService