Internet of things (IoT) API platform

1. A method, comprising:

receiving, by a first network device in an application programming interface (API) management layer of a service provider network, a token request from an application on a user device;

monitoring, by the first network device, a group of proxy servers in the API management layer to determine workloads of the group of proxy servers in the API management layer;

generating, in response to the token request, a token that includes a time-stamp and a server identifier, the server identifier indicating a particular proxy server, of the group of proxy servers and the server identifier being assigned to balance the workloads among the group of proxy servers;

sending, by the first network device and to the application, the token;

receiving, from the application and by a second network device in the API management layer, an API call that includes the token;

validating, by the second network device, the token;

routing, by the second network device, the API call to the particular proxy server indicated by the token in response to successfully validating the token; and

providing, to the application, a bypass uniform resource locator (URL), to bypass the API management layer, for one or more types of designated API calls, wherein use of the bypass URL requires separate validation using the token.

2. The method of claim 1 , further comprising:

receiving, at a third network device in a cloud platform layer and from the application via the bypass URL, one of the one or more types of designated API calls and the token;

validating, by the third network device, the token; and

providing, by the third network device and to the application, a response to the one of the one or more types of designated API calls.

3. The method of claim 1 , wherein providing the bypass URL includes sending the bypass URL with the token.

4. The method of claim 1 , wherein providing the bypass URL includes sending the bypass URL to the application after validating the token.

5. The method of claim 1 , wherein the token includes a hash value that is generated using a one-way hash algorithm.

6. The method of claim 5 , wherein validating the token includes:

comparing the time stamp with an expiration period for the token, and

applying the one-way hash algorithm.

7. The method of claim 1 , further comprising:

redirecting the application to a URL for the first network device when the validating is not successful.

8. The method of claim 1 , further comprising:

receiving, by the second network device, another API call that includes the token but does not correspond to one of the one or more types of designated API calls;

validating, by the second network device, the token; and

directing the API call to the particular proxy server indicated in the token when the validating is successful.

9. The method of claim 1 , further comprising:

verifying, by the second network device and after receiving the API call, an availability of the particular proxy server corresponding to the server identifier.

10. The method of claim 1 , further comprising:

providing, by the particular proxy server and to the application, a response to the API call.

11. A system, comprising:

a front-door system for an API management layer including:

a network interface to communicate with one or more remote systems,

one or more first memories to store instructions, and

one or more first processors configured to execute instructions in the one or more memories to:

receive a token request from an application,

monitor a group of proxy servers in the API management layer to determine workloads of the group of proxy servers in the API management layer,

generate a token that includes a time-stamp and a server identifier, the server identifier indicating a particular proxy server, of the group of proxy servers and the server identifier being assigned to balance the workloads among the group of proxy servers,

send, to the application, the token, and

provide, to the application, a bypass uniform resource locator (URL), to bypass the API management layer, for one or more types of data-intensive API calls, wherein use of the bypass URL requires separate validation using the token; and

an API orchestration system for the API management layer including:

a second network interface to communicate with the one or more remote systems,

one or more second memories to store instructions, and

one or more second processors configured to execute instructions in the one or more second memories to:

receive an API call, that includes the token, from the application,

validate the token, and

route the API call to the particular proxy server indicated by the token in response to successfully validating the token.

12. The system of claim 11 , further comprising:

a cloud platform to:

receive, from the application and via the bypass URL, one of the one or more types of data-intensive API calls and the token;

validate the token; and

provide, to the application, a response to the one of the one or more types of data-intensive API calls.

13. The system of claim 12 , wherein providing the bypass URL includes sending the bypass URL with the token.

14. The system of claim 11 , wherein the token includes a hash value that is generated using a one-way hash algorithm.

15. The system of claim 11 , wherein validating the token includes:

comparing the time stamp with an expiration period for the token.

16. The system of claim 11 , wherein the one or more second processors of the API orchestration system are further configured to execute instructions in the one or more second memories to:

redirect the application to a URL for the front-door system when the validating is not successful.

17. The system of claim 11 , wherein the one or more second processors of the API orchestration system are further configured to execute instructions in the one or more memories to:

verify, after receiving the API call, an availability of the particular proxy server corresponding to the server identifier.

18. A non-transitory computer-readable medium including instructions, executed by one or more processors, for causing the one or more processors to:

receive a token request from an application;

monitor a group of proxy servers in an API management layer to determine workloads of the group of proxy servers in the API management layer;

generate, in response to the token request, a token that includes a time-stamp and a server identifier, the server identifier indicating a particular proxy server, of the group of proxy servers and the server identifier being assigned to balance the workloads among the group of proxy servers;

send, to the application, the token;

receive, from the application, an API call that includes the token;

validate the token;

route the API call to the particular proxy server indicated by the token when the validating is successful; and

provide, to the application, a bypass uniform resource locator (URL), to bypass the API management layer, for one or more particular types of data-intensive API calls, wherein use of the bypass URL requires separate validation using the token.

19. The non-transitory computer-readable medium of claim 18 , further comprising instructions for causing the one or more processors to:

receive another API call that includes the token but does not correspond to one of the one or more particular types of data-intensive API calls;

validate the token; and

route the API call to the particular proxy server indicated in the token in response to successfully validating the token.

20. The non-transitory computer-readable medium of claim 18 , further comprising instructions for causing the one or more processors to:

receive, from the application and via the bypass URL, one of the one or more particular types of data-intensive API calls and the token;

validate the token; and

provide, to the application, a response to the one of the one or more particular types of data-intensive API calls.