KR102758760B1 - Method and apparatus for providing information - Google Patents

Abstract

A method for providing information in an electronic device is disclosed. Specifically, the method for providing information in an electronic device may include: a step of verifying an inbound API request including first identification information about a requester and request information for an API (Application Programming Interface) based on information acquired from a first terminal; a step of assigning second identification information to the inbound API request; a step of verifying a service server corresponding to the inbound API request; a step of transmitting an outbound API request including the second identification information to the service server based on the inbound API request; a step of receiving an API response corresponding to the outbound API request from the service server; and a step of providing a list page for the inbound API request, the outbound API request, and the API response.

Description

METHOD AND APPARATUS FOR PROVIDING INFORMATION

Embodiments of the present specification relate to a method and device for providing information. More specifically, embodiments of the present specification relate to a method and device for managing API requests executed by a terminal and API responses obtained from multiple other servers in response thereto, and providing information to a user through a list page thereof.

Information exchange between the backend and the frontend is performed by the API (Application Programming Interface). Specifically, when the frontend requests an API to the backend, the backend can send an API response corresponding to the API request to the frontend.

Meanwhile, API requests requested by users may be provided to different servers depending on the characteristics of the requests, and it may be difficult to collectively identify them. In addition, when a function is executed on a terminal connected to a server, the front end may request multiple APIs corresponding to the function, and the back end and the front end exchange information through multiple APIs corresponding to the execution of the function. However, in cases such as when an error occurs in the execution of a function on a terminal, multiple API requests and multiple API responses must be debugged, and there was a problem that it was difficult to collectively identify API requests and API responses in an environment where the sender and receiver were diverse.

In this regard, reference can be made to prior literature such as KR102163818B1 and KR102230272B1.

The present disclosure has been proposed to solve the above-described problems, and provides a method for providing information and a device therefor.

More specifically, the present disclosure aims to provide a method and device that can collectively check API requests and API responses generated according to actions of a specific terminal by managing and storing API requests requested by a specific terminal and API responses corresponding thereto, and can check information exchanged between users through the same and perform modifications thereto.

The technical problems to be solved by this embodiment are not limited to the technical problems described above, and other technical problems can be inferred from the following embodiments.

As a technical means for achieving the above-described task, a method for providing information in an electronic device according to the first aspect of the present disclosure may include a step of confirming an inbound API request including first identification information about a requester and request information for an API (Application Programming Interface) based on information acquired from a first terminal; a step of assigning second identification information to the inbound API request; a step of confirming a service server corresponding to the inbound API request; a step of transmitting an outbound API request including the second identification information to the service server based on the inbound API request; a step of receiving an API response corresponding to the outbound API request from the service server; and a step of providing a list page for the inbound API request, the outbound API request, and the API response.

According to one embodiment, a method for providing information may further include: a step of identifying an inbound API request corresponding to a first terminal based on first identification information; a step of identifying an outbound API request and an API response corresponding to the inbound API request based on second identification information; and a step of matching the first identification information, the second identification information, the inbound API request, the outbound API request, and the API response based on the first identification information and the second identification information and storing the same in data storage.

According to one embodiment, the step of providing a list page may include: a step of identifying an inbound API request corresponding to a first terminal from among a plurality of inbound API requests stored in a data storage using first identification information; a step of identifying a set of outbound API requests and a set of API responses corresponding to the inbound API request from among a plurality of outbound API requests and a plurality of API responses stored in the data storage using second identification information; and a step of providing a list page including a first list of sets of outbound API requests matching the inbound API request and a second list of outbound API requests and API responses.

According to one embodiment, a method for providing information may be characterized by providing a second list in response to receiving an input corresponding to an API outbound API request on a first page obtained from a first terminal.

According to one embodiment, the step of verifying the service server may include the step of verifying an outbound API request having the same second identification information as the inbound API request; and the step of verifying a service server corresponding to the outbound API request.

In one embodiment, the step of providing the list page may include the step of providing the list page by displaying an inbound API request at a first level and displaying an outbound API request at a second level lower than the first level.

According to one embodiment, the step of providing a list page may include the step of providing the list page by displaying at least one of information about a file size of an outbound API request, Method information corresponding to the outbound API request, Status information corresponding to the outbound API request, information about whether mock data is used for the outbound API request, information about a transmission time of the outbound API request, information about an icon corresponding to a second list, and information about a debugging icon of the outbound API request.

According to one embodiment, the step of receiving an API response may include the step of waiting for a response to transmission of an outbound API request including second identification information; and the step of receiving an API response, which is a response to the outbound API request, from the service server.

According to one embodiment, a method for providing information may further include: identifying a set of outbound API requests corresponding to an inbound API request from a data storage based on second identification information; identifying a first outbound API request that is a duplicate outbound API among the outbound API requests included in the set; identifying a modified set by deleting the first outbound API request from the set; and, if re-identifying the inbound API request, transmitting an outbound API request of the modified set including the second identification information based on the modified set.

According to one embodiment, a method for providing information may further include: identifying a set of outbound API requests corresponding to an inbound API request from a data storage based on second identification information; identifying a first outbound API request not included in the set based on specification information about the API; identifying a modified set by adding the first outbound API request to the set; and, when re-identifying the inbound API request, transmitting an outbound API request of the modified set including the second identification information based on the modified set.

According to one embodiment, a method for providing information may further include the steps of: receiving information about an inbound API request that is determined to have an error from a first terminal; checking second identification information, URL information corresponding to the inbound API request, and time information corresponding to the inbound API request based on the information about the inbound API request; and transmitting the first identification information, the second identification information, the URL information, and the time information to the second terminal.

According to one embodiment, a method of providing information may include: receiving, from a second terminal, modified data that modifies at least one of an inbound API request, an outbound API request, and an API response; and modifying, based on the modified data, at least one of the inbound API request, the outbound API request, and the API response.

An electronic device providing information according to a second aspect of the present disclosure may include a transceiver; a storage; and a processor configured to identify an inbound API request including first identification information about a requester and request information about an API based on information acquired from a first terminal, assign second identification information to the inbound API request, identify a service server corresponding to the inbound API request, transmit an outbound API request including the second identification information to the service server based on the inbound API request, receive an API response corresponding to the outbound API request from the service server, and provide a list page for the inbound API request, the outbound API request, and the API response.

The recording medium according to the third aspect of the present disclosure may be a non-transitory computer-readable recording medium having recorded thereon a program for execution on a computer.

