Migrate Proofing Data

I need to export historical Proofing information from Workfront as a client transitions from a parent company’s version of Workfront to their own.

Using an OAuth2 application configured in Workfront, I’m able to access the Workfront API to export project and document information from Workfront, but it appears that the Proofing information only lives within the embedded Proof HQ instance (please correct me if I’m wrong).

Since this is not a standalone Workflow Proofing instance, but rather it’s integrated and accessed via Workfront, which uses IMS authentication, I cannot “log in” to the Proof HQ API using a user/password (I have no password in Proof HQ).

As such, I’m attempting to authenticate with Proof HQ by calling the https://api.proofhq.com/home/authentication/getsessionid.html SOAP API, but can’t seem to get it to work.  I’ve tried the following SOAP envelope:

```

`<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"                  xmlns:prou="https://soap.proofhq.com/">   <soapenv:Header/>   <soapenv:Body>      <prou:getSessionId>         <prou:EmailAddress>${email}</prou:EmailAddress         <prou:AuthToken>${apiKey}</prou:AuthToken>      </prou:getSessionId>   </soapenv:Body></soapenv:Envelope>`

```

where `email` is my username email, and `apiKey` is the API key I’ve generated from the Workfront “Customer Info” interface, but ultimately the request fails stating “Your log in details are not valid.”

Can someone help me with the following questions?

1. Am I correct in that the proofing information can ONLY be exported via the Proof HQ API, and not the Workfront API?
2. Is there a better way to be getting a Proofing session key programmatically?
3. Is it possible to find in my network traffic in Workfront a Proofing session key that I could use, rather than trying to get one at run time using the `getSessionId()` API?

The Workfront/Proofing APIs have gone thru so many iterations in recent years, with the incorporation of IMS auth being the latest iteration, so AI is giving me a lot of “confident” answers that all end up being wrong.