Abstract: An application programming interface gateway receives a service request containing a voice command for invoking a first service for which the API gateway processes API calls, a manifest repository including a manifest file associated with the first service and containing a mapping from text commands to API endpoints associated with the first service, and a voice command processor that receives the voice command, converts the voice command to a converted text command, compares the converted text command to entries in the manifest, selects an entry in the manifest based on the converted text command, obtains a selected API endpoint associated with the entry in the manifest, constructs an API call to the service associated with the entry in the manifest that matches the converted text command, and issues the API call to the service.

Abstract: A web data collection and analysis system leveraging an intermediary allows for monitoring application traffic and usage patterns without deploying monitoring and analysis code to each application. Since the monitoring and analysis code is decoupled from the application, the system can also monitor and analyze legacy applications that may not be compatible with current web analytic tools. As application requests pass through the proxy server, an application traffic monitoring engine collects data from the web requests and responses. An application analytics engine analyzes the collected data and generates reports based on the analysis. The application traffic monitoring engine continually updates the collected application data as additional application traffic flows through the system. As a result, the system reflects a current status of the application traffic and usage pattern based on the flow of application requests and responses.

Abstract: When a user attempts to log in to his account from within an unsecure environment, such as a public computer or a third party application, the user is shown an anonymous token instead of a typical log in prompt to prevent the user from entering sensitive information. The anonymous token is random and is not associated with user data. The user opens a secure application associated with an authentication service to log in with appropriate credentials and provide the anonymous token. After authenticating the user, the authentication service temporarily associates user data with the anonymous token. An application within the unsecure environment, such as a browser, continuously listens for a user session associated with the anonymous token to be initiated. Once the browser detects a user session associated with the anonymous token, the browser retrieves the associated user data and automatically logs in the user.