According to an embodiment of the present specification, an electronic device matches an API request and a corresponding API response for a specific terminal and provides them as a list page, so that when an improvement is needed related to a service of the terminal, a developer can easily check an API request or API response associated with an error through the list page and perform a test thereon.

The effects of the invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by a person skilled in the art from the description of the claims.

FIG. 1 is a drawing for explaining a system for providing information in which a method for providing information by an electronic device according to various embodiments can be implemented.
FIG. 2 is a flowchart illustrating a method for providing information according to one embodiment.
FIG. 3 is a drawing to more specifically explain an information provision system (10) according to one embodiment.
Figure 4 is a drawing showing the screen of the first terminal.
Figure 5 is a screen showing a list page displaying inbound API requests.
FIG. 6 is a screen showing a list page including a first list displaying inbound API requests and corresponding outbound API requests.
Figure 7a shows a screen for the source code of the request header of the first outbound API request (611).
Figure 7b shows a screen for the source code of an API response corresponding to the first outbound API request (611).
FIG. 8 is a diagram illustrating an embodiment of correcting an API request or API response that is identified as having an error through a first terminal and a second terminal according to one embodiment.
FIG. 9 is a diagram for explaining an embodiment of modifying a set of outbound API requests corresponding to inbound API requests.
FIGS. 10a, 10b and 10c are diagrams illustrating an example embodiment of simulating an API request and an API response.
FIG. 11 is a block diagram schematically illustrating an electronic device for providing information according to one embodiment.

The terms used in the embodiments are selected from the most widely used general terms possible while considering the functions of the present disclosure, but this may vary depending on the intention of a technician working in the field, precedents, the emergence of new technologies, etc. In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in this case, the meanings thereof will be described in detail in the corresponding description section. Therefore, the terms used in the present disclosure should be defined based on the meanings of the terms and the overall contents of the present disclosure, rather than simply the names of the terms.

When a part of the specification is said to “include” a component, this does not mean that other components are excluded, unless otherwise specifically stated, but rather that other components may be included. In addition, terms such as “part,” “module,” etc., described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware or software, or a combination of hardware and software.

The expression “at least one of a, b, and c” as used throughout the specification can encompass “a alone,” “b alone,” “c alone,” “a and b,” “a and c,” “b and c,” or “all of a, b, and c.”

The "terminal" mentioned below may be implemented as a computer or portable terminal capable of connecting to a server or other terminal via a network. Here, the computer includes, for example, a notebook, desktop, laptop, etc. equipped with a WEB Browser, and the portable terminal may include, for example, a wireless communication device that ensures portability and mobility, such as a communication-based terminal such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), and all kinds of handheld-based wireless communication devices such as a smartphone, tablet PC, etc.

Below, with reference to the attached drawings, embodiments of the present disclosure are described in detail so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein.

Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.

In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present invention belongs and are not directly related to the present invention will be omitted. This is to convey the gist of the present invention more clearly without obscuring it by omitting unnecessary explanations.

For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically illustrated. In addition, the size of each component does not entirely reflect the actual size. The same or corresponding components in each drawing are given the same reference numbers.

The advantages and features of the present invention, and the methods for achieving them, will become clear with reference to the embodiments described in detail below together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and the present embodiments are provided only to make the disclosure of the present invention complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be loaded onto a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement the function in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured article including an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing apparatus, a series of operational steps may be performed on the computer or other programmable data processing apparatus to produce a computer-executable process, so that the instructions executing the computer or other programmable data processing apparatus may also provide steps for executing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a particular logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be performed substantially concurrently, or the blocks may sometimes be performed in reverse order, depending on the functionality they perform.

FIG. 1 is a drawing for explaining a system for providing information in which a method for providing information by an electronic device according to various embodiments can be implemented.

Referring to FIG. 1, the system (10) for providing item information according to various embodiments may be implemented by various types of devices. For example, the system (10) for providing item information may include an electronic device (100), a first terminal (110), and a service server (120). The system (10) for providing item information illustrated in FIG. 1 only illustrates components related to the present embodiment. Therefore, a person having ordinary skill in the art related to the present embodiment may understand that other general-purpose components may be further included in addition to the components illustrated in FIG. 1.

Each of the electronic device (100), the first terminal (110), and the service server (120) may include a transceiver, storage, and a processor. In addition, each of the electronic device (100), the first terminal (110), and the service server (120) means a unit that processes at least one function or operation, and this may be implemented by hardware or software, or a combination of hardware and software. Meanwhile, throughout the embodiments, each of the electronic device (100) and the first terminal (110) is referred to as a separate device or server, but this may be a logically divided structure, and at least some of them may be implemented by a separate function in one device or server.

According to one embodiment, the electronic device (100), the first terminal (110), and the service server (120) may include a plurality of computer systems or computer software implemented as network servers. For example, at least some of the electronic device (100), the first terminal (110), and the service server (120) may refer to a computer system and computer software that are connected to a lower device that can communicate with another network server through a computer network such as an intranet or the Internet, receive a task execution request, perform the task accordingly, and provide the execution result. In addition, at least some of the electronic device (100), the first terminal (110), and the service server (120) may be understood as a broad concept that includes a series of application programs that can operate on a network server, and various databases built on internal or connected other nodes. For example, at least some of the electronic device (100), the first terminal (110), and the service server (120) may be implemented using a network server program provided in various ways according to an operating system such as DOS, Windows, Linux, UNIX, or MacOS.

The electronic device (100), the first terminal (110), and the service server (120) can communicate with each other through a network (not shown). The network includes a Local Area Network (LAN), a Wide Area Network (WAN), a Value Added Network (VAN), a mobile radio communication network, a satellite communication network, and a combination thereof, and is a comprehensive data communication network that allows each network component shown in FIG. 1 to communicate smoothly with each other, and may include wired Internet, wireless Internet, and a mobile radio communication network. The wireless communication may include, but is not limited to, wireless LAN (Wi-Fi), Bluetooth, Bluetooth low energy, Zigbee, WFD (Wi-Fi Direct), UWB (ultra wideband), infrared communication (IrDA, infrared Data Association), NFC (Near Field Communication), etc., for example.

