I've manually constructed a SOAP request that I'm posting to the 1.1 API. This request worked fine for the 1.0, so am wondering what I'm missing.

The request is constructed as follows...

POST /api/1.2/zfapi.asmx HTTP/1.1<cr><lf>
Host: www.zenfolio.com<cr><lf>
User-Agent: Acme PhotoEdit plugin for Zenfolio<cr><lf>
Content-Type: text/xml; charset=utf-8<cr><lf>
Content-Length: calculated by Apache's HTTP client stuff<cr><lf>
SOAPAction: "http://www.zenfolio.com/api/1.1/LoadPublicProfile"<cr><lf>
X-Zenfolio-Token: = valid token<cr><lf>
<cr><lf>
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <LoadPublicProfile xmlns="http://www.zenfolio.com/api">
      <loginName>user</loginName>
    </LoadPublicProfile>
  </soap:Body>
</soap:Envelope>

...but am getting back this...

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Body>
    <soap:Fault xmlns:zf="http://www.zenfolio.com/api">
      <faultcode>zf:E_UNSPECIFIEDERROR</faultcode>
      <faultstring>Binding exception for property Zenfolio.Data.Snapshot.User+LoadByName.LoginName: Required parameter is missing.</faultstring>
      <detail />
    </soap:Fault>
  </soap:Body>
</soap:Envelope>

Any ideas?

Thanks,

Matthew

I'm reproducing this. We will try to fix it tomorrow.

It turns out what I reproduced was a different problem (now fixed).

The error message you receive would be returned if the loginName parameter is not provided. We have now fixed the error message to indicate it is a problem with the argument.

I am now getting back your modified XML response ('Value cannot be null. Parameter name : loginName'). However, I am providing this in my request. Is there something wrong with the way my SOAP body is constructed?

Thanks,

Matthew

I see some inconsistencies, although I'm not sure if they came from copying and pasting demo code:

1) You are calling API version 1.2, while SOAPAction header refers to version 1.1

2) The xmlns attribute on LoadPublicProfile should be "http://www.zenfolio.com/api/1.2"

I would suggest you capture the actual request you send with a packet sniffer, then it will be easier to tell what is wrong.

Sorry, I transcribed that part of the XML incorrectly, the 1.2 should read 1.1. I'm only trying to use the 1.1 API at this point.

I corrected the xlmns but still no luck. Looking at my original SOAP request and assuming the xlmns changes have been made and the 1.2 replaced with 1.1, am I missing something?

This was working fine with version 1.0 of the API.

Hang on, I think I had a typo, looks like your xmlns suggestion was the key. Thanks for reviewing my XML.

Nice to have custom SEO friendly page URLs implemented (the reason why I switched to 1.1).

Can we have Google AdSense templates / placeholders now too?

is this thread available in English? or maybe Fortran or COBOL for us old guys?   :)

Funny Kevin. I'm old enough to remember Fortran and COBOL, but too old to understand it anymore.

Kevin Thompson:

is this thread available in English? or maybe Fortran or COBOL for us old guys?   :)

I ran it through Google Translate and here's what it said:

So, imagine you're trying to take a shower, but you can't get the SOAP to work right.  I mean, it should be simple, right?  But you keep trying and it's just not working.  So you call up Dove and say "hey, Dove.  What's up with this SOAP?  My previous bar of SOAP was working just fine...  Now, I'm trying to take a shower, and I'm getting bubbles but there's no soapiness."

They get back to you and say "hmm... SOAP's not working for us either in certain circumstances; we'll figure it out and let you know."  A bit later, they call back.  "OK.  The problem we had with the SOAP was only applicable to the 'bath' scenario, so that's not quite what you were describing.  We've changed Physics so that in this situation, instead of getting bubbles but no soapiness, you just won't get any bubbles."

You call back.  "OK, I'm now I'm not getting any bubbles either.  But, I mean, I've gotta take a shower.  How can I get this shower going?"

"We think the problem you're running into is from holding the SOAP backwards.  You should make sure you're holding the SOAP according to the Applied Physics Interface version 1.2, not version 1.1.  You need to make sure you're holding the SOAP with the logo facing your body.  If you take a video of yourself while you're trying to shower, and then send it to us, that'll help us with the debugging process."

You call back.  "Uhh, guys, I'm pretty sure I'm holding the SOAP the right way.  I flipped it around just to be sure, and that made no difference.  This was working fine with the previous version of Physics."

"Oh, wait, now I see.  I had the text logo facing me the whole time, but it turns out I've gotta have the bird logo facing me.  OK, everything's working now and I'm getting clean already.  Thanks!"

--xsdg

Very funny, xsdg!!!!

That's just TOOOOO funny! I had been deleting your other messages on this topic, because I didn't understand a single word you said. This made PERFECT sense! Thanks for the laugh - I needed it.

 Brilliant!  I loved this, too.  Thanks for the smile..

Stephanie