Fruit Item 4th-Interface Finishing

now that you are using the Aps.net WEP API to develop the interface, you need to the interface needs to be well organized.

The interface is for the client to invoke.

Interface is actually a program on the server side, sending an HTTP request can be called.

The interface is a little bit independent.

An interface just do one thing on the line.

Interface Simple collation:

1. User Registration

Parameters: Mobile phone number password phone verification code address

2. User Login

Parameter: Phone number password

3. Get the Product List

Parameters: Classification Identification

4, access to product specific information

Parameter: Product number

5. Submit Order

Parameter: User account order contains product receipt address contact phone number

6. Get the list of user orders

Parameters: User Account

7. View Order content Information

Parameter: Order number

8. Cancellation of orders

Parameter: Order number

9. Receipt Confirmation

Parameter: Order number

10. Modify User Information

Parameters: User account phone Address

It's so much to think about. Do it slowly.

Discover the user-related features quite a bit. User registration also requires a verification code. How do you get it? Buy SMS Interface? Use a third-party authentication interface?

You can not register the code before the release time.

First pick the interface to get the product information to do it, with the user and order-independent.

Show the goods first.

Fruit Item 4th-Interface Finishing