According to one embodiment, a specific embodiment in which the electronic device (100) verifies an inbound API request including first identification information about a requester and request information for an API (Application Programming Interface) based on information acquired from a first terminal (110), assigns second identification information to the inbound API request, verifies a service server corresponding to the inbound API request, transmits an outbound API request including the second identification information to the service server based on the inbound API request, receives an API response corresponding to the outbound API request from the service server, and provides a list page for the inbound API request, the outbound API request, and the API response will be described in detail below.

FIG. 2 is a flowchart illustrating a method for providing information according to one embodiment.

Referring to FIG. 2, it can be clearly understood that some of the operations for providing information in an electronic device may be changed or substituted, or some of the orders between the operations may be changed, within a scope clearly understandable to a person skilled in the art to which the present invention pertains.

In step S210, the electronic device (100) can verify an inbound API request including first identification information about the requester and request information for the API based on information obtained from the first terminal.

According to one embodiment, the first terminal (110) may be an electronic device that performs various operations through an application, a program, etc. The first terminal (110) may be a mobile device or a computer device, but is not limited thereto. The first terminal (110) may transmit request information for an API and information for identifying the first terminal to the electronic device (100), and may perform a corresponding function through data obtained based on a method according to an embodiment of the present disclosure. For example, in response to a request to access a detailed page of a specific product through an e-commerce application, the first terminal (110) may obtain a page including an image, price information, discount information, etc. of the specific product, thereby displaying the page of the specific product. In order to display such a page, the e-commerce service server may receive each data from a database that manages information displayed on the page and generate a page based on this. Meanwhile, such page generation may also be generated in the terminal based on information provided by the e-commerce service server.

According to one embodiment, the electronic device (100) may obtain first identification information about the requester based on information obtained from the first terminal (110). Here, the obtained information may include information about the requester who requested the function to be performed by the first terminal (110). For example, the electronic device (100) may obtain information about a universally unique identifier (UUID) for distinguishing the requester from other users from the first terminal (110). Accordingly, the electronic device may verify identification information based on the information about the universally unique identifier obtained from the first terminal (110). The first identification information may be a universally unique identifier, but is not limited thereto. For example, the first identification information may be ID information of the requester.

According to one embodiment, the electronic device (100) can check an inbound API request including request information for an API. More specifically, the electronic device (100) can check an inbound API request including request information for at least one API required to execute a function in the first terminal (110). In addition, a plurality of inbound API requests corresponding to the function in the first terminal (110) may be configured. For example, 1) if the function in the first terminal (110) is a request for a detailed page for a specific product, 2) the inbound API request may include both a request corresponding to a menu included in all detailed pages regardless of the type of product, such as a GNB (Global Navigation bar), and a request corresponding to information on the specific product (e.g., information such as price information and quantity information).

In step S220, the electronic device (100) may assign second identification information to the inbound API request. Here, the second identification information may be information for distinguishing the inbound API request from other inbound API requests. In addition, the second identification information may be used to confirm at least one outbound API request having the same second identification information as the inbound API request. Accordingly, the electronic device (100) may sort at least one outbound API request corresponding to each of a plurality of inbound API requests corresponding to functions in the first terminal (110) based on the second identification information. By assigning the second identification information to the API request in this way, the API request provided by a specific terminal or requester can be traced, and thereby the API response corresponding to the API request can be managed in batches.

In step S230, the electronic device (100) can identify a service server corresponding to the inbound API request. More specifically, the electronic device (100) can identify an outbound API request having the same second identification information as the inbound API request, and can identify a service server corresponding to the identified outbound API request. In order to request at least one API according to at least one API request information included in the inbound API request, matching information of the inbound API request and the outbound API request may be required. As an example related to this, the electronic device (100) can identify at least one outbound API request having the same second identification information as the inbound API request by using the second identification information. Here, at least one outbound API request may correspond to at least one API request information, respectively. In addition, here, the outbound API request is a request transmitted from the electronic device (100) to the service server, and may be a part of the inbound API request.

According to one embodiment, the electronic device (100) can identify a service server to which at least one outbound API request will be transmitted. Here, the service server is a server that transmits an API response corresponding to a request received from the electronic device (100). The service server may be, but is not limited to, a web application server or a DB server. In addition, the service server may include a plurality of sub-service servers.

In step S240, the electronic device (100) can transmit an outbound API request including second identification information to the service server based on the inbound API request.

In step S250, the electronic device (100) can receive an API request corresponding to an outbound API request from a service server.

As an example of an embodiment for verifying an API request corresponding to a transmitted outbound API request, the electronic device (100) may wait for a response to the transmission of an outbound API request including second identification information, and may receive an API response, which is a response to the outbound API request, from a service server. Accordingly, the electronic device (100) may verify an outbound API request corresponding to the received API response even if the received API response does not have a separate identifier. However, the present invention is not limited thereto, and the electronic device (100) may verify an outbound API request having the same second identification information based on the second identification information included in the API response.

In step S260, the electronic device (100) can provide a list page for an inbound API request, an outbound API request, and an API response. More specifically, the electronic device (100) can identify an inbound API request corresponding to the first terminal (110) based on the first identification information, and can identify a set of outbound API requests and a set of AP responses corresponding to the inbound API request based on the second identification information. Accordingly, the electronic device (100) can provide a list including a first list for a set of API requests matching the inbound API request and a second list for the API outbound API request and the API response. A specific embodiment of providing the list page will be described in detail below.

FIG. 3 is a drawing to more specifically explain an information provision system (10) according to one embodiment.

Referring to FIG. 3, the system (10) for providing item information according to various embodiments may be implemented by various types of devices. For example, the system (10) for providing item information may include an electronic device (100), a first terminal (110), a service server (120), and a data storage (not shown). The data storage (not shown) may be a storage within the electronic device (100) or a storage external to the electronic device (100), but is not limited thereto. In addition, the data storage may be an open source-based non-relational database management system such as Redis (Remote Dictionary Server).

In step S310, the electronic device (100) can receive request information for the API from the first terminal (110). Upon receiving the request information for the API, the electronic device (100) can check an inbound API request including the request information for the API. Here, the request information for the API can correspond to a function performed in the first terminal (110).

In addition, the electronic device (100) can obtain first identification information about the requester based on the information obtained from the first terminal (110). 1) For example, if the first terminal (110) is a computer device, the electronic device (100) can obtain a universal unique identifier obtained from the first terminal (110) as the first identification information about the requester. 2) In addition, for example, if the first terminal (110) is a mobile device, the electronic device (100) can obtain a user ID (e.g., PCID) corresponding to the universal unique identifier obtained from the first terminal (110) as the first identification information about the requester.

