



























SOAP Description for the Management Service
AddPartner()
In this cell you should fill the “partnerInfo” entity in.
Here is the description of all fields:
parentId: this is an ID of the parent partner. You can get it from the cell GetPartnerInfo().
name: string(70). This is a partner name.
level: there are 4 levels which are allowed, such as “Distributor”, “SubDistributor”, “Reseller” and
“EndCustomer”. You can't create a partner with a level equal or higher than the level of the parent
partner.
privilege: there are 3 types of privileges, such as “Regular”, “Education” and “Charity”. All of them
are available for super-user of the root partner. In a common case “Regular” should be used.
childServiceTypes: this is an array of types. There are 3 existing types: “All-Inclusive”, “FullService”
and “SoftwareOnly”. The type provided by the parent partner is very important here, because if they
provides only “All-Inclusive”, for example, you will be able to specify only “All-Inclusive”. You can
provide an empty value for this field and in this case a partner will not be able to create subpartners.
serviceType: this is a type of service for a partner. There are only 3 possible types “AllInclusive”,“FullService” and “SoftwareOnly”, but the type of service depends on the types that the
parent partner provided in the field childServiceTypes.
state: there are 3 different values that can be specified, such as “InTrial”, “Registered”,
“InProduction”. However there is one rule for “InProduction”: you can use it only if the parent
partner has the “InProduction” state too.
weight: there are 4 different weights, such as “Dynamic”, “Bronze”, “Silver”, “Gold”. All of them are
available by IASO root account. A general account can only use “Dynamic”.
locationId: this is an ID from the partner's country. You can select this ID from the
call EnumerateLocations(). If there is no country in this list, you should select an ID of the nearest
country in this list.
flags: this is an array of strings. There are 2 flags allowed – “HasCustomBranding” and
“HasCustomUpdatePackages”. You can use both of them or leave this field to be an empty array.
externalCode: string(100). This field can be used to store any information of yours.
company: this entity has its own sub-fields:
postAddress: this entity has its own sub-fields:
state: string(40). The state of the country the company is located in.
district: string(40). The name of the district in the company’s country.
city: string(unlimited). The name of the company’s city.
zipCode: string(20). The zip code of the company’s city.
address: string(unlimited). The address in the company’s city.
country: string(100). The name of the company’s country.
phoneNumber: string(unlimited). The company’s phone number.
faxNumber: string(30). The company’s fax number. Optional.
websiteAddress: string(unlimited). The company’s web address. Optional.
legalCompanyName: string(unlimited). The legal company's name.
chamberOfCommerceNumber: string(unlimited). The chamber of the commerce number. Optional.
vatNumber: string(unlimited). The vat number. Optional.
bankAccountNumber: string(unlimited). The bank account number. Optional.
comment: string(unlimited). Any comment for this partner. Optional.
minimalBillAmount: An internal field. You can specify “0” here.
This is an XML example:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:AddPartner>
<request>
<partnerInfo>
<parentId>6</parentId>
<name>test</name>
<level>EndCustomer</level>
<privilege>Regular</privilege>
<childServiceTypes>
<!-- Zero or more repetitions: -->
<string>AllInclusive</string>
</childServiceTypes>
<serviceType>AllInclusive</serviceType>
<state>InTrial</state>
<weight>Dynamic</weight>
<locationId>1</locationId>
<flags>
<!-- Zero or more
repetitions: -->
<string>HasCustomBranding</string>
</flags>
<externalCode>someinfo</externalCode>
<company>
<postAddress>
<country>US</country>
<state>NY</state>
<city>New-York</city>
<zipCode>12345</zipCode>
<address>1stAvenue, 34</address>
</postAddress>
<phoneNumber>+1(720)123-71-20</phoneNumber>
<faxNumber>+1(720)123-7120</faxNumber>
<websiteAddress>http://www.sample.com/</websiteAddress>
<legalCompanyName>Testcompany</legalCompanyName>
</company>
<comment>Somecomment</comment>
<minimalBillAmount>0</minimalBillAmount>
</partnerInfo>
</request>
</urn1:AddPartner> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:









Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'parentId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with correct
data.
Partner level is not specified
The field level is missing.
Add the field level to the request.
Partner name is invalid
The field name is empty or Fill the field with correct data.
contains only spaces.
Combination of partner
state/parent partner state is not
allowed
You specified the parent's
state that is not allowed
Fill a correct partner state in.
AddAccount()
In this cell you should fill the “AccountInfo” entity in.
Here is the description of all fields:
name: string(50). This is an account name. Optional. If you don’t specify this field, the account's
name will be generated automatically.
password: string(50). The account's password. Optional. If you don’t specify this field, the account's
password will be generated automatically.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
productId: this is a product ID. You can get it using the cell EnumerateProducts().
locationId: this is a location ID of account. You can select this ID from the cell EnumerateLocations().
If there is no country specified in this list, you should select an ID from the nearest country in this list
or you can use a location ID from his partner entity using the cell GetPartnerInfo().
expectedBackupSize: This is expected backup size in bytes for this account. You can specify any
number here.
expirationTime: this is a datetime field (ISO 8601), when an account will expire. Optional. If you don’t
specify this field, an account will be set up that will never expire.
This is an XML example:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:AddAccount>
<request>
<partnerId>6</partnerId>
<productId>1</productId>
<locationId>1</locationId>
<expectedBackupSize>0</expectedBackupSize>
<expirationTime>2013-0120T00:00:00+00:00</expirationTime>
</request>
</urn1:AddAccount> </soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element 'partnerId'.
A wrong type or an Fill this field with a correct type.
empty field.
Validation constraint violation:
occurrence violation in element
'request'.
Some required
fields are missing.
Check for missing required fields and
add them to the request with correct
data.
AddProduct()
In this cell you should fill the “ProductInfo” entity in. Here is also the description of all fields:
name: string(50). This is a product name.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo(). Products created by this
partner ID will be available to this partner and all sub-partners.






features: an array of pair strings. This is a list of product features. You can get full list of features
using the cell EnumerateFeatures().
This is an XML example:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:AddProduct>
<request>
<productInfo>
<name>Testtest
test</name>
<partnerId>6</partnerId>
<features>
<!-- Zero or more repetitions:
-->
<pair>
<first>VirtualDrive</first>
<second>1</second>
</pair>
</features>
</productInfo>
</request>
</urn1:AddProduct> </soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'parentId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with
correct data.
Product name is invalid
The field name is empty or Fill the field with correct data.
contains only spaces.
Product with same name already
exists
You specified an existent
product name
Change the product name to nonexisting one.
AddUser()
In this cell you should fill the “UserInfo” entity in.
Here is the description of all fields:
name: string(50). This is a user name.
password: string(50). This is a user password.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
roleId: this is a user role's ID. You can get a full list using the cell EnumerateUserRoles().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:AddUser>
<request>
<userInfo>
<partnerId>6</partnerId>
<name>new_user</name>
<password>AdedLgbAdeUQ#W</password>
<roleId>1</roleId>
</userInfo>
</request>
</urn1:AddUser> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Validation constraint violation:
data type mismatch in element
'parentId'.
A wrong type or an empty Fill this field with a correct type.
field.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
User role Id is not specified
The field roleId is missing. Add the field roleId to the request.
Username is invalid
The field name is empty
or contains only spaces.
Fill the field with correct data.
User role is invalid
You specified a nonexistent user role.
Specify a correct user role.
User with same name already
exists
You specified an existing
user name.
Specify a non-existing user name.
AddCustomColumn()
In this cell you should fill the “CustomColumnInfo” entity in.
Here is the description of all fields:
name: string(200). This is a custom column name.
Solution
Check for missing required fields and
add them to the request with correct
data.


valueType: now only the “string” type is possible to use.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:AddCustomColumn>
<request>
<customColumnInfo>
<partnerId>6</partnerId>
<valueType>string</valueType>
<name>new_column_test</name>
</customColumnInfo>
</request>
</urn1:AddCustomColumn> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element 'partnerId'.
A wrong type or an Fill this field with a correct type.
empty field.
Validation constraint violation:
occurrence violation in element
'request'.
Some required
fields are missing.
Check for missing required fields and
add them to the request with correct
data.
AddContactPerson()
In this cell you should fill the “contactPersonInfo” entity in.









Here is the description of all fields:
name: string(150). This is a contact person's name.
emailAddress: this is an e-mail address of the contact person.
phoneNumber: this is a phone number of the contact person.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
types: this is an array of “contactPersonType”. Optional. The “contactPersonType” could be of the
following values: “AuthorizedSigner”, “Administrative”, “Technical” and “Sales”.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:AddContactPerson>
<request>
<contactPersonInfo>
<partnerId>6</partnerId>
<types>
<contactPersonType>Technical</contactPersonType>
</types>
<name>JohnDoe</name>
<emailAddress>john.doe@sample.com</emailAddress>
<phoneNumber>123456789</phoneNumber>
</contactPersonInfo>
</request>
</urn1:AddContactPerson> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element 'partnerId'.
A wrong type or an
empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields Check for missing required fields and
are missing.
add them to request with correct data.
Contact person type is not specified
The field type is
missing.
Add the field type to the request.
AddNotificationTemplate()
In this cell you should fill the “notificationTemplate” entity in.
Here is the description of all fields:
id: this is the ID of a notification template, you should specify “0” and the ID will be generated
automatically.
name: string(50). This is a name of a notification template.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
body: string(unlimited).This is a notification template.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:AddNotificationTemplate>
<request>
<notificationTemplate>
<id>0</id>
<name>New notificationtemplate</name>
<partnerId>6</partnerId>
<body>Hello, <%Partner.Name%>!</body>
</notificationTemplate>
</urn1:AddNotificationTemplate> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:











</request>
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element 'partnerId'.
A wrong type or an Fill this field with a correct type.
empty field.
Validation constraint violation:
occurrence violation in element
'request'.
Some required
fields are missing.
Check for missing required fields and
add them to the request with correct
data.
AddNotificationRule()
In this cell you should fill the “notificationRule” entity in.
Here is the description of all fields:
id: this is the ID of a notification rule, you should specify “0” and the ID will be generated
automatically.
name: string(50). This is a name of a notification template.
entity: This is an entity of notification rules. There are 4 possible values: “Account”, ”Partner”,
”Storage”, ”User”.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
expression: string(unlimited). This is an expression of a notification rule.
predicate: This is a predicate of a notification rule. There are 6 possible predicates: “New”, ”True”,
”False”, ”Changed”, ”TrueToFalse”, ”FalseToTrue”.
schedule: string(50). This is a schedule of a notification rule. It is in the CRON format.
transportType: this is a transport type. There are 2 possible values: “Smtp”, ”AmazonSes”.
templateId: This is an ID of a notification template. You can create it using the
cell AddNotificationTemplate() or get an existing template from the list using the
cell EnumerateTemplates().
recipients: string(unlimited). These are the recipients of this rule. You can write down any amount of
recipients dividing them by a comma.
enabled: This is a flag which means whether this notification rule was enabled at the beginning or not.
You should use “true” or “false” values.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:AddNotificationRule>
<request>
<rule>
<id>0</id>
<name>New notificationRule</name>
<entity>Partner</entity>
<partnerId>6</partnerId>
<expression>Partner.state == state.registered</expression>
<predicate>FalseToTrue</predicate>
<schedule>* 5 * **</schedule>
<transportType>AmazonSes</transportType>
<templateId>19</templateId>
<recipients>test@samplesss.com</recipients>
<enabled>true</enabled>
</rule>
</request>
</urn1:AddNotificationRule> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'partnerId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Rule name is invalid
The field name is empty or Fill the field with correct data.
contains only spaces.
EnumerateUserRoles()
This is a cell without any fields.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>




