https://netsuiteprofessionals.com logo
Join Slack
Powered by
```&lt;soapenv:Envelope xmlns:xsd='<http://www.w3....
# suitetalkapi
n
Copy code
<soapenv:Envelope xmlns:xsd='<http://www.w3.org/2001/XMLSchema>' 
    xmlns:xsi='<http://www.w3.org/2001/XMLSchema-instance>' 
    xmlns:soapenv='<http://schemas.xmlsoap.org/soap/envelope/>' 
    xmlns:tranCust='urn:<http://customers_2019_2.transactions.webservices.netsuite.com|customers_2019_2.transactions.webservices.netsuite.com>' 
    xmlns:platformCore='urn:<http://core_2019_2.platform.webservices.netsuite.com|core_2019_2.platform.webservices.netsuite.com>' 
    xmlns:platformMsgs='urn:<http://messages_2019_2.platform.webservices.netsuite.com|messages_2019_2.platform.webservices.netsuite.com>'>
    <soapenv:Header>
        <tokenPassport xsi:type="platformCore:TokenPassport">
            <account xsi:type="xsd:string">${NetId}</account>
            <consumerKey xsi:type="xsd:string">${consumerKey}</consumerKey>
            <token xsi:type="xsd:string">${tokenId}</token>
            <nonce xsi:type="xsd:string">${nonce}</nonce>
            <timestamp xsi:type="xsd:long">${timeStamp}</timestamp>
            <signature algorithm="HMAC_SHA256" xsi:type="platformCore:TokenPassportSignature">${signature}</signature>
        </tokenPassport>
    </soapenv:Header>
    <soapenv:Body>
        <get xsi:type='platformMsgs:GetRequest'>
            <baseRef xsi:type='platformCore:RecordRef' internalId='370' type='salesOrder'/>
        </get>
    </soapenv:Body>
</soapenv:Envelope>
@battk any thoughts?
b
gimmie 15 minutes while i mutate a successful request into yours
n
Ok, thank you.
b
works for me with something else that generates nonce, timestamp, and signature
you should check that the integration record is setup to allow webservices
n
Okay, wait.
By integration record you mean "Manage Integration" page?
b
n
I do not see the options to allow it for Soap.
b
Token-based Authentication
n
that's checked.
b
try posting to a restlet using postman using your tokens
if its valid, then the data for your template is somehow off
n
Okay, sure.
hmm.. receiving Invalid Login Attempt
b
are you sure you have your tokens correct
n
I regenerated the tokens
Now I get: Could not get any response
b
that sounds unusual
have you made posts to restlet before using postman?
n
Yes, I am familiar with sending request to RESTlet using POSTman..
Generated the tokens again
Invalid Login Attempt
b
try making a new integration
n
still the same.
b
dunno what to tell you
get it sorted on the restlet
then move onto suitetalk
n
Do you think it is related to the new account-specific URL?
This testdrive account is on 2019.2
b
account specific urls are not new
n
hmmm.. wait. I think let me generate the tokens all again.
still the same.
Generated new access tokens, and new integration tokens
b
do you have any working example of a restlet in your account?
n
yes. I have
b
use the tokens from that working request for suitetalk
n
RESTlet is still not working
Did it work at your end? SOAP request?
b
yup
but then again, i can send requests to restlets using the same tokens
n
Oh 😞
Yeah, I cannot send request to restlet or soap using the tokens.
am I missing any feature/preference?
b
i think you get a warning about that
n
which version are you on, 2019.2?
Is it test drive account?
b
yes
but its a leading account 2020.1
n
I am using POSTman for RESTlet. I select Oauth 1.0 under the authorization tab and add the related information leaving nonce and timestamp blank.
b
for restlets, you have to get the token ids and realm correct
n
One more thing. Using SOAP, I am seeing a failed entry under Login Audit trail. But with RESTlet, I am not seeing any failed entry.
b
and have to use a user/role that is allowed for the script audience
n
I am using Administrator role.
to generate the access token
b
is the role of the access token for administrator
n
it is
b
and the user is your user?
n
yes
b
is the restlet released or in testing
n
Restlet is released for all roles and all employees
b
there arent many variables left
the restlet sounds setup correctly
im, assuming you can fill in the 6 fields necessary in postman to send the request properly
n
consumer key and secret, token and secret, signature method, realm, version.
restlet works when access directly in the browser and sends the respond.
One more thing. Using SOAP, I am seeing a failed entry under Login Audit trail. But with RESTlet, I am not seeing any failed entry.
Is it something helpful?
b
did you get the url right?
n
yes I copied the url from my restlet deployment/
b
beyond dumb things like you have a space in one of your values somewhere
i dont have anything else for your mystery
n
hmmm, it surely is a mystery. I have work dev account at 2020.1. I was able to get the REST webservices up and running in under 15 minutes using POSTman.
I have a gut feeling it has to do something with 2019.2
thanks for your time and help. I will test on another dev account I have.
3 Views
Open in Slack
PreviousNext
Powered by