According to one embodiment, the electronic device (100) for providing information may include Nginx and a Java Application. 1) Nginx is an open source web server program, and is a web server capable of operating servers such as HTTP and reverse proxy. More specifically, Nginx is a web server that operates in an asynchronous event-based structure, and the electronic device (100) can efficiently process traffic with fewer resources through Nginx. In addition, the electronic device (100) may operate as an electronic device that mediates the API request and API response of the present invention through Nginx. 2) Java may be one of the programming languages mainly used in the backend. The electronic device (100) may transmit at least one outbound API request having the same second identification information as the inbound API request to the service server through the Java Application.

In addition, the electronic device (100) may include a mock agent to simulate and modify parts of the outbound API request and API response that require additional testing. For example, when accessing the detailed page of a specific product through the first terminal, there may be an error in the price information, discount information, etc. of the specific product, so that information on the price of the specific product on the detailed page may not be displayed. At this time, the electronic device (100) may provide a list page that includes a function for modifying an API response corresponding to an API request for the vendor Item ID of the specific product. Accordingly, when performing an additional test, the electronic device (100) may receive a modified API response (Mocked API Response) as a response to the API request for the vendor Item ID of the specific product. Accordingly, the first terminal may display a detailed page on which information on the price of the specific product is properly displayed. In this regard, this will be examined in detail with reference to FIGS. 6 and 9.

In step S320, the electronic device (100) can match the first identification information, the second identification information, and the inbound API request and store them in the data storage. Prior to this, the electronic device (100) can assign the second identification information to the inbound API request. Accordingly, the electronic device (100) can distinguish the inbound API request from other inbound API requests based on the second identification information. The electronic device (100) can distinguish an outbound API request having the same second identification information as the inbound API request. The electronic device (100) can identify the inbound API request corresponding to the first terminal based on the first identification information, and match the second identification information with the inbound API request. Based on this matching relationship, the electronic device (100) can store the first identification information, the second identification information, and the inbound API request in the data storage.

In step S330, the electronic device (100) can check a service server corresponding to the inbound API request, and transmit at least one outbound API request corresponding to the inbound API request to the checked service server. For example, referring to FIG. 3, the electronic device (100) can transmit a first outbound API request to a service server for a first service, and can transmit a second outbound API request to a service server for a second service. In addition, the electronic device (100) can receive a first API response corresponding to the first outbound API request from the service server for the first service, and can receive a second API request corresponding to the second outbound API request from the service server for the second service.

Here, the outbound API request transmitted to the service server follows the HTTP (HyperText Transfer Protocol) convention and may include a request line, a request header, and a request body. In addition, the API response may include a Status line, a response header, and a response body in accordance with the HTTP convention. In addition, the API in the present invention may be a Rest (Representational State of Transfer) API, but is not limited thereto.

In step S340, the electronic device (100) can receive an API response from the service server (120). More specifically, the electronic device (100) can wait for a response according to transmission of the first outbound API request, and can receive a second API response, which is a response to the first outbound API request, from the service server including the first service. Accordingly, the electronic device (100) can confirm the first API response corresponding to the first outbound API request among the API responses (including the first API response and the second API response) received from the service server.

In step S350, the electronic device (100) can store an outbound API request including second identification information and a corresponding API response in data storage.

Through steps S320 and S350, the electronic device (100) can match the first identification information, the second identification information, the inbound API request, the outbound API request, and the API response based on the first identification information and the second identification information, and store them in the data storage. More specifically, the electronic device (100) can store the outbound API request and the API response in the data storage by matching the first outbound API request and the first API response, and matching the second outbound API request and the second API response. The electronic device (100) can confirm the inbound API request corresponding to the first terminal based on the first identification information, and confirm the outbound API request and the API response corresponding to the inbound API request based on the second identification information.

In step S360, the electronic device (100) can provide a list page by matching the inbound API request, the outbound API request, and the API responses. More specifically, the list page can be a list page in the working environment of the first terminal (110) by searching for the first identification information corresponding to the first terminal (110). However, the list page in the working environment of the first terminal (110) is not only confirmed in the first terminal (110).

In step S370, the electronic device (100) can also provide the list page to the second terminal. More specifically, upon receiving a request for a list page corresponding to the first identification information of the first terminal (110) from the second terminal, the electronic device (100) can also provide the list page to the second terminal. Previously, the user of the first terminal (110) can provide the first identification information corresponding to the first terminal (100) to the user of the second terminal (110).

In step S380, the electronic device (100) can provide a function corresponding to the inbound API request. For example, the electronic device (100) can generate an e-commerce related page corresponding to the request for the API based on information obtained from the service server (120) and provide it to the first terminal (110).

Figure 4 is a drawing showing the screen of the first terminal.

According to one embodiment, the first terminal (110) may be an electronic device that performs various functions and operations. More specifically, when a user executes a function related to accessing a detailed page of a 30m roll toilet paper product (hereinafter, the target item) through the first terminal (110), the first terminal (110) may display a page such as page (400). The page (400) may be divided into a plurality of areas on the page (400) that match a plurality of inbound API requests according to the execution of the function of the first terminal (110).

For example, area 1 (410) of page (400) may be an area related to breadcrumbs and may display "main menu to subcategories" for a target item. Area 2 of page (400) may include areas (421), (422), and (423), and area 2 may include an image for a target item, name information for the target item, rating information for the target item, rating number information for the target item, and price information for the target item. Area 3 (430) of page (400) may be an area related to a My Coupang icon and may display information about a requester (who may be a user of an e-commerce service). Area 4 (440) of page (400) may be an area related to discount information. Area 5 (450) of page (400) may display information about a shopping cart. Area 6 (460) of the page (400) may be an area for banner advertisements of the page (400). However, the areas of the page (400) may include areas for shipping information as well as areas 1 (410), 2, 3 (430), 4 (440), 5 (450), and 6 (460).

As described in FIG. 2, the electronic device (100) can provide a list page including a first list for a set of outbound API requests matching an inbound API request and a second list for the outbound API requests and corresponding API responses. Below, an embodiment that provides a list page corresponding to the embodiment of FIG. 4 will be described.

Figure 5 is a screen showing a list page displaying inbound API requests.

