Application program interface analyzer for a universal interaction platform
AssigneeEntefy Inc.
InventorsAlston Ghafourifar, Philip Nathan Greenberg, Neil Achtman
Life of this patent
Estimating the term…
Abstract
An application program interface (API) analyzer that determines protocols and formats to interact with a service provider or smart device. The API analyzer identifies an API endpoint or websites for the service provider or smart device, determines a service category or device category, selects a category-specific corpus, forms a service-specific or device-specific corpus by appending information regarding the service provider or smart device to the category-specific corpus, and parses API documentation or the websites.
Claims20
A computer-implemented method of determining protocols and formats to interact with a service provider or smart device via an application program interface (API), the method comprising:
- identifying an API endpoint for the service provider or smart device;
- determining a service category or device category for the service provider or smart device;
- selecting a category-specific corpus based on the service category or device category;
- mapping one or more queries or instructions to one or more of the functions and parameters by an API analyzer;
- and
- forming a service-specific or device-specific corpus by appending the category-specific corpus to include the functions available via the API, the parameters required to request the functions, and the one or more queries or instructions mapped to the functions and parameters.
An application program interface (API) analyzer, comprising:
- one or more storage devices that store a plurality of category-specific corpuses;
- a user-interface;
- one or more processing units that:
- identify an API endpoint for a service provider or smart device;
- determine a service category or device category for the service provider or smart device;
- select one of the category-specific corpuses based on the service category or device category;
- parse API documentation to determine functions available via the API and parameters required to request the functions available via the API;
- map one or more of the functions and parameters to one or more queries or instructions;
- forming a service-specific or device-specific corpus by appending the category-specific corpus to include the functions available via the API, the parameters required to request the functions, and the one or more queries or instructions mapped to the functions and parameters;
- and
- store the service-specific or device-specific corpus in the one or more storage devices.
A non-transitory computer readable storage medium (CRSM) comprising computer executable instructions stored thereon to cause one or more processing units to:
- identify an application program interface (API) endpoint for a service provider or smart device;
- determine a service category or device category for the service provider or smart device;
- select a category-specific corpus based on the service category or device category;
- parse API documentation to determine functions available via the API and parameters required to request the functions available via the API;
- map one or more queries or instructions to one or more of the functions and parameters;
- and
- form a service-specific or device-specific corpus by appending the category-specific corpus to include the functions available via the API, the parameters required to request the functions, and the one or more queries or instructions mapped to the functions and parameters.
A non-transitory computer readable storage medium (CRSM) comprising computer executable instructions stored thereon to cause one or more processing units to:
- identify service provider websites;
- determine a service category for the service provider;
- select a category-specific corpus based on the service category;
- parse the service provider websites to extract objects that include meaningful information regarding the service provider or services offered by the service provider;
- categorize each of the extracted objects by comparing the extracted objects to a database of known data types, structures, and/or keywords and associating each of the extracted objects with a category;
- map each of the extracted objects to one or more queries;
- form a service-specific corpus by appending the category-specific corpus to include the extracted objects and the one or more queries mapped to each of the extracted objects;
- provide functionality for a user to submit one of the one or more queries;
- and
- output the extracted object mapped to the query submitted by the user.
Dependencies are inferred from the claim text.