SOAP vs. Web API vs. REST Calls

(0) Share

Report

Posted on by DDMoore

I have heard that SOAP calls into D365 F&O will become obsolete in the future but have not found complete documentation stating this as a fact nor providing a timeframe.

Is it true that Microsoft will be obsoleting the SOAP functionality in D365 F&O? If true, when?

The alternatives being using either REST or Web API. Are either of these significantly faster or more reliable? For my purposes we have small payloads (both sending data and receiving data) but will have thousands of unique requests on an 8 hour shift. I have sent Postman calls using both SOAP and Web API and have not found much difference in timing (+/- 10 milliseconds) between these 2 protocols.

Thanks for the assistance.

I have the same question (0)

All responses (4)

Answers (1)

nunomaia 25 Moderator on at

Like (0)

Report

In some Microsoft D365 products SOAP is being deprecated.

In particular, the D365 Finance Supply Chain, I don't remember any Microsoft notification about that. Microsoft change easily change product roadmap

The biggest advantage of Rest against SAP is that you can easily build a consumer API from a third party client without having a tool to generate a SOAP proxy client.You can easily test / validate a REST endpoint from Postman.

I think It's safe for now, to keep using SOAP.

Was this reply helpful? Yes No
Martin Dráb 237,803 Most Valuable Professional on at

Like (0)

Report

I also didn't hear anything about deprecating SOAP.

Regarding Web API vs REST, it all depends on your defintion of "Web API". If you mean web API in general, then there is no point in comparing them and asking about things like performance. Web API means kinds of web services, which includes those that are designing according to the REST pattern.

If you mean ASP.NET Web API, this framework can be used to develop RESTful services, therefore asking what's faster or more reliable again doesn't make good sense.

Was this reply helpful? Yes No
DDMoore 71 on at

Like (0)

Report

My question is around the different URLs used to access D365 data.

<Dynamics URL>/soap/services/<service name> - uses a SOAP envelope

<Dynamics URL>/api/services/<service name> - uses a JSON body for the request and response. This is what I was referring to as Web API.

<Dynamics URL>/data/<table entity name> - a RESTful call.

Our app currently has SOAP calls in it. Is there a performance or Microsoft deprecation reason to update these?

Thanks again for the assistance.

Duane

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,803 Most Valuable Professional on at

Like (0)

Report

The first two are endpoint of custom services. When you create a custom service, it's available exposed through these two endpoints and the consumers can choose which one they want to use.

The third endpoint is for OData services, where public data entities are published.

Was this reply helpful? Yes No

Join the conversation

Community site session details

SOAP vs. Web API vs. REST Calls

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

SOAP vs. Web API vs. REST Calls

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates