Skip to main content
gembry1
Inspiring
April 4, 2019
Answered

Integration Key working w/ SOAP requests

  • April 4, 2019
  • 2 replies
  • 1259 views

Hello All,

When swapping out the old apiKey with the new Integration key I am able to pull data with my legacy SOAP requests. See the below snippet of XML.

Will this continue to work after the OAuth switch?

https://secure.echosign.com/services/EchoSignDocumentService16

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

    <soap:Body>

        <getDocuments xmlns="http://api.echosign">

            <apiKey>3AAA9999999999999999999999**Integration*key**9999999999999999999999</apiKey>

            <documentKey>12345</documentKey>

            <ns5:options xmlns:ns5="http://api.echosign" xmlns:ns4="http://dto11.api.echosign" xmlns:ns3="http://dto13.api.echosign" xmlns:ns2="http://dto9.api.echosign" xmlns="http://dto14.api.echosign" />

        </getDocuments>

    </soap:Body>

</soap:Envelope>

Thanks

This topic has been closed for replies.
Correct answer gembry1

Adobe Sign is ending support for older API authentication models - will "legacy access keys" still work ok?

It appears that the Legacy IP Keys will be fine per this thread.

2 replies

gembry1
gembry1AuthorCorrect answer
Inspiring
July 30, 2019
gembry1
gembry1Author
Inspiring
April 16, 2019

Hello Rijul Raj Khurana - Would you have any insight into this question or know who would?

Community Manager
April 17, 2019

probably, but no-one is going to tell for sure as SOAP has been deprecated for some time and no longer supported.

Try and move all legacy to REST api  as soon as you can.