According to one embodiment, the electronic device (100) can check a plurality of inbound API requests corresponding to the execution of a function of the first terminal. In addition, the electronic device (100) can provide a list page (500) indicating a plurality of inbound API requests corresponding to the execution of a function of the first terminal. The matching relationship between the list page (500) and a plurality of areas of the page (400) displayed on the first terminal (110) is as follows.

1) The inbound API request (510) of the list page (500) is a request for breadcrumbs and may correspond to “Coupang Home, Single Life, Detergent/Toilet Paper, Toilet Paper, Premium Roll Toilet Paper (3 or more layers)” of area 1 (410) of the page (400). 2) The inbound API request (520) of the list page (500) is a request for information on an item whose vendor item ID is “5077941266” and may correspond to areas (421), (422), and (423) of the page (400). 3) The inbound API request (530) of the list page (500) is a request for user information and may correspond to area (430) of the page (400). 4) The inbound API request (540) of the list page (500) is a request for discount information for an item having a vendor item ID of "5077941266" and may correspond to area 4 (440) of the page (400). 5) The inbound API request (550) of the list page (500) is a request for a shopping cart count and may correspond to area 5 (450) of the page (400). 6) The inbound API request (560) of the list page (500) is a request for a banner related to the item "261192458" and may correspond to an advertisement for 18 rolls of toilet paper displayed in area 6 (460) of the page (400).

However, the list page (500) is not only provided to the electronic device (100). Other users can check the list page (500) that displays the inbound API request according to the function execution (execution of access to the detailed page of the target product according to FIG. 4) in the first terminal (110) by entering the first identification information, "6288215614209259755120" (570).

In addition, the electronic device (100) can use the first identification information to identify an inbound API request corresponding to the first terminal among a plurality of inbound API requests stored in the data storage, and can use the second identification information to identify a set of outbound API requests and a set of API responses corresponding to the inbound API request among a plurality of outbound API requests and a plurality of API responses stored in the data storage. Accordingly, the electronic device (100) can provide a list page including a first list for a set of outbound API requests matching the inbound API request and a second list for the outbound API requests and API responses. A specific embodiment related thereto will be described in detail with reference to FIG. 6 below.

FIG. 6 is a screen showing a list page including a first list displaying inbound API requests and corresponding outbound API requests.

According to one embodiment, the electronic device (100) may provide the list page (600) by displaying an inbound API request as a first level and displaying a corresponding outbound API request as a second level lower than the first level. For example, when an inbound API request (610) for "breadcrmb-gnbmenu" having an Index number of 12 on the list page (600) is clicked, the electronic device (100) may provide the list page (600) including List 1 for a set of outbound API requests matching the inbound API request (610). In this regard, the list page (600) may display the number of sets of outbound API requests matching the inbound API request in the Count of the row for the inbound API request. For example, the number of sets of outbound API requests matching the inbound API request (610) may be 5. A set of outbound API requests matching an inbound API request (610) may include a first outbound API request (611) for "hotketword", a second outbound API request (612) for "searchads", a third outbound API request (613) for "member", a fourth outbound API request (614) for "category-info", and a fifth outbound API request (615) for "document".

According to one embodiment, the electronic device (100) may display information about an outbound API request in a first list and provide the information by displaying it on a list page (600). The information about the outbound API request may include information about a file size of the outbound API request (631), Method information (632) corresponding to the outbound API request, Status information (633) about whether the API request is successful, Information about whether mock data is used for the outbound API request (634), Information about an icon corresponding to a second list (635), Information about a debugging icon of the outbound API request (636), and Information about a transmission time of the outbound API request (637).

1) Information (636) about the file size of the outbound API request may indicate the file size of the outbound API request. For example, the file size of the first outbound API request (611) may be 0.51KB.

The API in this invention may be a REST API (Representational State Transfer) that complies with the constraints of the REST architecture. Specifically, the API Rest architecture may mean an architecture designed to process resources via HTTP Methods. For example, the third outbound API request (613) complies with the HTTP protocol and may include a member, which is a resource. Below, 2) Method information (632) corresponding to the outbound API request, which is a Method of the HTTP protocol that means an operation on the corresponding resource, and 3) Status information (633) indicating whether the outbound API request is successful will be described in detail.

2) Method information (632) corresponding to the outbound API request may be information about the Method of the HTTP protocol. For example, i) if the Method information (632) is “GET”, the service server (120) can search for information about a REST API resource and send an API response to the electronic device (100). ii) if the Method information (632) is “POST”, the service server (120) can create a REST API resource and send an API response to the electronic device (100). iii) if the Method information (632) is “PUT”, the service server (120) can update a REST API resource and send an API response to the electronic device (100). iv) if the Method information (632) is “DELETE”, the service server (120) can delete a REST API resource or related configuration and send an API response to the electronic device (100). However, the Method information (632) is not limited to the above example. Referring to FIG. 6, the Method information of the first outbound API request (610) is "POST", so the service server (120) can create a REST API resource and send an API response to the electronic device (100).

3) Status information (633) corresponding to the outbound API request may be information on whether the outbound API request was successful according to the HTTP protocol. For example, i) if Status information (633) is "200", Status information (633) may be information that the service server (120) normally processed the outbound API request. ii) if Status information (633) is "201", Status information (633) may be information that the service server (120) normally processed the outbound API request and a new resource was created. iii) if Status information (633) is "400", Status information (633) may be information that the outbound API request is invalid and thus was not processed by the service server (120). However, Status information (633) is not limited to the above example. Referring to FIG. 6, the status information of the first outbound API request (610) is 200, indicating that the service server (120) has normally processed the first outbound API request.

4) Information (634) on whether mock data is used for the outbound API request may indicate whether mock data is used for the outbound API request and the corresponding API response. Specifically, the list page may display a slide button corresponding to the outbound API request differently depending on whether mock data is used. For example, referring to FIG. 6, information (634) on whether mock data is used for the first outbound API request (610) indicates that mock data is not used for the first outbound API request (610) and the corresponding API response.

5) Information (635) about an icon corresponding to the second list may correspond to a second list for an outbound API request and a corresponding API response. For example, in response to an input through a view button of a first outbound API request (611) displayed on a list page (600), the electronic device (100) may provide a second list for an outbound API request and a corresponding API response.

6) Information (636) on the debugging icon of the outbound API request can be used when debugging the corresponding outbound API request. More specifically, the electronic device (100) can display the debugging icon of the corresponding outbound API request on the list page (600) so that only the first outbound API request (611) among multiple outbound API requests can be curled and tested.

