Online Business Method, System and Apparatus Based on Open Application Programming Interface

1. A method comprising: receiving a request to invoke a plurality of Application Programming Interfaces (APIs) according to a transaction request, the plurality of APIs including a first API and a second API, a first service corresponding to the first API, and a second service corresponding to the second API; determining that an invocation sequence exists among the plurality of APIs, the invocation sequence including that an invocation of the first API precedes an invocation of the second API; determining a first Internet Service Provider (ISP) server that provides the first service corresponding to the first API; sending a first invocation request to the first ISP server; receiving a service page corresponding to the transaction request returned by the first ISP server according to the first invocation request; embedding the invocation sequence of the plurality of APIs in the service page; triggering a second invocation request to a second ISP server that provides the second service corresponding to the second API according to the invocation sequence embedded in the service page; sending the second invocation request to the second ISP server; receiving via the service page a result from the second ISP server; and sending the service page to a third party development server to process the service page.

2. The method as recited in claim 1 , wherein before sending the second invocation request to the second ISP server, the method further comprises: determining, according to an invocation relationship among the plurality of APIs, that the second API needs to be invoked through the first API; sending the second invocation request to the first ISP server corresponding to the second Open API; and receiving the service page from the first ISP server corresponding to the second API in response to the second invocation request by: sending, from the first ISP server, the second invocation request to the second ISP server; and receiving a processed service page by the first ISP server.

3. The method as recited in claim 1 , further comprising embedding the service page into a page corresponding to the transaction request.

4. The method as recited in claim 1 , wherein before determining the first ISP server, the method further comprises: authenticating a user who sends the transaction request.

5. The method as recited in claim 4 , wherein the authenticating the user who sends the transaction request comprises: creating a user login identification when the user logs in successfully; and determining whether the user login identification is valid when the user login identification is updated each time when the user sends a respective transaction request.

6. An apparatus comprising: one or more data processing equipments; and one or more memories having stored thereon computer-executable components that are executable by the one or more data processing equipments to perform acts including: receiving a request to invoke a plurality of Application Programming Interfaces (APIs) from a third party development server according to a user's transaction request, the plurality of APIs including a first API and a second API, a first service corresponding to the first API, and a second service corresponding to the second API; determining that an invocation sequence exists among the plurality of APIs, the invocation sequence including that an invocation of the first API precedes an invocation of the second API; determining a first Internet Service Provider (ISP) server that provides the first service corresponding to the first API; sending a first invocation request to the first ISP server; receiving a service page corresponding to the transaction request returned by the first ISP server according to the first invocation request; embedding the invocation sequence of the plurality of APIs in the service page; receiving via the service page a result from the second ISP server; and sending the service page to the third party development server to process the service page.

7. The apparatus as recited in claim 6 , wherein the acts further include: triggering a second invocation request to a second ISP server that provides the second service corresponding to the second API according to the invocation sequence embedded in the service page; sending the second invocation request to the second ISP server; and receiving via the service page a result from the second ISP server.

8. The apparatus as recited in claim 7 , wherein the acts further include: determining whether the second API should be invoked through the first API according to an invocation relationship among the plurality of APIs before sending the second invocation request to the second ISP server; and forwarding the second invocation request to the second ISP server in an event that an analysis result of the invocation relationship analysis module is positive.

9. The apparatus as recited in claim 6 , wherein the acts further include: authenticating a user who sends the business request.

10. The apparatus as recited in claim 9 , wherein the authenticating the user who sends the transaction request includes: creating a user login certification when the user logs in successfully; and determining the user login certification is valid, wherein the user login certification is updated each time when the user sends a business request.

11. A system comprising: a transaction implementation server including: one or more data processing equipments; and one or more memories having stored thereon computer-executable instructions that are executable by the one or more data processing equipments to perform acts including: receiving a request to invoke a plurality of Application Programming Interfaces (APIs) according to a transaction request, the plurality of APIs including a first API and a second API, a first service corresponding to the first API, and a second service corresponding to the second API; determining that an invocation sequence exists among the plurality of APIs, the invocation sequence including that an invocation of the first API precedes an invocation of the second API; determining a first Internet Service Provider (ISP) server that provides the first service corresponding to the first API; sending a first invocation request to the first ISP server; receiving a service page corresponding to the transaction request returned by the first ISP server according to the first invocation request; embedding the invocation sequence of the plurality of APIs in the service page; receiving via the service page a result from the second ISP server; and sending the service page to a third party development server to process the service page.

12. The system as recited in claim 11 , wherein the acts further include sending the service page to a third party development server.

13. The system as recited in claim 11 , wherein the first ISP server returns the service page to the transaction implementation server according to the first invocation request sent by the transaction implementation server.

14. The system as recited in claim 11 , wherein the third party development server processes the service page and sends the processed service page to a user.

15. The system as recited in claim 11 , wherein the third party development server processes the service page and sends the processed service page to request a user to trigger the invocation of the second service corresponding to the second API.

16. The system as recited in claim 11 , wherein the plurality of APIs are open APIs.

17. The method as recited in claim 1 , wherein the plurality of APIs are open APIs.

18. The apparatus as recited in claim 6 , wherein the plurality of APIs are open APIs.

19. The apparatus as recited in claim 6 , wherein the acts further include sending the processed service page to a user to request the user to trigger an invocation of the second service corresponding to the second API.

20. The method as recited in claim 2 , wherein: the service page is received by the first ISP server from the second ISP server; and the service page is embedded in another service page of the second ISP server.