# US 2026/0093559 A1 · Unified Application Programming Interface > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2026/0093559 A1 - Document ID: US20260093559A1 - Status: Published application - Kind: A1 - Application number: 18/900,163 - Filed: 2024-09-27 - Published: 2026-04-02 - Earliest claimed: 2024-09-27 - Assignees: Paypal, Inc. - Applicants: PayPal, Inc. - Inventors: Samuel John Parsons; Benjamin Breaux Coumes - Web page: https://patentgrep.com/patent/US20260093559A1 ## CPC - G06F 9/541: {via adapters, e.g. between incompatible applications} - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F 9/547: {Remote procedure calls [RPC]; Web services} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Techniques are disclosed relating to implementing a unified application programming interface (API) to facilitate operations across multiple service provider systems. A computer system implements a portion of the unified API that enables it to issue requests in a common format to a variety of service provider systems capable of performing operations of a particular type. The computer system receives a request to facilitate an operation of the particular type through a target service provider system and identifies an appropriate connector associated with the target service provider system based on the request. The computer system then sends a request conforming to the unified API to the identified connector to facilitate the operation at the target service provider system. The identified connector conforms content of the request into a format ingestible by the target service provider system and then forwards that request to the target service provider system for processing. ## Claims ### Claim 1 A method, comprising: implementing, by a computer system, at least a portion of a unified application programming interface (API) that enables the computer system to issue requests directed to a plurality of service provider systems capable of performing operations of a particular type, wherein the requests have a common format; receiving, by the computer system, a first request to process an operation of the particular type through a particular one of the plurality of service provider systems; identifying, by the computer system based on the first request, one of a plurality of connectors associated with the plurality of service provider systems, wherein a given connector is operable to handle requests according to a set of specifications of the unified API and interface with a respective one of the plurality of service provider systems; and sending, by the computer system, a second request conforming to the unified API to the identified connector to facilitate the operation at the particular service provider system, including conforming content of the second request to a format ingestible by the particular service provider system. ### Claim 2 (depends on 1) The method of claim 1, further comprising: receiving, by the computer system, a notification payload from the particular service provider system that is in a format ingestible by the identified connector; sending, by the computer system, the notification payload to the identified connector for processing; and receiving, by the computer system from the identified connector, a response identifying an operation status of the operation at the particular service provider system. ### Claim 3 (depends on 2) The method of claim 2, further comprising: enqueuing, by the computer system, information identifying the operation status into a notification queue that is accessible to a system of record that is operable to retrieve the information from the notification queue and update a record corresponding to the operation to have the operation status. ### Claim 4 (depends on 1) The method of claim 1, further comprising: maintaining, by the computer system, a connector store storing connector data associated with the plurality of connectors, wherein the connector data specifies, for a given one of the plurality of connectors, a set of properties associated with the given connector; and in response to receiving a request to register an additional connector, the computer system registering the additional connector, including storing additional connector data in the connector store that specifies one or more properties for the additional connector that include a network address of the additional connector. ### Claim 5 (depends on 4) The method of claim 4, wherein the additional connector data specifies: eligibility criteria indicative of which ones of a plurality of service providers are permitted to utilize the additional connector; and one or more settings that are configurable by a service provider when establishing a configuration that associates the service provider with the additional connector. ### Claim 6 (depends on 1) The method of claim 1, further comprising: receiving, by the computer system, a request to generate a first configuration with the identified connector, wherein the request specifies a set of authentication credentials for initiating the operation at the particular service provider system on behalf of a service provider; and storing, by the computer system, configuration data in association with the identified connector and the service provider, wherein the configuration data includes the set of authentication credentials, and wherein the second request to the identified connector includes the set of authentication credentials. ### Claim 7 (depends on 6) The method of claim 6, wherein the service provider is associated with a second configuration with the identified connector, wherein the first and second configurations permit the computer system to initiate operations at the particular service provider system with respect to different accounts associated with the service provider. ### Claim 8 (depends on 6) The method of claim 6, further comprising: storing, by the computer system, additional configuration data in association with the identified connector and a different service provider, wherein the additional configuration data establishes a second configuration with the identified connector and includes a different set of authentication credentials for initiating the operation at the particular service provider system on behalf of the different service provider. ### Claim 9 (depends on 1) The method of claim 1, wherein the set of specifications defined by the unified API identifies at least one security protocol for establishing secure communications between the computer system and the plurality of service provider systems via the plurality of connectors. ### Claim 10 A non-transitory computer-readable medium having program instructions stored thereon that are capable of causing a computer system to perform operations comprising: implementing at least a portion of a unified application programming interface (API) that enables the computer system to cause a plurality of service provider systems to perform operations of a particular type; receiving, from a system of record, a first request to process an operation of the particular type through a particular one of the plurality of service provider systems; generating a second request that identifies the operation and conforms to a common format of the unified API that is processable by a plurality of connectors operable to handle requests according to a set of specifications of the unified API and interface with a respective one of the plurality of service provider systems; and sending the second request to a particular one of the plurality of connectors to facilitate the operation at the particular service provider system, including conforming content of the second request to a format ingestible by the particular service provider system; receiving a response from the particular connector indicating an operation status of the operation; and updating an operation record in the system of record based on the response from the particular connector. ### Claim 11 (depends on 10) The non-transitory computer-readable medium of claim 10, wherein the operations further comprise: receiving a notification payload from the particular service provider system that is in a format ingestible by the particular connector; and subsequent to sending the notification payload to the particular connector, receiving a response identifying an operation status of the operation at the particular service provider system, wherein the updating of the operation record includes enqueuing information identifying the operation status into a notification queue that is accessible to the system of record to retrieve the information from the notification queue and update the operation record. ### Claim 12 (depends on 10) The non-transitory computer-readable medium of claim 10, wherein the operations further comprise: prior to the receiving of the first request to process the operation of the particular type: registering the particular connector, including storing connector data that specifies one or more properties for the particular connector that include a network address of the particular connector and one or more settings that are configurable by a given service provider when establishing a configuration that associates the given service provider with the particular connector; and storing configuration data in association with the particular connector and a service provider associated with the first request, wherein the configuration data includes a set of authentication credentials that permits the computer system to send the second request on behalf of the service provider. ### Claim 13 (depends on 12) The non-transitory computer-readable medium of claim 12, wherein the configuration data is associated with a configuration pertaining to the particular connector, and wherein the operations further comprise providing a control panel interface that enables the service provider to create and modify the configuration. ### Claim 14 (depends on 12) The non-transitory computer-readable medium of claim 12, wherein the configuration data is associated with multiple configurations established by the service provider that pertain to the particular connector, and wherein the multiple configurations permit the service provider to perform operations of the particular type with respect to different accounts of the service provider at the particular service provider system. ### Claim 15 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein the first request includes a JSON Web Token (JWT) that specifies a set of permissions associated with requesting ones of the plurality of service provider systems to perform operations, and wherein the operations further comprise: verifying that the JWT is valid and signed by a trusted key; and validating that a holder of the JWT has permission to request performance of the operation at the particular service provider system. ### Claim 16 A system, comprising: at least one processor; and memory having program instructions stored thereon that are executable by the at least one processor to cause the system to perform operations comprising: storing configuration data that describes a plurality of configurations for a plurality of connectors associated with a plurality of service provider systems, wherein a given connector is operable to handle requests according to a unified application programming interface (API) and interface with a respective one of the plurality of service provider systems; and receiving a first request to process an operation of a particular type through a particular one of the plurality of service provider systems; identifying, based on the first request, one of a plurality of connectors that is associated with the particular service provider system; generating, based on a particular one of the plurality of configurations that is associated with the identified connector, a second request that identifies the operation and conforms to a common format of the unified API that is processable by the identified connector; and sending the second request to the identified connector to facilitate the operation at the particular service provider system, including conforming content of the second request to a format ingestible by the particular service provider system. ### Claim 17 (depends on 16) The system of claim 16, wherein the operations further comprise: receiving a notification payload from the particular service provider system that is in a format ingestible by the particular connector but not by the system; and sending the notification payload to the identified connector for processing; and receiving, from the identified connector, a response identifying an operation status of the operation at the particular service provider system; and enqueuing information identifying the operation status into a notification queue accessible to a system of record that issued the first request. ### Claim 18 (depends on 16) The system of claim 16, wherein the operations further comprise: registering the identified connector, including storing connector data specifying a network address of the identified connector and one or more settings that are configurable by a given service provider when establishing a given configuration, wherein the particular configuration is associated with a service provider corresponding to the first request and includes a set of authentication credentials that permits the system to send the second request on behalf of the service provider. ### Claim 19 (depends on 18) The system of claim 18, wherein the service provider is associated with another configuration with the identified connector, wherein the particular configuration and the other configuration permit the system to initiate operations at the particular service provider system with respect to different accounts associated with the service provider. ### Claim 20 (depends on 16) The system of claim 16, wherein the first request specifies a set of permissions associated with requesting ones of the plurality of service provider systems to perform operations, and wherein the operations further comprise validating, based on the set of permissions, whether a service provider corresponding to the first request has permission to request performance of the operation.