7) Information about the transmission time of the outbound API request (637) may include information about the time the outbound API request was transmitted. For example, it can be confirmed that the first outbound API request was transmitted at 9:05:59 on 2022.05.13.

As described above, in response to an input via an icon corresponding to the second list of the list page (600), the electronic device (100) can provide a second page including an outbound API request and an API response. The second page displaying the first outbound API request (611) and the corresponding API response of the list page (600) will be described in FIGS. 7A and 7B.

Figure 7a shows a screen for the source code of the request header of the first outbound API request (611).

According to one embodiment, the electronic device (100) may provide a second list including a first outbound API request (611), a request header of the first outbound API request (611), and source code for an API response corresponding to the first outbound API request (611), in response to inputs via an icon for a request (710), an icon for a request header (720), and an icon for a response (730).

Referring to FIG. 7a, the first screen (700) may be a screen for the source code of the request header of the first outbound API request (611). The first outbound API request (611) may be a request for a “hotkeyword”.

In the present invention, an outbound API request may be a request according to the HTTP protocol, and may include a line (721) for "HOST" related to a service server host name and port number, a line (722) for "REFERER" related to URL address information of a recently accessed web page, a line (723) for "ACCEPT-LANGUAGE" related to a language that the server can support, a line (724) for "ACCEPT" related to a media type type that the server can process, and a line (725) for "ACCEPT ENCODING" related to a compression method supported by the server.

Figure 7b shows a screen for the source code of an API response corresponding to the first outbound API request (611).

Referring to FIG. 7b, the second screen (750) may be a screen for an API request corresponding to the first outbound API request (611). The electronic device (100) may, in response to an input through an icon (730) for a response, provide a second list including a source code for the API response. The second screen (750) may include “200”, which is Status information (731) corresponding to the first outbound API request (611). Accordingly, it may be known that the service server (120) has normally processed the first outbound API request (611).

The API response is an API response corresponding to the first outbound API request (611) for the "hotkeyword" and may include information about the keyword and the level of the keyword. For example, the API response may include a list of keywords including "cooking oil", "love test", "chiffon pink", "number 1", and "canola oil", and corresponding levels including "0", "10", "10", "10", and "10".

FIG. 8 is a diagram illustrating an example of modifying an API request or API response when an error occurs through a first terminal and a second terminal according to an embodiment of the present invention.

Through the list page provided by the electronic device (100), an API request corresponding to the performance of a function of the first terminal (110) (here, the API request may include an inbound API request and an outbound API request) and an API request or API response that is determined to have an error among the API responses can be checked. Accordingly, a specific embodiment of correcting an API request or API response that is determined to have an error will be examined below.

According to one embodiment, the electronic device (100) can check information about a target inbound API request (810) that is determined to have an error from the first terminal (110). If an outbound API request or API response is determined to have an error, the electronic device (100) can receive information about a target inbound API request (810) that corresponds to the outbound API request or API response that is determined to have an error.

Accordingly, the electronic device (100) can check the second identification information, URL information corresponding to the target inbound API request, and time information corresponding to the target inbound API request based on the information about the target inbound API request (810). Accordingly, the electronic device (100) can transmit information (820) including the first identification information, the second identification information, URL information corresponding to the target inbound API request (810), and time information corresponding to the target inbound API request to the second terminal (800).

However, the second terminal (800) may also receive the same information (830) as the information (820) according to another embodiment as follows. For example, by searching for the first identification information corresponding to the first terminal (110) in the list page, a user using another terminal can also check the list page displaying the API request and API response matching the function execution of the first terminal (110). Accordingly, the user of the first terminal (110) can share the list page displaying the API request and API response with the user of the second terminal (800). Accordingly, multiple users using different terminals can test and correct an erroneous part among the API request and API response together through the list page. A user of the first terminal (110) can check an inbound API request with an error through a list page, and then transmit information (830) including first identification information, second identification information, URL information corresponding to the target inbound API request (810), and time information corresponding to the target inbound API request to the second terminal (800).

A user of a second terminal (800) who has obtained first identification information, second identification information, URL information corresponding to a target inbound API request (810), and time information corresponding to the target inbound API request can identify a target inbound API request (810) that has been identified as having an error in the first terminal (110) by searching for the first identification information on a list page. Accordingly, the user of the second terminal (800) can check an API request or API response that has an error among the target inbound API request (810), an outbound API request corresponding to the target inbound API request (810), and an API response.

According to one embodiment, the electronic device (100) may receive, from the second terminal (110), modified data (840) that modifies at least one of an inbound API request, an outbound API request corresponding to the inbound API request, and an API response. For example, the modified data (840) of FIG. 8 may be data that modifies an element having an error in the API response. More specifically, the electronic device (100) may modify at least one of the inbound API request, the corresponding outbound API request, and the API response based on the modified data (840). For example, the API response before modification may include a response such as "fresh": 15000, "global": 29800 (851) in relation to a threshold price of free shipping. In addition, the electronic device (100) can modify "fresh": 15000, "global": 29800 (851) to "fresh": 29800, "global": 15000 (852) based on the modification data (840). Accordingly, the electronic device (100) can perform the first terminal (110) by improving the function of the first terminal (110) according to the modified API response (860) based on the modification data (840).

FIG. 9 is a diagram for explaining an embodiment of modifying a set of outbound API requests corresponding to inbound API requests.

FIG. 9 illustrates a first list page (900), a second list page (930), and a third list page (960) according to the number of outbound API requests included in a set of multiple outbound API requests corresponding to an inbound API request for “category-layer” having an index number of 12.

1) According to one embodiment, the electronic device (100) may verify a set of outbound API requests corresponding to an inbound API request from a data storage based on second identification information, verify a first outbound API request that is a duplicate outbound API among the outbound API requests included in the set, verify a modified set by deleting the first outbound API request from the set, and re-verify the inbound API request, and transmit an outbound API request of the modified set including second identification information based on the modified set.

For example, a set of outbound API requests corresponding to an inbound API request for "category-layer" with an Index number of 12 displayed on the second list page (930) may include four outbound API requests. However, the first outbound API request (931) and the second outbound API request (932) may be duplicated. If the first outbound API request (931) and the second outbound API request (932) are duplicated, there is a problem that more resources are allocated in the API request and API response process even if the same function is performed in the first terminal (110). Accordingly, the electronic device (100) may check a modified set of outbound API requests by deleting one of the first outbound API request (931) and the second outbound API request (932). For example, a modified set, such as in the first list page (900), may consist of three non-duplicate outbound API requests.

