Systems and methods for populating online applications using third party platforms
US-10095676-B2 · Oct 9, 2018 · US
US2018276053A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2018276053-A1 |
| Application number | US-201715467344-A |
| Country | US |
| Kind code | A1 |
| Filing date | Mar 23, 2017 |
| Priority date | Mar 23, 2017 |
| Publication date | Sep 27, 2018 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed are various approaches for dynamically integrating a client application with multiple third-party services. An integration service receives a request to perform an action relative to a particular third-party service from a client device. The request is received through a first application programming interface (API) generic to a plurality of third-party services. The integration service communicates with the particular third-party service to perform the action using a second API specific to the particular third-party service. The integration service sends a response to the client device through the first API. The response is based at least in part on a result of the action and includes an indication of one of a plurality of predefined user interfaces.
Opening claim text (preview).
We claim the following: 1 . A system for dynamically integrating client applications with third-party services, comprising: at least one computing device comprising a processor and a memory; and an integration service executable by the at least one computing device, the integration service causing the at least one computing device to at least: receive a request to perform an action relative to a particular third-party service from a client device, the request being received through a first application programming interface (API) generic to a plurality of third-party services; communicate with the particular third-party service to perform the action using a second API specific to the particular third-party service; and send a response to the client device through the first API, the response being based at least in part on a result of the action, the response including an indication of one of a plurality of predefined user interfaces. 2 . The system of claim 1 , wherein a user interaction with another one of the plurality of predefined user interfaces rendered by the client device causes the request to perform the action to be sent to the integration service. 3 . The system of claim 1 , wherein the client device is configured by a management service with a plurality of web code templates respectively implementing the plurality of predefined user interfaces. 4 . The system of claim 1 , wherein the request to perform the action includes a uniform resource locator (URL) and at least one parameter. 5 . The system of claim 1 , wherein the response further includes a status code and a status message. 6 . The system of claim 1 , wherein the request is generated by a client application executed on the client device, the client application being managed by a management service. 7 . The system of claim 6 , wherein the client application is an email client application, and the action is relative to an email message. 8 . The system of claim 1 , wherein the integration service further causes the at least one computing device to at least: receive a subsequent request to perform another action relative to another third-party service from the client device, the subsequent request being received through the first API; communicate with the other third-party service to perform the other action using a third API specific to the other third-party service; and send a subsequent response to the client device through the first API, the subsequent response being based at least in part on a result of the other action, the subsequent response including an indication of another one of the plurality of predefined user interfaces. 9 . A method for dynamically integrating client applications with third-party services, comprising: receiving a request to perform an action relative to a particular third-party service from a client device, the request being received through a first application programming interface (API) generic to a plurality of third-party services; communicating with the particular third-party service to perform the action using a second API specific to the particular third-party service; and sending a response to the client device through the first API, the response being based at least in part on a result of the action, the response including an indication of one of a plurality of predefined user interfaces. 10 . The method of claim 9 , further comprising configuring the client device, based at least in part on the response, to render the one of the plurality of predefined user interfaces on a display. 11 . The method of claim 9 , further comprising sending at least one user interface template to the client device before receiving the request to perform the action, wherein the at least one user interface template includes code for rendering the plurality of predefined user interfaces. 12 . The method of claim 11 , wherein the code for rendering the plurality of predefined user interfaces includes code that implements at least one callback to native code executed in the client device. 13 . The method of claim 11 , wherein the at least one user interface template is sent to the client device in response to the client device requesting the at least one user interface template as a result of processing a configuration file. 14 . The method of claim 13 , further comprising sending the configuration file to the client device as part of a device management enrollment process. 15 . The method of claim 9 , further comprising sending data encoding at least one regular expression to the client device before receiving the request to perform the action, wherein the at least one regular expression identifies at least one entity to which the action can be applied. 16 . A non-transitory computer-readable medium comprising machine-readable instructions, wherein when executed by a processor of a computing device, the machine-readable instructions cause the computing device to at least: receive a request to perform an action relative to a particular third-party service from a client device, the request being received through a first application programming interface (API) generic to a plurality of third-party services; communicate with the particular third-party service to perform the action using a second API specific to the particular third-party service; and send a response to the client device through the first API, the response being based at least in part on a result of the action, the response including an indication of one of a plurality of predefined user interfaces. 17 . The non-transitory computer-readable medium of claim 16 , wherein the machine-readable instructions further cause the computing device to at least: send a configuration file to the client device as part of a device management enrollment process; and send at least one user interface template is sent to the client device in response to the client device requesting the at least one user interface template as a result of processing the configuration file, wherein the at least one user interface template includes code for rendering the plurality of predefined user interfaces. 18 . The non-transitory computer-readable medium of claim 16 , wherein the machine-readable instructions further cause the computing device to at least send data encoding at least one regular expression to the client device before receiving the request to perform the action, wherein the at least one regular expression identifies at least one entity to which the action can be applied. 19 . The non-transitory computer-readable medium of claim 16 , wherein the request to perform the action includes a uniform resource locator (URL) and at least one parameter, and wherein the response further includes a status code and a status message. 20 . The non-transitory computer-readable medium of claim 16 , wherein a client application that generates the request is independent of the second API.
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
Electricity · mapped topic
Electricity · mapped topic
via adapters, e.g. between incompatible applications · CPC title
using third party service providers · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.