Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
SOAP web services enable full flexibility for building operation-centric services. They provide industry-standard interoperability and channel and host pluggability.
You can use SOAP to interact with page or codeunit web services in Business Central.
Note
Support for SOAP endpoints is deprecated in Business Central and will be removed in an upcoming release. Start to move your solutions to use either ODataV4 or API pages/queries. API pages/queries are recommended.
Support for publishing Microsoft UI pages as SOAP web services will be removed in Business Central 2026 release wave 2 (version 29.0). Starting in version 26.0, Microsoft UI pages can't be published as SOAP web services unless the Feature: Disable SOAP web services on Microsoft UI pages key in Feature Management is turned off. Learn more Disable SOAP web services on Microsoft UI pages feature key.
Learn more about the removal timelines in Deprecated Features in the Platform - Clients, Server, and Database.
Note
Instead of exposing UI pages as web service endpoints, use API pages or API queries because they've been optimized for this scenario. For more information, see Writing efficient Web Services
| To | See |
|---|---|
| Review the different options for creating URIs to interact with SOAP web services. | SOAP Web Service URIs |
| Review the set of operations that are available when a page is exposed as a web service. | Basic Page Operations |
| Learn how to write code that provides a list of existing companies in a Business Central database. | Using SystemService to Find Companies |
| Ensure that field values are updated from web services. | Using Properties to Indicate Field Value Presence |
Related information
Web service performance
Troubleshoot web service errors
Web service telemetry
Basic Page Operations (for SOAP webservices)