<soapenv:Body>
<urn1:EnumerateUserRoles>
<request/>
</urn1:EnumerateUserRoles>
</soapenv:Body> </soapenv:Envelope>
EnumeratePermissions()
This is a cell without any fields.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:EnumeratePermissions>
<request/>
</urn1:EnumeratePermissions>
</soapenv:Body> </soapenv:Envelope>
EnumerateUsers()
Here is the description of all fields:
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo()
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:EnumerateUsers>
<request>
<partnerId>6</partnerId>
</request>
</urn1:EnumerateUsers> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'partnerId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Operation is restricted by partner
scope.
You specified partner ID
restricted by your account
rights.
Specify a partner ID depending on
your account rights.
GetUserInfo()
Here is the description of all fields:
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
name: string(50). This is a name of the user.
password: string(50). This is a password of the user.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:GetUserInfo>
<request>
<partnerId>6</partnerId>
<name>root</name>
<password>sOS0wgWvs0fdk</password>
</request>
</urn1:GetUserInfo> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element
'partnerId'.
A wrong type or an
empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Password for user 'root' is invalid.
You specified a wrong
password for the user.
Specify a correct password.
User 'test' of partner #6 not found in You specified a nonthe database
existent user.


Specify a correct user name.
ModifyUser()
In this cell you should fill the “UserInfo” entity in.
Here is the description of all fields:
id: this is a user ID. You can get it using the cell EnumerateUsers() or GetUserInfo().
name: string(50). This is a user name. Optional. If you use this field, the user name will be changed.



password: string(50). This is a user password. Optional. If you use this field, the password will be
changed.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
roleId: this is a user role ID. You can get a full list using the cell EnumerateUserRoles(). Optional. If
you fill this field in, the user role will be changed.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:ModifyUser>
<request>
<userInfo>
<id>154</id>
<partnerId>6</partnerId>
<name>test</name>
<roleId>5</roleId>
</userInfo>
</request>
</urn1:ModifyUser> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error



Cause
Solution
Validation constraint violation:
A wrong type or an empty
data type mismatch in element 'id'. field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with
correct data.
Username is invalid
The field name is empty or Fill the field with correct data.
contains only spaces.
User role is invalid
You specified a nonexistent user role.
Specify a correct user role.
User #256 not found in the
database.
You specified a nonexistent user ID.
Specify a correct user ID.
Operation is restricted by partner
scope.
You specified not yours
user ID.
Specify a correct user ID.
RemoveUser()
Here is the description of all fields:
id: this is a user ID. You can get it using the cell EnumerateUsers() or GetUserInfo().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:RemoveUser>
<request>
<id>154</id>
</request>
</urn1:RemoveUser> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element 'id'.
A wrong type or an
empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields Check for missing required fields and
are missing.
add them to the request with correct
data.
User #256 not found in the database.
You specified a nonexistent user ID.
Specify a correct user ID.
Operation is restricted by partner
scope.
You specified an
invalid user ID.
Specify a correct user ID.
ChangeAccountPassword()
Here is the description of all fields:
account: string(50). This is an account name.
newPassword: string(50). This is a new password.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:ChangeAccountPassword>
<request>
<account>test_account</account>
<newPassword>new_password</newPassword>
</request>
</urn1:ChangeAccountPassword> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error






Solution
Validation constraint violation:
Some required fields
occurrence violation in element 'request'. are missing.
Check for missing required fields
and add them to the request with
correct data.
Account‘new_account’ not found in the
database.
You specified a nonexistent account
name.
Specify a correct account name.
Operation is restricted by partner scope.
You specified an
invalid account.
Specify a correct account name.
EnumerateAccountStatistics()
In this cell you should fill the “query” entity in.
Here is the description of all fields:
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
startRecordNumber: In this field you should specify a start record number, for example, "0".
recordsCount: In this field you should specify the amount of requested records.
columns: this is an array of strings. Here is the list of column short names, which might be included in
responses, should be specified.
filter: this is a records filter. Optional. Here you can use short column names and operations like “<”,
“>”, “==”, “!=”.
orderBy: Optional. This field is used to sort the record by some columns.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:EnumerateAccountStatistics>
<request>
<query>
<partnerId>6</partnerId>
<startRecordNumber>0</startRecordNumber>
<recordsCount>100</recordsCount>
<columns>
<!-- Zero or more repetitions: -->
<string>AN</string>
<string>AR</string>
<string>US</string>
</columns>
</query>
</request>
</urn1:EnumerateAccountStatistics> </soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error

Cause
Cause
Solution
Validation constraint violation: data
A wrong type or an
type mismatch in element 'partnerId'. empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Partner #666 not found in the
database.
You specified a nonexistent partner ID.
Specify a correct partner ID.
Operation is restricted by partner
scope.
You specified an
invalid account.
Specify a correct account name.
GetAccountFeatures()
Here is the description of all fields:
account: string(50). This is an account name.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:GetAccountFeatures>
<request>
<account>test_account</account>
</request>
</urn1:GetAccountFeatures> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Validation constraint violation: data type A wrong type or an
mismatch in element 'account'.
empty field.
Solution
Fill this field with a correct type.

Validation constraint violation:
Some required fields
occurrence violation in element 'request'. are missing.
Check for missing required fields
and add them to the request with
correct data.
Account‘test_account’ not found in the
database.
You specified a nonexistent account
name.
Specify a correct account name.
Operation is restricted by partner scope.
You specified an
invalid account.
Specify a correct account name.
GetAccountInfo()
Here is the description of all fields:
account: string(50). This is an account name.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:GetAccountInfo>
<request>
<account>test_account</account>
</request>
</urn1:GetAccountInfo> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error







