In this era of big data, l1 and l2 interfaces are needed in many places. The l1 and l2 interfaces serve as bridges between applications and databases, and are important helpers for data integration and sharing.
The l1 and l2 interfaces are suitable for all walks of life. With the continuous expansion of application scenarios, the development of l1 and l2 interfaces is also on the rise, opening up the development market of l1 and l2 interfaces.
Therefore, it is extremely important and beneficial to write a l1 and l2 interface. So, how are the l1 and l2 interfaces programmed? These elements must be mastered.
A complete l1 and l2 interface requires a complete interface document. Interface documents are essential. What are the important elements for writing interface documents?
First, interface overview, interface overview. The interface overview mainly includes business functions, reading objects, and interface documents, allowing readers to intuitively understand the functions of l1 and l2 interfaces;
Second, api permission description. It is a critical step to specify the generation of symbolic parameters;
Third, code, request clarification. When requesting an interface, the interface must be consistent with the encoding method. The main content of the interface document request description is the domain name and data format request; fourth, the interface list and status code description.
The interface list in the interface document is the most important. Among the request parameters of the interface, the meaning and type of each parameter must be explained in detail, such as interface name, interface address, and interface request.
Field names for l1 and l2 interfaces:
| field name |
type |
Remark |
| stock_exchange |
uint32 |
Stock market, 1-SH, 2-SZ |
| stock_code |
string |
Securities code |
| created_at |
int64 |
Delegated Date Timestamp (milliseconds) |
| code |
string |
Principal ID |
| price |
uint32 |
Order price |
| volume |
uint64 |
Order quantity |
| amount |
uint64 |
Turnover |
| tx_dir |
uint32 |
Trading direction: 0-unknown, 1-buy, 2-sell |
| tx_kind |
uint32 |
Transaction type: 1-market price, 2-limit price, 3-priority of the party, 10-cancellation, 11-unclear (funds/bonds have this value) |
Return example:
Proficiency in writing an l1 and l2 interface requires a skilled method. The request parameter uses GET, POST is used to update data, PUT is used to add data, and DELETE is used to delete data.
How to write the above elements of l1 and l2 interfaces is essential. At the beginning of the design, the function of the api must be clarified to keep the logic and cleanliness of the code. The security verification mechanism also needs to be resolved to prevent data from being stolen. Problems of data tampering and illegal submission arise.
If you really need to use the l2 interface, it is more practical to choose a ready-made one. If you are interested, you can contact the qq below to learn more.