THANK YOU SO MUCH! I was able to write a record to the recipients table. I'll pass this info to the web devs. Edit: found the field names.

Got it. I've now connected to the marketing instance and have a session token. I assume the next step is xtk:write, and that I would need to specify the @email field from recipients? Is it that simple?

Since you know, please answer one more question for me. I am also working on using the Campaign API to insert new recipients from my website (newsletter subscribers.) I assume the same session token and logon is required on the campaign server, but I'll need other methods to write the data. Do you h...

THANK YOU! I am finally getting somewhere!

ok. I just tried adding the following BEFORE the sessiontoken and and it seems I'm getting closer. <xtk:session#Logon></xtk:session> Now I'm seeing the following result: <faultcode>SOAP-ENV:Client</faultcode><faultstring xsi:type='xsd:string'>SOP-330010 The XML SOAP message is invalid (service 'Push...

Do you have an example of how to form step 1? Is it the same as step 1 but with the xtk:session#Logon somehow replacing the sessiontoken?

Hi, I'm VERY new to APIs. The part I'm not sure about is where to use xtk:session#Logon. Does it go inside the <PushEvent xmlns="urn:nms:rtEvent"> before or after the <sessiontoken>user/pass</sessiontoken>? I'm pretty sure that would be before the domevent, right? Any way you can post a full example...

Hello, it's been some time but I wanted to provide an update. Shortly after this post I had some help from a consultant who identified there was a problem with the columns selected for output. I chose columns on a link instead of the recipient. I also had a large split using data from a linked schem...

Hi, I'm on V7 and I'm having a similar issue... My GPG is not working at all though...  While I'm trying to troubleshoot, I noticed one of the files "In process" in the File history of the File Mapping.  Has anyone figured out how to stop this?

There is no approve button, but I really think it was an error caused by me removing the approval feature from the workflow. I have now rebuilt the workflow in the same way and no longer see this problem. I have stopped this workflow and will delete it. Thanks for your time.