US 12,105,835 B2
Efficient API with privacy protection
Jeremiah David Brazeau, Hudson, NH (US); Victor Manuel Romero Carrasco, Malaga (ES); Christopher David Boran, Burlington, MA (US); Andre Huss, San Francisco, CA (US); and Pallav Kothari, San Francisco, CA (US)
Assigned to Salesforce, Inc., San Francisco, CA (US)
Filed by salesforce.com, inc., San Francisco, CA (US)
Filed on Apr. 7, 2021, as Appl. No. 17/224,307.
Claims priority of provisional application 63/046,135, filed on Jun. 30, 2020.
Prior Publication US 2021/0406397 A1, Dec. 30, 2021
Int. Cl. G06F 21/62 (2013.01); G06F 9/54 (2006.01)
CPC G06F 21/6245 (2013.01) [G06F 9/547 (2013.01)] 15 Claims
OG exemplary drawing
 
1. A computer-implemented method for efficient application programming interface (API) processing with privacy protection, the method comprising:
receiving a combined user request for content from a client;
parsing the combined user request for content to identify a first request portion for public information, a second request portion for customized information that is customized or targeted or structured for the specific individual and that can be retrieved without personally identifying the specific individual, and a third request portion for personal information that personally identifies an individual or is presented to the individual or is protected for access by the individual, wherein parsing the user request for content to identify one or more request portions comprises: identifying the one or more request portions based on a convention associated with each request portion, the convention being learned about or from the request for the portion of content based on a number of times the content is requested;
subdividing the combined user request into the corresponding request portions based on the type of content portions being requested;
transmitting separately the first request portion, the second request portion that is customized or targeted or structured for the specific individual and that can be retrieved without personally identifying the specific individual, and the third request portion to one of a plurality of microservices based on the type of the portion of content being requested;
receiving separately a first response portion comprising the public information, a second response portion comprising the customized information that is customized or targeted or structured for the specific individual and that can be retrieved without personally identifying the specific individual, and a third response portion comprising the personal information;
determining the type of the portion of content; and
in response to determining the type of the portion of content is not personal information, separately caching the portion of content based on the type of the portion of content;
combining the first response portion, the second response portion, and the third response portion into a combined user response; and
sending the combined user response to the client.