Cause
Solution
Validation constraint violation: data type A wrong type or an
mismatch in element 'account'.
empty field.
Fill this field with a correct type.
Validation constraint violation:
Some required fields
occurrence violation in element 'request'. are missing.
Check for missing required fields
and add them to the request with
correct data.
Account‘test_account’ not found in the
database.
You specified a nonexistent account
name.
Specify a correct account name.
Operation is restricted by partner scope.
You specified an
invalid account.
Specify a correct account name.
ModifyAccount()
In this cell you should filll the “AccountInfo” entity in.
Here is the description of all fields:
id: this is an account ID. You can get it using EnumerateAccountStatistics().
name: string(50). This is an account name. Optional.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
productId: this is a product ID. You can get it using the cell EnumerateProducts().
locationId: this is a location ID of the account. You can select a new ID from the
cell EnumerateLocations(), if there is no country in this list, you should select an ID of the nearest
country from this list or you can use the locationID from its partner's entity using the
cell GetPartnerInfo().
expectedBackupSize: This is expected backup size in bytes for this account. You can specify any
number here.
expirationTime: this is a date time field (ISO 8601), when the account will expire. Optional.
This is XML example:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:ModifyAccount>
<request>
<id>43</id>
<name>new_name</name>
<partnerId>6</partnerId>
<productId>1</productId>
<locationId>1</locationId>
<expectedBackupSize>0</expectedBackupSize>
<expirationTime>2013-01-20T00:00:00+00:00</expirationTime>
</request>
</urn1:ModifyAccount> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
A wrong type or an
Fill this field with a correct type.
type mismatch in element 'partnerId'. empty field.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Account #256 not found in the
database.
You specified a nonexistent account ID.
Specify a correct account ID.
Operation is restricted by partner
scope.
You specified an
invalid account ID.
Specify a correct account ID.
RemoveAccount()
Here is the description of all fields:





name: this is an account name. You can get it using the call EnumerateAccountStatistics().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:RemoveAccount>
<request>
<name>154</name>
</request>
</urn1:RemoveUser> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Account‘test’ not found in the
database.
You specified a nonexistent account
name.
Specify a correct account name.
Operation is restricted by partner
scope.
You specified an
invalid account name.
Specify a correct account name.
SetAccountFeatures()
Furthermore, here is the description of all the fields:
account: string(50). This is an account name. You can get it using the
cell EnumerateAccountStatistics().
features: an array of pair strings. This is a list of product features. You can get a full list of features
using the cell EnumerateFeatures().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:SetAccountFeatures>
<request>
<account>test</account>
<features>
<!-- Zero or more repetitions: -->
<pair>
<first>VirtualDrive</first>
<second>1</second>
</pair>
</features>
</request>
</urn1:SetAccountFeatures>
</soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Account‘test’ not found in the
database.
You specified a nonexistent account
name.
Specify a correct account name.
Operation is restricted by partner
scope.
You specified an
invalid account name.
Specify a correct account name.
SetAccountFeaturesById()
Here is the description of all fields:
accountId: This is an account ID. You can get it using the cell EnumerateAccountStatistics().
features: an array of pair strings. This is a list of product features. You can get a full list of features
using the cell EnumerateFeatures().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:SetAccountFeaturesById>
<request>
<accountId>421</accountId>
<features>
<!--Zero or more repetitions:-->
<pair>
<first>VirtualDrive</first>
<second>1</second>
</pair>
</features>
</request>
</urn1:SetAccountFeaturesById> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error

Solution
Validation constraint violation: data
A wrong type or an
type mismatch in element 'accountId'. empty field.
Filll this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Account#123 not found in the
database.
You specified a nonexisting account ID.
Specify a correct account ID.
Operation is restricted by partner
scope.
You specified an
invalid account ID.
Specify a correct account ID.
EnumerateContactPersons()
Here is the description of all fields:
partnerId: This is a partner ID. You can get it using the cell GetPartnerInfo().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:EnumerateContactPersons>
<request>
<partnerId>6</accountId>
</request>
</urn1:EnumerateContactPersons> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error

Cause
Cause
Solution
Validation constraint violation: data
A wrong type or an
type mismatch in element 'partnertId'. empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Partner#523 not found in the
database.
You specified a nonexistent partner ID.
Specify a correct partner ID.
Operation is restricted by partner
scope.
You specified an
invalid partner ID.
Specify a correct partner ID.
GetContactPersonInfoById()
Here is the description of all fields:
contactPersonId: This is an ID of a contact person. You can get it using the
cell EnumerateContactPersons().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:GetContactPersonInfoById>
<request>
<contactPersonId>6</contactPersonId>
</request>
</urn1:GetContactPersonInfoById>
</soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element
'contactPersonId'.
A wrong type or an
empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields
and add them to the request with
correct data.
Contact person#523 not found in the
database.
You specified a nonexistent contact
person ID.
Specify a correct ID of a contact
person.
Operation is restricted by partner scope. You specified an
invalid contact person
ID.







