Getting WSDL after version 2_4 with customer endpoint? | Community
Skip to main content
A
Anonymous
October 13, 2014
Solved

Getting WSDL after version 2_4 with customer endpoint?

  • October 13, 2014
  • 2 replies
  • 1180 views
Hi all,

I have a SOAP API endpoint ending with '2_7'.
I think it means that I could use SOAP APIs v2.7 to access data.
But when trying to get WSDL with URL 'http://app.marketo.com/soap/mktows/2_7?WSDL', I was told that 'Please use your customer specific SOAP endpoint to get the WSDL.'

Does it mean that WSDL after version 2_4 would not support a generic way to be got, or these WSDLs are supported only for specified customer?

Thanks,
Biao
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by
This is deliberate- basically we originally had a single URL which wasn't very fault tolerant and had some other scalability concerns for us. So, while we couldn't move existing users of old WSDLs (and the API), we want everyone to use something unique as the endpoint moving forward.

The content of the WSDLs are the same for every customer right now, and it's probably fine to assume they will be for quite some time, should you want to locally cache and reuse across instances.

2 replies

Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
October 13, 2014
Hi Biao,

I'm not certain why the WSDL is not available at the public URL, but you can access it for your instance specific SOAP URL.  You can access it at the following:  https://***-***-***.mktoapi.com/soap/mktows/2_7?WSDL
A
Anonymous
Accepted solution
October 13, 2014
This is deliberate- basically we originally had a single URL which wasn't very fault tolerant and had some other scalability concerns for us. So, while we couldn't move existing users of old WSDLs (and the API), we want everyone to use something unique as the endpoint moving forward.

The content of the WSDLs are the same for every customer right now, and it's probably fine to assume they will be for quite some time, should you want to locally cache and reuse across instances.
Terms & ConditionsAccessibility statement

Loading footer...