Development Notes
Role of public and private keys
Party A is the third-party business caller
Party B is the service provider of ChainUp
The role of public-private key pair: Party A needs to generate a pair of public-private keys in advance when creating the application in the background, where the public key (rsa_third_pub) is provided to Party B, and the private key is kept by itself. When Party A requests the service provided by Party B, Party B encrypts the request parameters with Party B's public key and signs the original MD5 data with Party A's private key; when Party B receives the request, Party B decrypts the data with Party B's private key and checks the original MD5 data with Party A's public key.
Account Preparation
Developers need to prepare the following information.
Generate a pair of public and private keys, and submit the public key to the platform by creating an application in the background
Third-party application server IP (optional)
The information that the developer needs to save.
The private key corresponding to the public key submitted to the platform: rsa_third_pri .
The unique identifier of the created application: app_id. The public key of the application corresponding to the platform: rsa_saas_pub.
RSA public-private key production address
Production rules.
Cipher length: 2048
Key format: PKCS#8
Interface rules
| Transmission method.: | https |
|---|---|
Signature fields: | All required fields except the sign field need to be involved in the signature |
Response status code is: | 0 means successful processing, non-0 means request error or system exception |
Request address: | Domain name + interface address |
Encryption algorithm: | Java encryption and decryption demo ： https://github.com/exchange-platformApi/platformV2-java-example.git |
Interface documentation
All the POST requests below need to convert the parameters in the Query object to json strings, encrypt them as data using rsa_saas_pub, and sign the data using the rsa_third_pri private key.
this is demo
Last updated