Article ID: 128407, created on Feb 21, 2016, last review on Feb 21, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5

Symptoms

Example of such API call

# cat pem.addDomain.xml
<?xml version="1.0"?>
<methodCall>
<methodName>pem.addDomain</methodName>
<params>
<param>
<value>
<struct>
<member>
<name>subscription_id</name>
<value><int>1234567</int></value>
</member>
<member>
<name>domain_name</name>
<value><string>parallelstest.tld</string></value>
</member>
<member>
<name>registrar_status</name>
<value><int>2</int></value>
</member>
<member>
<name>hosting_type</name>
<value><int>2</int></value>
</member>   
<member>
<name>domain_parking_type</name>
<value><int>3</int></value>
</member>   
<member>
<name>path</name>
<value><string>http://hostname/~parallelstest</string></value>
</member>
</struct>
</value>
</param>
</params>
</methodCall>

where http://hostname/~parallelstest is a valid path and we can specify it as forwarding path via CCP without problems.

# curl -d@pem.addDomain.xml http://127.0.0.1:8440
<?xml version="1.0" encoding="UTF-8"?>
<methodResponse><params><param><value><struct><member><name>error_message</name><value><string>Invalid path 'http://hostname/~parallelstest' passed for hosting type '2'. Pease refer to the Parallels Automation OpenAPI documentation.</string></value></member><member><name>extype_id</name><value><i4>201</i4></value></member><member><name>module_id</name><value><string>OpenAPI</string></value></member><member><name>properties</name><value><struct><member><name>htype</name><value><string>2</string></value></member><member><name>path</name><value><string>http://hostname/~parallelstest</string></value></member></struct></value></member><member><name>status</name><value><i4>-1</i4></value></member></struct></value></param></params></methodResponse>

Cause

Product bug POA-89989

Resolution

Please, contact your TAM or PTA to trace the status of the issue. As a workaround, please submit such API call without ~ in the path and then correct it manually via CCP.

Search Words

invalid path api

forwarding

standard forward api

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF