ndv

window.Ecwid.OnAPILoaded.add(function() {
    window.Ecwid.setSignInUrls({
        signInUrl: 'http://my.site.com/signin',
        signOutUrl: 'http://my.site.com/signout' // signOutUrl is optional
    });
});

ndv

<?xml version="1.0" encoding="UTF-8"?>
<be-owner-result>
  <redirect-url>URL_TO_REDIRECT_TO</redirect-url>
</be-owner-result>

ndv

<storeList>
 <stores>
   <id>STORE ID</id>
   <channelId>PARTNER ID</channelId>
   <name>Store name</name>
   <nick>Store owner's nickname</nick>
   <email>Store owner's email</email>
   <url>Store URL</url>
   <suspended>'Suspended' status, either 'true' or 'false'</suspended>
   <traffic>Traffic consumed since start of the month, bytes</traffic>

ndv

<!--
This is the default store template file which is used to create new stores. It contains all predefined settings and
products, and even demo orders and customers. Every bit of this template can be replaced when the store is
creating in an API call. The custom template passed in API call should have the same structure, but may only describe
some of the tags. Tags in the custom template replace the corresponding tags in the default template before it
gets applied to store creation. Tags that are missing from the custom template are taken from the default template.

Note that some tags are replaced, not merged, meaning that all the subtag structure is taken from the custom 
template, if the custom template specifies the tag.