Expand my Community achievements bar.

Adobe Campaign User Groups are live now. Join our Adobe Campaign User Groups and connect with your local leaders!
SOLVED

Getting HTTP/1.1 403 Forbidden when I Try Transactional Messaging via SOAP UI

Avatar

Level 2

Hi All,

 

I am getting HTTP/1.1 403 Forbidden when I Try transactional messaging Via SOAP UI. Please let me know what might be the issue. Please find screenshot of the request below

BhaskarJC_0-1717478664069.png

Please help

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 7

You've to use first a logon call to your instance, like this:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:xtk:session">
    <soapenv:Header/>
    <soapenv:Body>
     <urn:Logon>
         <urn:sessiontoken></urn:sessiontoken>
         <urn:strLogin>xxxxxx</urn:strLogin>
         <urn:strPassword>xxxxxxx</urn:strPassword>
         <urn:elemParameters></urn:elemParameters>
     </urn:Logon>
 </soapenv:Body>
</soapenv:Envelope>

And with SOAPAction=xtk:session#Logon as header. 

 

it will give you a session token, which you have to use in your actual call, between sessiontoken brackets. Remember to change the header, now it must be SOAPAction=nms:rtEvent#PushEvents

 

 

If this fails, check instance url, instance users and that you're using a technical operator or one with enough rights

View solution in original post

3 Replies

Avatar

Community Advisor

@BhaskarJC 

 

If you are on v8.5 and above then you will have to use the technical operator.

 

Documentation is available here: https://experienceleague.adobe.com/en/docs/campaign/technotes-ac/tn-new/ims-migration


     Manoj
     Find me on LinkedIn

Avatar

Community Advisor

@BhaskarJC 

Your URL seems to point to mid. Please check if you have the correct URL and try again.

Also per default username/password is not enabled (excepted if you request the support to allow it), so you may need to use logon method to get the session method.

 

Thanks,

David



David Kangni

Avatar

Correct answer by
Level 7

You've to use first a logon call to your instance, like this:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:xtk:session">
    <soapenv:Header/>
    <soapenv:Body>
     <urn:Logon>
         <urn:sessiontoken></urn:sessiontoken>
         <urn:strLogin>xxxxxx</urn:strLogin>
         <urn:strPassword>xxxxxxx</urn:strPassword>
         <urn:elemParameters></urn:elemParameters>
     </urn:Logon>
 </soapenv:Body>
</soapenv:Envelope>

And with SOAPAction=xtk:session#Logon as header. 

 

it will give you a session token, which you have to use in your actual call, between sessiontoken brackets. Remember to change the header, now it must be SOAPAction=nms:rtEvent#PushEvents

 

 

If this fails, check instance url, instance users and that you're using a technical operator or one with enough rights