Choosing the endpoint to use

  • Article

The Dynamics GP service provides two endpoints that applications can connect to. Several factors will determine whether you use the legacy endpoint or the native endpoint for your application.

Legacy endpoint

The legacy endpoint uses the BasicHttpBinding. Consider using the legacy endpoint in the following situations:

  • You are upgrading an application that had integrated with the Dynamics GP web service from an earlier release of Microsoft Dynamics GP.
  • You are using a development tool that supports only standard ASMX-based web services (such as those created with ASP.NET). For example, applications created with Visual Studio 2005 can connect only to ASMX-based web services, so they must use the legacy endpoint.

Native endpoint

The native endpoint uses the WSHttpBinding. Consider using the native endpoint in the following situations:

  • You are creating a new application that will integrate with the Dynamics GP web service, and your development tool supports the WSHttpBinding used for the native endpoint.
  • You need the improved performance or features of the native endpoint. The development tool you use must support the WSHttpBinding. Visual Studio 2008 and later support connections to the native endpoint.
  • You need the improved security provided by the native endpoint. By default, the data exchanged with the native endpoint is encrypted.