Specify a correct ID of a contact
person.
ModifyContactPerson()
In this cell you should fill the “contactPersonInfo” entity in.
Here is the description of all fields:
id: this is an ID of a contact person. You can get it using the cell EnumerateContactPersons()
or GetContactPersonInfoById().
name: string(150). This is a contact person's name.
emailAddress: this is an e-mail address of a contact person.
phoneNumber: this is a phone number of a contact person.
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
types: this is an array of “contactPersonType”. Optional. “contactPersonType” can be one of these
values: “AuthorizedSigner”, “Administrative”, “Technical” and “Sales”.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:ModifyContactPerson>
<request>
<contactPersonInfo>
<id>24</id>
<partnerId>6</partnerId>
<types>
<contactPersonType>Technical</contactPersonType>
</types>
<name>new_name</name>
<emailAddress>john.doe@sample.com</emailAddress>
<phoneNumber>123456789</phoneNumber>
</contactPersonInfo>
</request>
</urn1:ModifyContactPerson> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'partnerId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with correct
data.
Contact person type is not
specified
The field type is missing.
Add the field type to the request.
Contact person#523 not found in
the database.
You specified a nonexistent ID of a contact
person.
Specify a correct contact person ID.
Operation is restricted by partner
scope.
You specified an invalid
contact person ID.
Specify a correct contact person ID.
RemoveContactPerson()
Here is the description of all fields:
contactPersonId: this is an ID of a contact person. You can get it using the
cell EnumerateContactPersons() or GetContactPersonInfoById().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:RemoveContactPerson>
<request>
<contactPersonId>24</contactPersonId>
</request>
</urn1:RemoveContactPerson>
</soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data A wrong type or an empty Fill this field with a correct type.
type mismatch in element
field.
'partnerId'.


Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with
correct data.
Contact person#523 not found in
the database.
You specified a nonexistent ID of a contact
person.
Specify a correct ID of a contact
person.
Operation is restricted by partner
scope.
You specified a nonexistent ID of a contact
person.
Specify a correct ID of a contact
person.
EnumerateCustomColumns()
Here is the description of all fields:
partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"
xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa><!-- Your visa here --></urn:visa> </soapenv:Header>
<soapenv:Body>
<urn1:EnumerateCustomColumns>
<request>
<partnerId>6</partnerId>
</request>
</urn1:EnumerateCustomColumns> </soapenv:Body> </soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'partnerId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Operation is restricted by partner
scope.
You specified a partner ID
restricted by your account
rights.
Specify a partner ID depending on
your account rights.
Partner#523 not found in the
database.
You specified a nonexistent partner ID.
Specify a correct partner ID.
GetAccountCustomColumnValues()
Here is the description of all fields:
accountName: this is an account name.You can get it using the cell EnumerateAccountStatistics().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:GetAccountCustomColumnValues>
<request>
<accountName>test account</accountName>
</request>
</urn1:GetAccountCustomColumnValues>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Operation is restricted by partner You specified an account
scope.
name restricted by your
account rights.
Specify an account name
depending on your account rights.
Account‘new account’ not found
in the database.
You specified a non-existent
account name.
Specify a correct account name.
GetCustomColumnInfoById() cell.
Here is the description of all fields:
– customColumnId: this is an ID of a custom column. You can get it using the
cell EnumerateCustomColumns().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:GetCustomColumnInfoById>
<request>
<customColumnId>6</customColumnId>
</request>
</urn1:GetCustomColumnInfoById>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element
'customColumnId'.
A wrong type or an empty
field.
Fill this field with a correct
type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required
fields and add them to the
request with correct data.
Operation is restricted by partner
scope.
You specified an ID of a
custom column restricted by
your account rights.
Specify an ID of a custom
column depending on your
account rights.
Custom column #523 not found in the You specified a non-existent
database.
ID of a custom column.
Specify a correct ID of a custom
column .
ModifyCustomColumn() cell.
In this cell you should fill the “CustomColumnInfo” entity in.
Here is the description of all fields:
– id: this is an ID of a custom column. You can get it using the cell EnumerateCustomColumns().
– name: string(200).This is a name of a custom column.
– valueType: now only the “string” type is possible to use.
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135825312804E1BBF3D55BC2144E7CB6BD93B3940AE3DA013541B4E5BE15499ECF38AB3B4D</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:ModifyCustomColumn>
<request>
<customColumnInfo>
<partnerId>6</partnerId>
<valueType>string</valueType>
<name>new_namess</name>
</customColumnInfo>
</request>
</urn1:ModifyCustomColumn>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'partnerId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Operation is restricted by
partner scope.
You specified an ID of a custom Specify an ID of a custom column
column restricted by your
depending on your account rights.
account rights.
Custom column #523 not found
in the database.
You specified a non-existent ID
of a custom column.
Specify a correct ID of a custom
column.
RemoveCustomColumn() cell.
Here is the description of all fields:
– customColumnId: this is an ID of a custom column. You can get it using the
cell EnumerateCustomColumns().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:RemoveCustomColumn>
<request>
<customColumnId>6</customColumnId>
</request>
</urn1:RemoveCustomColumn>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element
'customColumnId'.
A wrong type or an empty
field.
Fill this field with a correct
type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required
fields and add them to the
request with correct data.
Operation is restricted by partner
scope.
You specified an ID of a
custom column restricted by
your account rights.
Specify an ID of a custom
column depending on your
account rights.
Custom column #523 not found in the You specified a non-existent
database.
ID of a custom column.
Specify a correct ID of a custom
column.
UpdateAccountCustomColumnValues() cell.
Here is the description of all fields:
– accountName: this is an account name. You can get it using the cell EnumerateAccountStatistics().
– customColumnValues: this is an array of column values. ‘columnValue’ consists of ‘customColumnId’
and ‘value’.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:UpdateAccountCustomColumnValues>
<request>
<accountName>test_account</accountName>
<customColumnValues>
<!--Zero or more repetitions:-->
<columnValue>
<customColumnId>45</customColumnId>
<value>New_value</value>
</columnValue>
</customColumnValues>
</request>
</urn1:UpdateAccountCustomColumnValues>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element
'customColumnId'.
A wrong type or an empty
field.
Fill this field with a correct
type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request
with correct data.
Operation is restricted by partner
scope.
You specified an account
name restricted by your
account rights.
Specify an account name
depending on your account
rights.
Account‘new account’ not found in
the database.
You specified a nonexistent account name.
Specify a correct ID of an
account name.
Custom column #523 not found in the
database.
You specified a nonexistent ID of a custom
column.
Specify a correct ID of a custom
column.
UpdateAccountCustomColumnValuesById() cell.
Here is the description of all fields:
– accountId: this is an account name. You can get it using the cell EnumerateAccountStatistics().
– customColumnValues: this is an array of column values. ‘columnValue’ consists of ‘customColumnId’
and ‘value’.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:UpdateAccountCustomColumnValuesById>
<request>
<accountId>23</accountId>
<customColumnValues>
<!--Zero or more repetitions:-->
<columnValue>
<customColumnId>45</customColumnId>
<value>New_value</value>
</columnValue>
</customColumnValues>
</request>
</urn1:UpdateAccountCustomColumnValuesById>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'accountId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
Some required fields are
missing.
Check for missing required fields
and add them to the request with
'request'.
correct data.
Operation is restricted by partner
scope.
You specified an account
name restricted by your
account rights.
Specify an account name
depending on your account rights.
Account‘new account’ not found
in the database.
You specified a non-existent
account name.
Specify a correct account name.
Custom column #523 not found in
the database.
You specified a non-existent
ID of a custom column.
Specify a correct custom column
ID.
EnumerateLocations() cell.
This is a cell without fields.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common" xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-1358347318D32CF3488D3415AA4EE03A7FD0303BF04E68BAEE0A0600A29214A5EFBEE62F6F</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:EnumerateLocations>
<request/>
</urn1:EnumerateLocations>
</soapenv:Body>
</soapenv:Envelope>
EnumerateFeatures() cell.
This is a cell without fields.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-1358347318D32CF3488D3415AA4EE03A7FD0303BF04E68BAEE0A0600A29214A5EFBEE62F6F</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:EnumerateFeatures>
<request/>
</urn1:EnumerateFeatures>
</soapenv:Body>
</soapenv:Envelope>
EnumerateProducts() cell.
Here is the description of all fields:
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
– currentPartnerOnly: this is a boolean flag ‘true’ or ‘false’.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:EnumerateProducts>
<request>
<partnerId>23</partnerId>
<currentPartnerOnly>false</currentPartnerOnly>
</request>
</urn1:EnumerateProducts>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'partnerId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Operation is restricted by partner
scope.
You specified a partner ID
restricted by your account
rights.
Specify a partner ID depending on
your account rights.
Partner#543 not found in the
database.
You specified a nonexistent partner ID.
Specify a correct partner ID.
ModifyProduct() cell.
In this cell you should fill the “ProductInfo” entity in. Here is the description of all fields:
– id: this is a product ID. You can get it from the cell EnumerateProducts().
– name: string(50). This is a product name.
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo(). Products created by
this partner ID will be available to this partner and all sub-partners.
– features: an array of pair strings. This is a list of product features. You can get a full list of features
using the cell EnumerateFeatures().
Thisis XML example:
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135825312804E1BBF3D55BC2144E7CB6BD93B3940AE3DA013541B4E5BE15499ECF38AB3B4D</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:ModifyProduct>
<request>
<productInfo>
<id>4</id>
<name>new_name</name>
<partnerId>6</partnerId>
<features>
<!--Zeroor more repetitions:-->
<pair>
<first>LocalCache</first>
<second>false</second>
</pair>
</features>
</productInfo>
</request>
</urn1:ModifyProduct>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'parentId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Product name is invalid
The field name is empty or
contains only spaces.
Fill the field with correct data.
Product with same name already
exists
You specified an existent
product name
Change the product name to a nonexistent one.
Operation is restricted by partner
scope.
You specified an ID
restricted by your account
rights.
Specify an ID depending on your
account rights.
Product#543 not found in the
You specified a non-
Specify a correct product ID.
database.
existent product ID.
RemoveProduct() cell.
Here is the description of all fields:
– productId: this is a product ID. You can get it from the cell EnumerateProducts().
This is an XML example:
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135825312804E1BBF3D55BC2144E7CB6BD93B3940AE3DA013541B4E5BE15499ECF38AB3B4D</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:RemoveProduct>
<request>
<productId>4</productId>
</request>
</urn1:RemoveProduct>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'productId'.
A wrong type or an empty Fill this field with a correct type.
field.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with
correct data.
Operation is restricted by partner
scope.
You specified an ID
restricted by your
account rights.
Specify an ID depending on your
account rights.
Product#543 not found in the
database.
You specified a nonexistent product ID.
Specify a correct product ID.
EnumeratePartners() cell.
Here is the description of all fields:
– parentPartnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
– fetchRecursively: this is a boolean value “true” or “false”. You will receive the list of all subpartners, if you specify “true”. And you will receive only one level of sub-partners, if you specify
“false”.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:iaso-com:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:EnumeratePartners>
<request>
<parentPartnerId>6</parentPartnerId>
<fetchRecursively>true</fetchRecursively>
</request>
</urn1:EnumeratePartners>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element
'parentPartnerId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
Some required fields are
missing.
Check for missing required fields
and add them to the request with
'request'.
Operation is restricted by partner
scope.
correct data.
You specified a partner ID Specify a partner ID depending on
restricted by your account your account rights.
rights.
EnumeratePartnerStateTransitions() cell.
This is a cell without fields.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:EnumeratePartnerStateTransitions>
<request>
</request>
</urn1:EnumeratePartnerStateTransitions>
</soapenv:Body>
</soapenv:Envelope>
GetPartnerInfo() cell.
Here is the description of all fields:
– name: this is a partner name.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:GetPartnerInfo>
<request>
<name>John Doe</name>
</request>
</urn1:GetPartnerInfo>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Operation is restricted by partner You specified a partner name Specify a partner name depending
scope.
restricted by your account
on your account rights.
rights.
GetPartnerInfoById() cell.
Here is the description of all fields:
– id: this is a partner ID. You can get this ID by the cell GetPartnerInfo();
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:GetPartnerInfoById>
<request>
<id>12</id>
</request>
</urn1:GetPartnerInfoById>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'id'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Operation is restricted by partner You specified a partner ID
scope.
restricted by your account
rights.
Specify a partner ID depending on
your account rights.
GetRootPartnerName() cell.
This is a cell without fields.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:GetRootPartnerName>
<request>
</request>
</urn1:GetRootPartnerName>
</soapenv:Body>
</soapenv:Envelope>
ChangePartnerState() cell.
Here is the description of all fields:
– partnerId: this is a partner ID. You can get if using the cell GetPartnerInfo().
– action: this is an action. You can get the list of actions from the
cell EnumeratePartnerStateTransitions().
– reason: a string (unlimited). This is a reason of changing a state for a partner.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-135835264467B413F74F575B949A8A570ECF1C2394BD20E2B5035BEF7A07710A18960BF909</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:ChangePartnerState>
<request>
<partnerId>12</partnerId>
<action>Reject</action>
<reason>Mistake</reason>
</request>
</urn1:ChangePartnerState>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'partnerId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields
and add them to the request with
correct data.
Operation is restricted by partner
scope.
You specified a partner ID
restricted by your account
rights.
Specify a partner ID depending on
your account rights.
ModifyPartner() cell.
In this cell you should fill the “partnerInfo” entity in. Here is the description of all fields:
– id: this is a partner ID. You can get it from the cell GetPartnerInfo().
– parentId: this is an ID of a parent partner. You can get it from the cell GetPartnerInfo().
– name: a string(70). This is a partner name.
– level: there are 4 possible types of levels, such as “Distributor”, “SubDistributor”, “Reseller” and
“EndCustomer”. You can't create a partner with an equal or higher level than their parent partner's
one.
– privelege: there are 3 different types of privileges, such as “Regular”, “Education” and “Charity”.
All of them are available for a super user of the rootpartner. In a general case “Regular” should be
used.
– childServiceTypes: it's an array of types. There is 3 possible types “AllInclusive”, “FullService” and
“SoftwareOnly”, though it depends on the types provided by the parent partner: if they provide only
“AllInclusive”, you can specify only “AllInclusive”. You can provide an empty value for this field and
in this case the partner will not be able to create sub-partners.
– serviceType: this is type of service for a partner. There are only 3 possible types “AllInclusive”,
“FullService” and “SoftwareOnly”, but it depends on the types a parent partner provides in the
field childServiceTypes.
– state: there are 3 different values that can be specified, they are “InTrial”, “Registered”,
“InProduction”. But there is one rule for “InProduction” – you can only use it if a parent partner has a
state “InProduction”.
– weight: there are 4 different weights, such as “Dynamic”, “Bronze”, “Silver”, “Gold”. All of them
are available by the IASO root account. A general account can use only “Dynamic”.
– locationId: this is an ID from a partner country. You can select this ID from the
cell EnumerateLocations(). If there is no country in this list you should select an ID from the nearest
country in this list.
– flags: this is an array of strings. There are 2 possible flags: “HasCustomBranding” and
“HasCustomUpdatePackages”. You can use both of them or leave this field to be an empty array.
– externalCode: a string(100). This field can be used to store any information of yours.
– company: this is an entity with its own sub-fields:
 postAddress: this is an entity with its own sub-fields:
