May I recommend this learning lab? https://developer.cisco.com/learning/lab/python-zeep-axl-lab/step/1 In step 4, you'll see this: line_data = { 'line' : { 'pattern' : LINEDN, 'description' : 'Test Line' , 'usage' : 'Device' , 'routePartitionName' : None } } # the ** before line_data tells the Python function to expect # an unspecified number of keyword/value pairs try : line_resp = service.addLine(**line_data) except Fault as err: etc... As you can see, I pass json as the argument, and prefix it with ** in order to tell the API to expect an unspecified number of keyword/value pairs.  There are probably other ways to pass values to the AXL API, but this always works best for me.   Check out the next page for a possible hiccup.  Sometimes there isn't a subkey name when an XML tag would have a number of sub-tags.  So I simply substitute '_value_1' for the name. A great way to predict what AXL/Zeep will understand is to run a query like getPhone or whatever, and look at what it returns.  Then use that as a general guide for what to specify.  Keep in mind, though, that you can't do a getPhone and then modify some values and then use it to do an updatePhone.  The two APIs are not mirrored - they take different json/XML structure.    phone_data = { 'phone' : { 'name' : PHONEID, 'description' : PHONEID, 'product' : 'Cisco 8821' , 'class' : 'Phone' , 'protocol' : 'SIP' , 'devicePoolName' : { '_value_1' : 'Default' }, 'commonPhoneConfigName' : { '_value_1' : 'Standard Common Phone Profile' }, What I usually do is try a request in SoapUI, and when I have it working, I convert the XML (in my head) to what it would look like as JSON.  There are ways in Python to convert the working XML to working JSON and vice versa, but I don't use them.   ... View more