web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Unanswered

BC365 : SOAP Web Service Bad Request 400 Response : RESPONSSLProtocol : TLSv1.2

(0) ShareShare
ReportReport
Posted on by 21

Hi Experts,

I was integrating a Fedex test Web service with Business Central Wave 2 (15.2) Version SaaS.

GITHUB Link for the project -- github.com/.../FedexSrvAvail

I have created xml request and also tested that generated xml request from BC365 in SOAPUI & Postman and I got the response.

XML Request -->

<?xml version="1.0" encoding="ISO-8859-1"?>
<soapenv:Envelope xmlns:v13="">http://fedex.com/ws/vacs/v13" xmlns:soapenv="">schemas.xmlsoap.org/.../">
<soapenv:Header/>
<soapenv:Body>
<v13:ServiceAvailabilityRequest>
<v13:WebAuthenticationDetail>
<v13:UserCredential>
<v13:Key>biup8qh4BjICtpRi</v13:Key>
<v13:Password>L0BK7eUzMb75xlLInWRdaH4nI</v13:Password>
</v13:UserCredential>
</v13:WebAuthenticationDetail>
<v13:ClientDetail>
<v13:AccountNumber>510087720</v13:AccountNumber>
<v13:MeterNumber>114035650</v13:MeterNumber>
<v13:Localization>
<v13:LanguageCode>EN</v13:LanguageCode>
<v13:LocaleCode>US</v13:LocaleCode>
</v13:Localization>
</v13:ClientDetail>
<v13:TransactionDetail>
<v13:CustomerTransactionId>ServiceAvailabilityRequest</v13:CustomerTransactionId>
<v13:Localization>
<v13:LanguageCode>EN</v13:LanguageCode>
<v13:LocaleCode>US</v13:LocaleCode>
</v13:Localization>
</v13:TransactionDetail>
<v13:Version>
<v13:ServiceId>vacs</v13:ServiceId>
<v13:Major>13</v13:Major>
<v13:Intermediate>0</v13:Intermediate>
<v13:Minor>0</v13:Minor>
</v13:Version>
<v13:Origin>
<v13:PostalCode>38017</v13:PostalCode>
<v13:CountryCode>US</v13:CountryCode>
</v13:Origin>
<v13:Destination>
<v13:PostalCode>05040</v13:PostalCode>
<v13:CountryCode>BR</v13:CountryCode>
</v13:Destination>
<v13:ShipDate>2019-01-02</v13:ShipDate>
<v13:CarrierCode>FDXE</v13:CarrierCode>
</v13:ServiceAvailabilityRequest>
</soapenv:Body>
</soapenv:Envelope>

But in Business Central I am getting 400 Bad Request RESPONSSLProtocol : TLSv1.2 as Response. 

pastedimage1578899969639v2.png

In Nav, we can set Security Protocol as below.

ServicePointManager=System.Net.ServicePointManager
SecurityProtocolType=System.Net.SecurityProtocolType
ServicePointManager.SecurityProtocol := SecurityProtocolType.Tls12

I have the same question (0)
  • keoma Profile Picture
    32,729 on at

    please never publish private data like keys and passwords!

    use fiddler2 to debug the soap message and response when connecting with bc.

  • ManishKumarHataria Profile Picture
    21 on at

    Thanks for the suggestion but its my test account & Password(created free with fedex) and there is no harm if anyone access this.

    Please suggest me solution.

    I have tried debugging with BC365 and checked Response with SOAPUI & Postman and both gave me response code 200.

    In BC365 I am getting the 400 bad request.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,151

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,443 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,092 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans