- Create and access accounts with a single master list.
- Access accounts with a monthly subscription plan through the API (Subscriptions will still only be maintained through the VerticalResponse website).
- Calls to get a list of lists (enumerateLists() method), will indicate which list is the master list.
- List member data will be maintain consistent across all lists with single calls to editListMember() and deleteListMember().
- Differentiate between accounts with master lists from those without through the API.
Beginning on Tuesday, July 19, 2011, we will open a public API testing server that will allow you to test the new version of the API from your local sandbox environment.
IMPORTANT: Testing should be done in an environment separate from the production version of your integration with VerticalResponse to prevent any downtime to your customers.
To test these changes to our API, please follow these instructions:
- You will need to change your test environment’s DNS settings temporarily so that api.verticalresponse.com points to our testing server. You can do this by adding the following line to your hosts file:184.108.40.206 api.verticalresponse.comIn a Linux and Mac OS X environment, your hosts file is located at “/etc/hosts”. In a Windows environment, your hosts file can be found at “%WinDir%\System32\Drivers\etc\hosts”.
- In your test environment, point your code to the WSDL at the following URL:Enterprise API
https://api.verticalresponse.com/partner-wsdl/1.0/VRAPI.wsdlPlease Note: If you are using a language that requires you to compile the stub code generated from this WSDL (i.e. Java, C#, etc.) you will need to regenerate and recompile that code in order to perform these tests.
- IMPORTANT: Our test servers point to the production databases – Any changes made to data on these servers will also be made to your live accounts. We suggest you create a new account to test your integration against in order to avoid impacting live customer data.
- Please thoroughly test your integration with VerticalResponse to ensure it works as expected. We intend to push the new API to our production servers on August 10th between 6pm and 10pm. You should plan to push any changes you may have made to make your code work with these changes to your production environment during that time as well.
The testing environment will be available as of 12:00pm PDT, 7/19/2011. Updates to this release information shall appear here, so please bookmark this page and check back periodically. If you have questions or need assistance, please contact firstname.lastname@example.org.
We look forward to the upcoming release and to your testing feedback.