Error response returned from Offer API when tested from SOAPUI

[SriBhargav_94]

Hello Folks,

Hope you're doing good and safe!

I am trying a Interaction API call (Propose Method) from SOAPUI and below are the details:

Request URL: https://<SERVER_NAME>/interaction/liveRcp/sms.

Where, liveRcp is Environment and sms is Offer Space. 

Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:nms:interaction"> <soapenv:Header/>
<soapenv:Body>
<Propose>
<sessiontoken>SESSION_TOKEN</sessiontoken>
<targetId>EMAIL_ID</targetId>
<maxCount>2</maxCount>
<categories></categories>
<themes></themes>
<context>
<interaction>
<inbound>true</inbound>
</interaction>
</context>
</Propose>
</soapenv:Body>
</soapenv:Envelope>

So before hitting this, I created Offer Space, Offer and published to Live successfully. But the response I am getting is as below

Response:

<SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns="http://xml.apache.org/xml-soap" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultstring>The offer space with the 'liveRcp|sms' key hasn't been published.</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

As offer space is published and present in live, unable to understand as why this error is returned.  Checked similar posts posted earlier, but no luck. Would request your help here, quick response is appreciated.

Thanks,

Sri Bhargav

[SriBhargav_94]

Folks,

Any suggestions on this ? Please help with this

@Adhiyan , @Vipul_Raghav @Jonathon_wodnicki ...

Regards,

Sri Bhargav

[SriBhargav_94]

Folks, Any update on this. Please help with your inputs!

[Jonathon_wodnicki · Accepted solution]

Hi,

Is the published offer space's internal name 'sms'?

You can check publication by querying xtk:reportHistory schema, it's where compiled spaces are output.

Thanks,

-Jon

[SriBhargav_94]

Thank you all for the inputs. I am able to resolve this error now.

Thanks,

Sri Bhargav