2) According to one embodiment, the electronic device (100) may identify a set of outbound API requests corresponding to an inbound API request from a data storage based on second identification information, identify a first outbound API request not included in the set based on specification information about the API, identify a modified set by adding the first outbound API request to the set, and re-verify the inbound API request, and transmit an outbound API request of the modified set including the second identification information based on the modified set.

For example, a set of outbound API requests corresponding to an inbound API request for "category-layer" with an Index number of 12 displayed on a second list page (930) may include two outbound API requests. The electronic device (100) may identify a third outbound API request (903) that is not included in the set of outbound API requests, based on specification information for an API corresponding to the inbound API request. Here, the specification information for the API corresponding to the inbound API request may typically be information on a set of a plurality of outbound API requests corresponding to the inbound API request. For example, the specification information for an API corresponding to an inbound API request for "category-layer" having an index number of 12 may include information on a first set including a first outbound API request (901), a second outbound API request (902), and a third outbound API request (903). Accordingly, the electronic device (100) can compare the set of outbound API requests and the first set to identify the third outbound API request (903) that is not included in the set of API requests. Accordingly, the electronic device (100) can identify a modified set of outbound API requests by adding the third outbound API request (903) to the set of outbound API requests. For example, the modified set may be composed of three outbound API requests, such as in the first list page (900).

According to one embodiment, as seen in the information (634) on whether mock data is used for an outbound API request through the list page provided by the electronic device (100), API requests and API responses can be modified with mock data. This will be examined in detail below.

FIGS. 10a, 10b and 10c are diagrams illustrating an example embodiment of simulating an API request and an API response.

Referring to FIG. 10A, a list page (1000) provided by an electronic device (100) is illustrated. A user can check a target API request or target API response that requires mocking among API requests and API responses. For example, a user can select a first outbound API request (1011) and a second outbound API request (1012) that require mocking on the list page and click "Save as mock data" (1020). In addition, a user can select the first outbound API request (1011) even when mocking is required for an API response corresponding to the first outbound API request (1011).

Referring to FIG. 10b, in response to clicking “Save as mock data” (1020), the electronic device (100) may display a page (1030) for entering information about the mock data. For example, the user may enter “Test Project” (1031) as the project, “A” (1032) as the scenario, and “test for A” (1033) as the group name through the page (1030), and click “Save” (1034) to save the information about the mock data.

Referring to FIG. 10c, the electronic device (100) may provide a page (1040) for editing a target API request or a target API response for which mocking is required. For example, a user may input “Test Project” (1041) as a project name and “A” (1042) as a scenario through the page (1040), thereby checking a list of mock data saved under the name “A” in the “Test Project” project. Based on the information about the URL and Create Time displayed on the page (1040), the user may check the target API request or the target API response for which mocking is required in the list of mock data. Accordingly, in response to an input through the Edit icon (1043) of the page (1040), the electronic device (100) may provide an interface for editing the target API request or the target API response for which an input has been received.

FIG. 11 is a block diagram schematically illustrating an electronic device for providing information according to one embodiment.

The electronic device (1100) of Fig. 11 may correspond to the electronic device (100) of the present specification.

The electronic device (1100) of the present disclosure may include, according to an embodiment, a transceiver (1110), a processor (1120), and storage (1130). The components illustrated in FIG. 11 are not essential for implementing the electronic device, and thus, it will be understood by those skilled in the art related to the present embodiment that the electronic device (1100) described in the present specification may have more or fewer components than the components listed above. Meanwhile, in the embodiment, the processor (1120) may include at least one processor. In addition, the electronic device (1100) may also operate as a server or a proxy server.

The transceiver (1110) can communicate with an external device using wired or wireless communication technology and can include the transceiver (1110). The external device can be a terminal or a server including a terminal of a developer or a quality assurance team. In addition, the communication technology used by the transceiver (1110) can include, but is not limited to, GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), LTE (Long Term Evolution), 5G, WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), Bluetooth, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), ZigBee, NFC (Near Field Communication), etc.

According to one embodiment, the transceiver (1110) may communicate with the first terminal (110) and the service server (120) to exchange information. More specifically, the transceiver (1100) may transmit and receive API requests and API responses with the service server (120). For example, the transceiver (1100) may obtain information such as a universal unique identifier from the first terminal (110). The transceiver (1100) may transmit an outbound API request including second identification information to the service server (120), and receive an API response corresponding to the outbound API request from the service server.

The processor (1120) can control the overall operation of the electronic device (1100) and process data and signals. The processor (1120) can perform one of the methods described above through FIGS. 1 to 11. The processor (1120) can control embodiments performed by the electronic device (1100) through interaction with the transceiver (1110) and the storage (1130), and further components that the electronic device (1100) can include. According to one embodiment, the processor (1120) may verify an inbound API request including first identification information about a requester and request information about an API based on information acquired from a first terminal, assign second identification information to the inbound API request, verify a service server corresponding to the inbound API request, transmit an outbound API request including the second identification information to the service server (120) based on the inbound API request, receive an API response corresponding to the outbound API request from the service server (120), and provide a list page for the inbound API request, the outbound API request, and the API response.

Storage (1130) can store information for performing at least one of the methods described above through FIGS. 1 to 11. Storage (1130) can be referred to as memory and can be volatile memory or nonvolatile memory. For example, storage (1130) can include data storage of FIG. 3.

Meanwhile, the present specification and drawings have disclosed preferred embodiments of the present invention, and although specific terms have been used, they have been used only in a general sense to easily explain the technical contents of the present invention and to help understand the invention, and are not intended to limit the scope of the present invention. It will be apparent to those skilled in the art that other modified examples based on the technical idea of the present invention can be implemented in addition to the embodiments disclosed herein.

The electronic device or terminal according to the above-described embodiments may include a processor, a memory for storing and executing program data, a permanent storage such as a disk drive, a communication port for communicating with an external device, a user interface device such as a touch panel, a key, an icon, etc. The methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program commands executable on the processor. Here, the computer-readable recording medium includes a magnetic storage medium (e.g., a read-only memory (ROM), a random-access memory (RAM), a floppy disk, a hard disk, etc.) and an optical reading medium (e.g., a CD-ROM, a Digital Versatile Disc (DVD)). The computer-readable recording medium may be distributed to computer systems connected to a network, so that the computer-readable code may be stored and executed in a distributed manner. The medium may be readable by a computer, stored in a memory, and executed by a processor.

