JiTu Open Platform API

https://open.jtjms-sa.com/#/apiDoc

Admin

JiTu Open Platform provides a standardized API for logistics services including order management,...

Tokens:901

Snippets:4

Trust Score:6.2

Update:10 months ago

Show doc for...

Tokens:

Raw

### J&T API Integration Guide

Source: https://open.jtjms-sa.com/#/apiDoc/index

This section details the process for integrating with the J&T Open Platform API, including registration, developer application, enterprise authentication, testing, and deployment.

```APIDOC
## J&T API Integration Process

### Description
This guide outlines the steps required to integrate with the J&T Open Platform API, enabling data exchange between clients and the platform.

### Integration Steps

1.  **Register User:** Sign up to become a member of the J&T Open Platform.
2.  **Apply as Developer:** Complete your developer information to become a standard developer on the platform.
3.  **Enterprise Authentication:** Fill in your company details to gain access to all API permissions, including order and electronic waybill services.
4.  **Joint Debugging and Testing:** Test the interface services in the staging environment and communicate with the API service personnel to resolve any issues.
5.  **Go Live:** After successful testing, contact the API service personnel to confirm deployment details.

## Signature Method

### Description
This section describes the signature method used for API requests, ensuring data integrity and security.

### Method Details

1.  **Protocol and Encoding:** Information is exchanged using HTTP form submission. The default character encoding is UTF-8. The data format is `application/x-www-form-urlencoded`.
2.  **Credentials:** `apiAccount` and `privateKey` are provided by the platform.
3.  **Digest Calculation:** `digest = base64(md5(JSON of business parameters + privateKey))`. Note: First, obtain the byte array by MD5 hashing, then apply Base64 encoding.
    *   **Example:** `base64(MD5({"age":18,"gender":"male","name":"张三"}123456))`
    *   If the signature is incorrect, try URL encoding the request.
4.  **Field Type Convention:** Strictly adhere to the parameter formats and sizes specified in the field tables.
5.  **Field Parsing Convention:** Required fields in the parameter fields must be provided in every API call.
6.  **Code Examples and SDKs:** Refer to the example code and SDK documentation for specific interface examples.
```

Tokens:

Raw