When we first decided to provide an e-conomic API for our integration partners, it became apparent to us that we also needed to offer a much easier solution than setting up a connection to our SOAP API. So we created an SDK that wrapped all access and communication with our SOAP API in an easy to use .NET assembly.
Times change and so does what is included in a framework. Communication with a SOAP web service is much easier now than it was when we first set out, so the need for such an SDK is no longer as apparent. Furthermore, while using the SDK is easy, it unfortunately also creates an abstraction that hides what really goes on. This results in integrations that risk unknowingly using our API in less than ideal ways when it comes to, for example, the use of network bandwidth, with poor performance as a result.
The much better tooling available, when integrating with SOAP services, combined with the development of our new REST API means that we will no longer maintain our SDK. The current release (v1.4.18) which was released on May 6th 2015 is the last release of the SDK. From this date the SDK has been deprecated and we no longer advise the use of this SDK. We will no longer actively maintain this SDK.
What about the SOAP API?
The SOAP API is still supported, and we are still going to fix bugs when we find them. We are committed to supporting the many integrations that use our SOAP API and will continue to do so for a long time.
We will however not add new major functionality to our SOAP API. All new API development resources are directed towards our new REST API.
What if I find a bug in the SDK?
Contact us at firstname.lastname@example.org, and let us find out if the bug is really in the SDK or in our SOAP API. If it is in the SDK and not the SOAP API then we won’t fix it. Instead we’ll advise you to first look at our REST API to see if you can use that, or second take a look at the SOAP API to see if you can access that directly. You can use the same credentials in both SOAP and the SDK. If you use the token authentication method, then you will also be able to use those same tokens to authenticate against the REST API.
You will need to upgrade your SDK binaries to the latest version. All binaries below v1.4.18 will seize to work in the fall of 2015 when we are going to require that you include a custom X-EconomicAppIdentifier header in all requests made. This is only possible in the latest version of the SDK.
Should you have the need, then we supply several non-SDK examples here: https://github.com/e-conomic/eco-api-ex/tree/master/examples/