公开(公告)号：US20190230169A1

公开(公告)日：2019-07-25

申请号：US15879083

申请日：2018-01-24

Applicant: salesforce.com, inc.

Inventor： Kavitha Elangovan ,  Prabhjot Singh ,  Dmytro Kudriavtsev

IPC: H04L29/08 ,  H04L29/06 ,  G06F9/54

Abstract: Integrating third-party vendors' APIs is described. A system identifies a current call from a client computing system to an API associated with a third-party vendor, the current call including a configuration file for calling the API. The system determines whether a previous call was made to the API. The system determines whether part of the configuration file in the current call matches a corresponding part of a configuration file in the previous call, in response to a determination that a previous call was made to the API. The system uses a previously parsed configuration set, associated with the part of the configuration file in the current call, to configure a request in the current call and/or a response to the current call, in response to a determination that the configuration file in the current call matches the configuration file in the previous call.

公开(公告)号：US20190230081A1

公开(公告)日：2019-07-25

申请号：US15877703

申请日：2018-01-23

Applicant: salesforce.com, inc.

Inventor： Prabhjot Singh ,  Kavitha Elangovan ,  Dmytro Kudriavtsev

IPC: H04L29/06 ,  G06F9/54

Abstract: Managing authorization tokens for calling third-party vendors is described. A system identifies a current call from a client computing system to an API associated with a third-party vendor, the call including a configuration file for calling the API. The system determines, in response to a determination that a previous call was made to the API, whether a previous call was made to the API and whether a part of the configuration file in the current call matches a corresponding configuration file in the previous call. The system enables the API to authorize the current call by sending a copy of a previous authorization token to the client computing system, in response to a determination that the part of the configuration file in the current call matches the corresponding part of the configuration file in the previous call, the previous authorization being previously received from the API for the previous call.