•
•
•
•
•
•
country: a string(100). The name of the company’s country.
state: a string(40). The name of the state in the country the company is located.
district: a string(40). The name of the district in the company’s country.
city: a string(unlimited). The name of the company’s city.
zipCode: string(20). The zip code of the company’s city.
address: string(unlimited). The address in the company’s city.
 phoneNumber:string(unlimited). The company’s phone number.

faxNumber: string(30). The company’s fax number. Optional.

websiteAddress: string(unlimited). The company’s web address. Optional.

legalCompanyName:string(unlimited). A legal company name.

chamberOfCommerceNumber:string(unlimited). The chamber of commerce number.
Optional.

vatNumber:string(unlimited). A vat number. Optional.
 bankAccountNumber:string(unlimited). A bank account number. Optional.
– comment:string(unlimited). Any comment for this partner. Optional.
– minimalBillAmount: An internal field. You can specify “0” here.
This is an XML example:
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13582500218E0E68D06B3E4AF678C6910612BD0387608ABAB688275C25D80D07B3C7F8D654</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:ModifyPartner>
<request>
<partnerInfo>
<id>2</id>
<parentId>6</parentId>
<name>new_name</name>
<level>EndCustomer</level>
</partnerInfo>
</request>
</urn1:ModifyPartner>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'parentId'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with
correct data.
Partner name is invalid
The field name is empty or Fill the field with correct data.
contains only spaces.
RemovePartner() cell.
Here is the description of all fields:
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13584071943A85AECEFF7D7EC1091F70B480819630EF93213EE8517C6B4FB4BC522FF2899B</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:RemovePartner>
<request>
<partnerId>154</partnerId>
</request>
</urn1:RemovePartner>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
A wrong type or an
type mismatch in element 'partnerId'. empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Partner #256 not found in the
database.
You specified a nonexistent partner ID.
Specify a correct partner ID.
Operation is restricted by partner
scope.
You specified an
invalid partner ID.
Specify a correct partner ID.
EnableNotificationRule() cell.
Here is the description of all fields:
– id: this is a notification rule ID. You can get it from the cell EnumerateNotificationRules().
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
– enabled: this is a boolean value “true” or “false”.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common" xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13584071943A85AECEFF7D7EC1091F70B480819630EF93213EE8517C6B4FB4BC522FF2899B</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:EnableNotificationRule>
<request>
<id>15</id>
<partnerId>154</partnerId>
<enabled>true</enabled>
</request>
</urn1:EnableNotificationRule>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
A wrong type or an
type mismatch in element 'partnerId'. empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Partner #256 not found in the
database.
You specified a nonexistent partner ID.
Specify a correct partner ID.
Operation is restricted by partner
scope.
You specified an
invalid partner ID.
Specify a correct partner ID.
EnumerateActiveNotificationRules() cell.
Here is the description of all fields:
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common" xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13584071943A85AECEFF7D7EC1091F70B480819630EF93213EE8517C6B4FB4BC522FF2899B</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:EnumerateActiveNotificationRules>
<request>
<partnerId>154</partnerId>
</request>
</urn1:EnumerateActiveNotificationRules>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
A wrong type or an
type mismatch in element 'partnerId'. empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Partner #256 not found in the
database.
You specified a nonexistent partner ID.
Specify a correct partner ID.
Operation is restricted by partner
scope.
You specified an
invalid partner ID.
Specify a correct partner ID.
EnumerateNotificationRules() cell.
Here is the description of all fields:
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13584071943A85AECEFF7D7EC1091F70B480819630EF93213EE8517C6B4FB4BC522FF2899B</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:EnumerateNotificationRules>
<request>
<partnerId>154</partnerId>
</request>
</urn1:EnumerateNotificationRules>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
A wrong type or an
type mismatch in element 'partnerId'. empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Partner #256 not found in the
database.
You specified a nonexistent partner ID.
Specify a correct partner ID.
Operation is restricted by partner
scope.
You specified an
invalid partner ID.
Specify a correct partner ID.
EnumerateTemplates() cell.
Here is the description of all fields:
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
– partnerOnly: this is a boolean value “true” or “false”.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13584071943A85AECEFF7D7EC1091F70B480819630EF93213EE8517C6B4FB4BC522FF2899B</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:EnumerateTemplates>
<request>
<partnerId>154</partnerId>
<partnerOnly>true</partnerId>
</request>
</urn1:EnumerateTemplates>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
A wrong type or an
type mismatch in element 'partnerId'. empty field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields
are missing.
Check for missing required fields and
add them to the request with correct
data.
Partner #256 not found in the
database.
You specified a nonexistent partner ID.
Specify a correct partner ID.
Operation is restricted by partner
scope.
You specified an
invalid partner ID.
Specify a correct partner ID.
GetNotificationRule() cell.
Here is the description of all fields:
– id: this is a notification rule ID. You can get it using the cell EnumerateNotificationRules().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13584071943A85AECEFF7D7EC1091F70B480819630EF93213EE8517C6B4FB4BC522FF2899B</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:GetNotificationRule>
<request>
<id>15</id>
</request>
</urn1:GetNotificationRule>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
A wrong type or an empty Fill this field with a correct type.
data type mismatch in element 'id'. field.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with correct
data.
Notification rule #256 not found in
the database.
You specified a nonexistent notification rule
ID.
Specify a correct notification rule ID.
Operation is restricted by partner
scope.
You specified an invalid
notification rule ID.
Specify a correct notification rule ID.
GetNotificationTemplate() cell.
Here is the description of all fields:
– id: this is a notification template ID. You can get it using the cell EnumerateNotificationTemplates().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13584071943A85AECEFF7D7EC1091F70B480819630EF93213EE8517C6B4FB4BC522FF2899B</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:GetNotificationTemplate>
<request>
<id>15</id>
</request>
</urn1:GetNotificationTemplate>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'id'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with correct
data.
Notification template #256 not
found in the database.
You specified a nonexistent notification
template ID.
Specify a correct notification
template ID.
Operation is restricted by partner
scope.
You specified an invalid
notification template ID.
Specify a correct notification
template ID.
ModifyNotificationRule() call.
In this cell you should fill the “notificationRule” entity in.
Here is the description of all fields:
– id: this is an ID of a notification rule. You can get it using the cell EnumerateNotificationRules().
– name: string(50). This is a notification template's name.
– entity: This is an entity of notification rules. There are 4 possible values:
“Account”,”Partner”,”Storage”,”User”.
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
– expression: string(unlimited). This is a notification rule's expression.
– predicate: This is a notification rule's predicate. There are 6 possible predicates: “New”, ”True”,
”False”, ”Changed”, ”TrueToFalse”, ”FalseToTrue”.
– schedule: string(50). This is a notification rule's schedule in CRON format.
– transportType: this is a transport type. There are 2 possible values: “Smtp”, ”AmazonSes”.
– templateId: This is a notification template's ID, which you can create using the
cell AddNotificationTemplate() or getting an existant template from the list using the
cell EnumerateTemplates().
– recipients: string(unlimited). These are recipients of this rule. You can write down any amount of
recipients divided by a comma.
– enabled: This is a flag meaning whether this notification rule was enabled from the start or not. You
should use “true” or “false” values.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-1358347318D32CF3488D3415AA4EE03A7FD0303BF04E68BAEE0A0600A29214A5EFBEE62F6F</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:ModifyNotificationRule>
<request>
<rule>
<id>43</id>
<name>New_name</name>
</rule>
</request>
</urn1:ModifyNotificationRule>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
A wrong type or an empty
data type mismatch in element 'id'. field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with
correct data.
Rule name is invalid
The field name is empty or Fill the field with correct data.
contains only spaces.
ModifyNotificationTemplate() cell.
In this cell you should fill the “notificationTemplate” entity in.
Here is the description of all fields:
– id: this is an ID of a notification template. You can get it using the
cell EnumerateNotificationTemplates().
– name: string(50). This is a notification template's name.
– partnerId: this is a partner ID. You can get it using the cell GetPartnerInfo().
– body: string(unlimited).This is a notification template.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-1358346126D08AEB3A9789D4CF3C21AA1121FDE4935A20BDAF29E2F6230FB268D2234E1F58</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:ModifyNotificationTemplate>
<request>
<notificationTemplate>
<id>4</id>
<name>New_name</name>
</notificationTemplate>
</request>
</urn1:ModifyNotificationTemplate>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation: data
type mismatch in element 'id'.
A wrong type or an Fill this field with a correct type.
empty field.
Validation constraint violation:
occurrence violation in element
'request'.
Some required
fields are missing.
Check for missing required fields and
add them to the request with correct
data.
RemoveNotificationTemplate() cell.
Here is the description of all fields:
– id: this is a notification template ID. You can get it using the cell EnumerateNotificationTemplates().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13584071943A85AECEFF7D7EC1091F70B480819630EF93213EE8517C6B4FB4BC522FF2899B</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:RemoveNotificationTemplate>
<request>
<id>15</id>
</request>
</urn1:RemoveNotificationTemplate>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'id'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with correct
data.
Notification template #256 not
found in the database.
You specified a nonexistent notification
template ID.
Specify a correct notification
template ID.
Operation is restricted by partner
scope.
You specified an invalid
notification template ID.
Specify a correct notification
template ID.
RemoveNotificationRule() cell.
Here is the description of all fields:
– id: this is a notification rule ID. You can get it using the cell EnumerateNotificationRules().
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:common"xmlns:urn1="urn:iaso-com:cloud:mansvc">
<soapenv:Header>
<urn:visa>4-5-1-13584071943A85AECEFF7D7EC1091F70B480819630EF93213EE8517C6B4FB4BC522FF2899B</urn:visa>
</soapenv:Header>
<soapenv:Body>
<urn1:RemoveNotificationRule>
<request>
<id>15</id>
</request>
</urn1:RemoveNotificationRule>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
data type mismatch in element
'id'.
A wrong type or an empty
field.
Fill this field with a correct type.
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with correct
data.
Notification rule #256 not found in You specified a nonthe database.
existent ID of a
Specify a correct ID of a notification
rule.
notification rule.
Operation is restricted by partner
scope.
You specified an invalid
notification rule ID.
Specify a correct ID of a notification
rule.
Login() cell.
Here is the description of all fields:
– partnerName: this is a partner name.
– userName: this is a user name.
– password: this is a password.
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:urn="urn:iasocom:cloud:mansvc">
<soapenv:Header/>
<soapenv:Body>
<urn:Login>
<request>
<partnerName>TEST</partnerName>
<userName>root</userName>
<password>test_password</password>
</request>
</urn:Login>
</soapenv:Body>
</soapenv:Envelope>
The list of common errors in responses:
Error
Cause
Solution
Validation constraint violation:
occurrence violation in element
'request'.
Some required fields are
missing.
Check for missing required fields and
add them to the request with
correct data.
Unknown user name or bad
password
You specified a wrong user Specify a correct user name and a
name or a wrong
correct password
password.