The present embodiment may be represented by functional block configurations and various processing steps. These functional blocks may be implemented by various numbers of hardware and/or software configurations that perform specific functions. For example, the embodiment may employ direct circuit configurations such as memory, processing, logic, look-up tables, etc., which may perform various functions under the control of one or more microprocessors or other control devices. Similarly to the fact that the components may be implemented as software programs or software elements, the present embodiment may be implemented in a programming or scripting language such as C, C++, Java, assembler, Python, etc., including various algorithms implemented as a combination of data structures, processes, routines, or other programming configurations. The functional aspects may be implemented as algorithms that are executed on one or more processors. In addition, the present embodiment may employ conventional techniques for electronic environment setting, signal processing, and/or data processing. Terms such as “mechanism,” “element,” “means,” and “configuration” may be used broadly and are not limited to mechanical and physical configurations. The terms may also include the meaning of a series of software processes (routines) in connection with a processor, etc.

The above-described embodiments are only examples, and other embodiments may be implemented within the scope of the claims set forth herein.

Claims (14)

In a method of providing information on an electronic device,
A step of verifying an inbound API request including first identification information about a requester and request information for an API (Application Programming Interface) based on information acquired from a first terminal;
A step of assigning second identification information to the above inbound API request;
A step for checking a service server responding to the above inbound API request;
A step of transmitting an outbound API request including the second identification information to the service server based on the inbound API request;
A step of receiving an API response corresponding to the outbound API request from the service server; and
Comprising a step of providing a list page for the inbound API request, the outbound API request and the API response,
The above information provision method is:
A step of verifying the inbound API request corresponding to the first terminal based on the first identification information;
A step of verifying the outbound API request and the API response corresponding to the inbound API request based on the second identification information; and
Further comprising a step of matching the first identification information, the second identification information, the inbound API request, the outbound API request and the API response based on the first identification information and the second identification information and storing them in data storage,
The steps for providing the above list page are:
A step of confirming an inbound API request corresponding to the first terminal among a plurality of inbound API requests stored in the data storage using the first identification information;
A step of using the second identification information to identify a set of outbound API requests and a set of API responses corresponding to the inbound API request among a plurality of outbound API requests and a plurality of API responses stored in the data storage;
Providing a list page including a first list of a set of outbound API requests matching the inbound API request and a second list of API responses corresponding to the outbound API request,
How to provide information.
delete delete In the first paragraph,
An information providing method characterized in that the second list is provided in response to the reception of an input corresponding to the outbound API request on the list page obtained from the first terminal.
In the first paragraph,
The steps to check the above service server are:
A step of verifying the outbound API request having the second identification information identical to the inbound API request; and
An information providing method comprising a step of verifying the service server corresponding to the above outbound API request.
In the first paragraph,
The steps for providing the above list page are:
An information providing method comprising the step of providing the list page by displaying the inbound API request at a first level and displaying the outbound API request at a second level lower than the first level.
In the first paragraph,
The steps for providing the above list page are:
An information providing method comprising the step of providing the list page by displaying at least one of information about the file size of the outbound API request, method information corresponding to the outbound API request, status information corresponding to the outbound API request, information about whether mock data is used for the outbound API request, information about the transmission time of the outbound API request, information about an icon corresponding to the second list, and information about a debugging icon of the outbound API request.
In the first paragraph,
The step of receiving the above API response is:
A step of waiting for a response to the transmission of the outbound API request including the second identification information; and
An information providing method comprising a step of receiving an API response, which is a response to the outbound API request, from the service server.
In the first paragraph,
A step of identifying a set of outbound API requests corresponding to the inbound API request from the data storage based on the second identification information;
A step of checking a first outbound API request, which is a duplicate outbound API request among the outbound API requests included in the above set;
A step of verifying a modified set by deleting the first outbound API request from the set; and
An information providing method further comprising the step of re-verifying said inbound API request, wherein the step comprises transmitting an outbound API request of said modified set including said second identification information based on said modified set.
In the first paragraph,
A step of identifying a set of outbound API requests corresponding to the inbound API request from the data storage based on the second identification information;
A step of identifying a first outbound API request not included in the set based on the specification information for the above API;
A step of adding the first outbound API request to the above set to verify the modified set; and
An information providing method further comprising the step of re-verifying said inbound API request, wherein the step comprises transmitting an outbound API request of said modified set including said second identification information based on said modified set.
In the first paragraph,
A step of receiving information about the inbound API request that is confirmed to have an error from the first terminal;
A step of verifying the second identification information, URL information corresponding to the inbound API request, and time information corresponding to the inbound API request based on information about the inbound API request; and
An information providing method further comprising the step of transmitting the first identification information, the second identification information, the URL information, and the time information to a second terminal.
In Article 11,
A step of receiving modified data that modifies at least one of the inbound API request, the outbound API request and the API response from the second terminal; and
An information providing method further comprising a step of modifying at least one of the inbound API request, the outbound API request and the API response based on the modified data.
In an electronic device for providing information,
transceiver;
Storage for storing one or more instructions; and
Verify an inbound API request including first identification information about the requester and request information for the API based on information obtained from the first terminal,
Assign second identification information to the above inbound API request,
Check the service server that responds to the above inbound API request,
Transmitting an outbound API request including the second identification information to the service server based on the inbound API request;
Receive an API response corresponding to the outbound API request from the service server, and
A processor comprising a processor that provides a list page for the inbound API request, the outbound API request, and the API response,
The above processor,
Based on the first identification information, the inbound API request corresponding to the first terminal is verified,
Verify the outbound API request and the API response corresponding to the inbound API request based on the second identification information, and
Based on the first identification information and the second identification information, the first identification information, the second identification information, the inbound API request, the outbound API request and the API response are matched and stored in data storage,
The above processor,
Using the first identification information, the inbound API request corresponding to the first terminal is identified among the plurality of inbound API requests stored in the data storage,
Using the second identification information, a set of outbound API requests and a set of API responses corresponding to the inbound API request are identified among a plurality of outbound API requests and a plurality of API responses stored in the data storage, and
Providing a list page including a first list of a set of outbound API requests matching the inbound API request and a second list of API responses corresponding to the outbound API request.
Electronic devices.
A non-transitory computer-readable storage medium having recorded thereon a program for executing the method of claim 1 on a computer.

Images