# US 2025/0165635 A1 · Systems and methods for api gateway synchronization with cloud storage > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0165635 A1 - Document ID: US20250165635A1 - Status: Published application - Kind: A1 - Application number: 18/517,657 - Filed: 2023-11-22 - Published: 2025-05-22 - Earliest claimed: 2023-11-22 - Assignees: Rakuten Mobile USA LLC; Rakuten Symphony India Private Limited - Applicants: Rakuten Mobile USA LLC; Rakuten Symphony India Private Limited - Inventors: Gaurav JAIN; Mohit Goyal; Hemant Sharma; Shudhanshu Shekhar - Web page: https://patentgrep.com/patent/US20250165635A1 ## CPC - G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Provided are a method, system, and device for onboarding an API using an API gateway, the method may include: receiving, by a traffic manager (TM) module, an event message originating from an all-in-one (AIO) module of a first datacenter; receiving, by the TM module, execution plan data from a cloud storage object, wherein the execution plan data may be used to configure load throttling of an API; forwarding, by the TM module, the event message to a key manager (KM) module; receiving, by the TM module, a security file event response from the KM module; forwarding, by the TM module, the event message to an API gateway; receiving, by the TM module, an API data event response from the API gateway; and sending, by the TM module, an API onboarding response event to the AIO module of the first datacenter based on the API data event response. ## Claims ### Claim 1 A method for onboarding an API using an API gateway, the method comprising: receiving, by a traffic manager (TM) module, an event message originating from an all-in-one (AIO) module of a first datacenter; receiving, by the TM module, execution plan data from a cloud storage object, wherein the execution plan data may be used to configure load throttling of an API; forwarding, by the TM module, the event message to a key manager (KM) module; receiving, by the TM module, a security file event response from the KM module; forwarding, by the TM module, the event message to an API gateway; receiving, by the TM module, an API data event response from the API gateway; and sending, by the TM module, an API onboarding response event to the AIO module of the first datacenter based on the API data event response. ### Claim 2 (depends on 1) The method as claimed in claim 1, wherein upon receiving the API onboarding response event, the AIO module of the first datacenter is configured to send a cross cluster sync message to an AIO module of a second datacenter. ### Claim 3 (depends on 1) The method as claimed in claim 1, wherein the KM module, upon receiving the event message, is configured to request and receive security details from the cloud storage object. ### Claim 4 (depends on 1) The method as claimed in claim 1, wherein the API gateway, upon receiving the event message, is configured to request and receive the API and security details from the cloud storage. ### Claim 5 (depends on 1) The method as claimed in claim 1, wherein the AIO module of the first datacenter is configured to send the event message to the TM module after receiving an API onboarding request from a client. ### Claim 6 (depends on 1) The method as claimed in claim 1, wherein the AIO module of the first datacenter is configured to put API data, security files, and execution files in the cloud storage object after receiving an API onboarding request from a client. ### Claim 7 (depends on 1) The method as claimed in claim 1, wherein the AIO module of the first datacenter is configured to send an API onboarding response to a client after receiving the API onboarding response event. ### Claim 8 An apparatus for onboarding an API using an API gateway, wherein the apparatus is configured to: receive, by a traffic manager (TM) module, an event message originating from an all-in-one (AIO) module of a first datacenter; receive, by the TM module, execution plan data from a cloud storage object, wherein the execution plan data may be used to configure load throttling of an API; forward, by the TM module, the event message to a key manager (KM) module; receive, by the TM module, a security file event response from the KM module; forward, by the TM module, the event message to an API gateway; receive, by the TM module, an API data event response from the API gateway; and send, by the TM module, an API onboarding response event to the AIO module of the first datacenter based on the API data event response. ### Claim 9 (depends on 8) The apparatus as claimed in claim 8, wherein upon receiving the API onboarding response event, the AIO module of the first datacenter is configured to send a cross cluster sync message to an AIO module of a second datacenter. ### Claim 10 (depends on 8) The apparatus as claimed in claim 8, wherein the KM module, upon receiving the event message, is configured to request and receive security details from the cloud storage object. ### Claim 11 (depends on 8) The apparatus as claimed in claim 8, wherein the API gateway, upon receiving the event message, is configured to request and receive the API and security details from the cloud storage. ### Claim 12 (depends on 8) The apparatus as claimed in claim 8, wherein the AIO module of the first datacenter is configured to send the event message to the TM module after receiving an API onboarding request from a client. ### Claim 13 (depends on 8) The apparatus as claimed in claim 8, wherein the AIO module of the first datacenter is configured to put API data, security files, and execution files in the cloud storage object after receiving an API onboarding request from a client. ### Claim 14 (depends on 8) The apparatus as claimed in claim 8, wherein the AIO module of the first datacenter is configured to send an API onboarding response to a client after receiving the API onboarding response event. ### Claim 15 A non-transitory computer-readable recording medium having recorded thereon instructions to perform a method comprising: receiving, by a traffic manager (TM) module, an event message originating from an all-in-one (AIO) module of a first datacenter; receiving, by the TM module, execution plan data from a cloud storage object, wherein the execution plan data may be used to configure load throttling of an API; forwarding, by the TM module, the event message to a key manager (KM) module; receiving, by the TM module, a security file event response from the KM module; forwarding, by the TM module, the event message to an API gateway; receiving, by the TM module, an API data event response from the API gateway; and sending, by the TM module, an API onboarding response event to the AIO module of the first datacenter based on the API data event response. ### Claim 16 (depends on 1) The non-transitory computer-readable recording medium as claimed in claim 1, wherein upon receiving the API onboarding response event, the AIO module of the first datacenter is configured to send a cross cluster sync message to an AIO module of a second datacenter. ### Claim 17 (depends on 15) The non-transitory computer-readable recording medium as claimed in claim 15, wherein the KM module, upon receiving the event message, is configured to request and receive security details from the cloud storage object. ### Claim 18 (depends on 15) The non-transitory computer-readable recording medium as claimed in claim 15, wherein the API gateway, upon receiving the event message, is configured to request and receive the API and security details from the cloud storage. ### Claim 19 (depends on 15) The non-transitory computer-readable recording medium as claimed in claim 15, wherein the AIO module of the first datacenter is configured to send the event message to the TM module after receiving an API onboarding request from a client. ### Claim 20 (depends on 15) The non-transitory computer-readable recording medium as claimed in claim 15, wherein the AIO module of the first datacenter is configured to put API data, security files, and execution files in the cloud storage object after receiving an API onboarding request from a client.