...

Step 3 Start your API docking

You can now begin to integrate the etower API into your test / formal environment. For complete information on all API operations, refer to the generic

API documentation. For technical assistance, please email etowercs@walltechsystem.cn

1.2VersionandBackwardCompatibility

The API is versioned, and different major versions use different URLs. For minor version
enhancement, we may add new features/properties, but never remove or change any
existing features/properties. API clients are required to tolerant newly added properties in
response JSON.

• For example, a REST call returns JSON like{"orderId":"12345","price":69,"priceCurrency":"AUD"}

API clients are required to be insensitive to new JSON properties in the future. But the
existing 3 propertieswon’tbe removed or redefined. Should the response have a new
property in the future minor version release, the client implementation need still be able
to work.

• For example Add trackingno field   {"orderId":"12345","price":69,"priceCurrency":"AUD","trackingNo":"123456"}
  

Backward compatibility is not assured between major versions

1.3ErrorHandling

Implementation errors that can be found and prevented at development stage are
handled using HTTP status code.
The description of HTTP status code:

• HTTP 2xx indicates successful returns in terms of implementation logic;

• 4xx is client side error

Encryption example

You can directly refer to the following code samples or download the compressed package API Signature Demo.zip