Saas connection system for implementing connection between saas applications using API specification including bm

Abstract

The present invention relates to a SaaS connection system enabling a connection between SaaS applications to be easily implemented by converting APIs provided by various SaaS applications into API specifications and providing input / output variables and a call program for all available APIs to a user on the basis of the API specifications, and information such as a cost for calling the APIs or the like to be provided to the user by including a BM for adding call information to the API specifications. The SaaS connection system may comprise: an API conversion unit that converts APIs provided by one or more SaaS applications into API specifications; a call information generation unit that adds, to the API specifications, call information for calling the APIs; and a programming unit that generates call programs for calling the APIs on the basis of the API specifications, wherein the call information may include information for selecting a call program and calculating a driving cost.

Description

A SaaS integration system that implements integration between SaaS applications using API specifications that include BM.

[0001] The present invention relates to a SaaS linkage system that implements linkage between SaaS applications using an API specification including a BM, and more specifically, to a SaaS linkage system that converts APIs provided by various SaaS applications into API specifications and provides input / output variables and call programs for all available APIs to a user based on the API specifications, thereby enabling easy implementation of linkage between SaaS applications, and that includes a BM that adds call information to the API specifications, thereby enabling information such as costs for API calls to be provided to the user.

[0002] SaaS (Software as a Service) is a software model that allows users to access only the services they need among its various functions. SaaS represents a fundamental shift in software distribution, whereby vendors use a single platform to provide software services to multiple customers, and users pay only for the services they use.

[0003] The most significant difference between SaaS and traditional software business models is the ownership of the product. While traditional enterprise software is stored and used on internal servers and other equipment, customers retain ownership, SaaS distinguishes itself from traditional licensing models by presenting software as a service, not a product.

[0004] SaaS significantly reduces the cost of purchasing new software features and allows businesses to avoid infrastructure investment and management burdens by paying based on usage over a set period of time.

[0005] Companies utilize SaaS applications with these advantages from various companies, depending on their specific needs. However, sharing, converting, and editing data between SaaS applications is challenging. To achieve this, companies must create programs that call the APIs provided by each SaaS application to retrieve and edit the desired data. As the number of SaaS applications a company utilizes grows, this task can become a significant burden, requiring significant time and manpower.

[0006] To alleviate this inconvenience, many inventors have been researching ways to easily retrieve and edit desired data by linking SaaS applications, but have not yet achieved satisfactory results.

[0007] The technical problem to be achieved by the SaaS linkage system that implements linkage between SaaS applications using an API specification including a BM (Business Model) according to the technical idea of ​​the present invention is to provide a SaaS linkage system that converts APIs provided by various SaaS applications into specifications and provides input / output variables and call programs for all available APIs to the user based on the specifications, thereby enabling easy implementation of linkage between SaaS applications.

[0008] Another technical task to be achieved by a SaaS linkage system that implements linkage between SaaS applications using an API specification including a BM according to the technical idea of ​​the present invention is to provide a SaaS linkage system that can provide users with information such as costs for API calls by including a BM that adds call information to the API specification, and can actively increase the provision of APIs by SaaS application providers.

[0009] The technical task to be achieved by the SaaS linkage system that implements linkage between SaaS applications using an API specification including BM according to the technical idea of ​​the present invention is not limited to the tasks mentioned above, and other tasks not mentioned will be clearly understood by those skilled in the art from the description below.

[0010] According to one embodiment of the technical idea of ​​the present invention, a SaaS linkage system for linking SaaS applications includes an API conversion unit that converts an API provided by one or more SaaS applications into an API specification; a call information generation unit that adds call information for calling the API to the API specification; and a programming unit that generates a call program that calls the API based on the API specification, wherein the call information may include information for selecting the call program and calculating the running cost.

[0011] The API specification converted by the API conversion unit may include information about call parameters and response parameters.

[0012] The call information may include at least one of an API call price, a limit on the number of API calls, an API call time, a response parameter price, and an API response time.

[0013] The SaaS linkage system may further include a form generation unit that inputs call parameters into a call program generated by the programming unit to call an API and checks whether expected response parameters corresponding to the input call parameters are normally output.

[0014] The form generator obtains call parameters and response parameters from the API specification, inputs the call parameters to run the calling program, and checks whether the expected response parameters that the calling program is expected to return are returned.

[0015] The form generation unit performs a verification process to check whether the returned response parameters are identical to the expected response parameters, and if the returned response parameters are not identical to the expected response parameters, the API conversion unit reconverts the API into a text-based API specification, and the programming unit can regenerate a calling program that calls the API based on the reconverted API specification.

[0016] The form generator can provide a table displaying call parameters, response parameters, and call information for each API.

[0017] The SaaS integration system may further include a user authentication unit that performs user authentication when a calling program is run and accesses a SaaS application via an API.

[0018] The programming department can create a calling program that returns response parameters when calling an API using call parameters based on the API specification, and can create a calling program that outputs processed output values ​​using the response parameters returned for each of multiple APIs.

[0019] The programming department can create a calling program that returns response parameters when calling an API with calling parameters based on the API specification, but can create a calling program that displays calling information and executes a step of obtaining user consent for the calling information before the calling program calls the API.

[0020] According to an embodiment of the technical idea of ​​the present invention, a SaaS linkage system that implements linkage between SaaS applications using an API specification including a BM converts APIs provided by various SaaS applications into specifications and provides input / output variables and call programs for all available APIs to the user based on the specifications, thereby enabling easy implementation of linkage between SaaS applications.

[0021] According to an embodiment of the technical idea of ​​the present invention, a SaaS linkage system that implements linkage between SaaS applications using an API specification including a BM can provide information such as costs for API calls to users by including a BM that adds call information to the API specification, and can actively increase the provision of APIs by SaaS application providers.

[0022] However, the effects that can be achieved by the SaaS linkage system that implements linkage between SaaS applications using an API specification including BM according to one embodiment of the present invention are not limited to those mentioned above, and other effects that are not mentioned will be clearly understood by those skilled in the art from the description below.

[0023] To facilitate a more thorough understanding of the drawings cited herein, a brief description of each drawing is provided.

[0024] FIG. 1 is a schematic diagram of a SaaS linkage system that implements linkage between SaaS applications using API specifications according to one embodiment of the present invention.

[0025] FIG. 2 schematically illustrates a table displaying call parameters, response parameters, and call information for each API provided by a form generation unit of a SaaS linkage system according to one embodiment of the present invention.

[0026] The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, and it should be understood that the present invention encompasses all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention.

[0027] In describing the present invention, detailed descriptions of related known technologies will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Furthermore, numbers (e.g., "first," "second," etc.) used throughout the description of this specification are merely identifiers used to distinguish one component from another.

[0028] Additionally, in this specification, when a component is referred to as being “connected” or “connected” to another component, it should be understood that the component may be directly connected or connected to the other component, but may also be connected or connected via another component in between, unless there is a specific description to the contrary.

[0029] In addition, the components expressed as "~part" in this specification may be two or more components combined into one component, or one component may be divided into two or more components with more detailed functions. In addition, each component described below may additionally perform some or all of the functions performed by other components in addition to its own main function, and of course, some of the main functions performed by each component may be exclusively performed by other components.

[0030] Hereinafter, embodiments according to the technical idea of ​​the present invention will be described in detail one by one.

[0031] FIG. 1 is a schematic diagram of a SaaS linkage system that implements linkage between SaaS applications using API specifications according to one embodiment of the present invention. FIG. 2 schematically illustrates a table displaying call parameters, response parameters, and call information for each API, provided by the form generation unit of the SaaS linkage system according to one embodiment of the present invention.

[0032] A SaaS linkage system (100) according to one embodiment of the present invention is connected to a user terminal (10) and a SaaS application (20) through a network (50), and may include an API conversion unit (110), a call information generation unit (120), a programming unit (130), a form generation unit (140), and a user authentication unit (150).

[0033] The user terminal (10) may be implemented as a computer capable of connecting to a remote server or terminal via a network (50). Here, the computer may include, for example, a notebook, desktop, or laptop equipped with a web browser. In addition, the user terminal (10) may be implemented as a terminal device capable of connecting to a remote server or terminal via a network (50). The terminal device may include all types of handheld-based wireless communication devices such as, for example, a wireless communication device that guarantees portability and mobility, such as a PCS (Personal Communication System), GSM (Global System for Mobile communications), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), PDA (Personal Digital Assistant), IMT (International Mobile Telecommunication)-2000, CDMA (Code Division Multiple Access)-2000, W-CDMA (W-Code Division Multiple Access), Wibro (Wireless Broadband Internet), LTE (Long Term Evolution), NR (New Radio), 5G terminal, smartphone, smartpad, tablet PC, etc.

[0034] SaaS (Software as a Service) refers to a business model that provides software in the form of a service, and SaaS applications (20) are provided as services that users can access through a web browser without purchasing or installing software. SaaS applications (20) are applications that are connected to a SaaS server and may be HR applications, accounting applications, marketing applications, etc., and may be various applications used for the work of users (companies). SaaS applications (20) may be multiple applications created by a single service provider or multiple applications provided by separate service providers.

[0035] A network (50) refers to a connection structure that enables information exchange between each node, such as a plurality of terminals and servers, and examples of such a network include, but are not limited to, a 3GPP (3rd Generation Partnership Project) network, an LTE (Long Term Evolution) network, a 5G network, a WIMAX (World Interoperability for Microwave Access) network, the Internet, a LAN (Local Area Network), a Wireless LAN (Wireless Local Area Network), a WAN (Wide Area Network), a PAN (Personal Area Network), a Bluetooth network, a satellite broadcasting network, an analog broadcasting network, and a DMB (Digital Multimedia Broadcasting) network.

[0036] The API conversion unit (110) can convert an API (Application Programming Interface) provided by one or more SaaS applications (20) into a text API specification.

[0037] Each SaaS application (20) may provide users with one or more APIs that perform specific functions. An API is a tool or standard that provides an interface for software applications to interact with each other. It helps multiple applications communicate and exchange data, and facilitates interaction between different software components. Typically, APIs are provided through functions, protocols, tools, classes, etc., which allow developers to utilize the functions of other applications or access services. For example, in web development, a web browser may use an API to communicate with a web server, and a mobile app may use an API to retrieve data from a server or interact with another device.

[0038] An API specification (or API documentation) is a document that details the functions, usage, endpoints, parameters, etc. of an API provided by a specific application or service. It can help developers and users correctly understand and use the API. The programming unit (130), described below, automatically generates a program that calls the API using the information contained in the API specification to obtain the desired result.

[0039] An API specification may include the following: API function description (a description of the main functions provided by the API and the purpose of the functions), endpoint information (information about the URL or URI for accessing specific functions in the API), parameter / request format (a description of the parameters required when calling the API and their types, formats, restrictions, etc., and information about how to send the API request), response format (a description of the format of the response returned by the API and the structure of the data included in the response), authentication / authorization (information about what authentication method is required to access the API and what permissions are required), error handling (information about error codes that may occur in the API and how to handle errors), examples and usage (a guide and code examples on how to use the API through actual usage examples), version / update information (version information and update history of the API).

[0040] The API conversion unit (110) may use various known methods to convert the API provided by the SaaS application (20) into an API specification, and a method of conversion using a known conversion tool such as Swagger may also be used.

[0041] The API specification converted by the API conversion unit (110) may include information on call parameters (input values), response parameters (output values), and API functions.

[0042] The call information generation unit (120) can add a BM to the API specification. That is, the call information generation unit (120) can add call information for calling the API. The call information can include API call prices, API call count limits, API call availability time, response parameter prices, API response times, etc.

[0043] API call price refers to the cost incurred when calling the API once from the server of the SaaS application, API call count limit refers to the number of times the API can be called from the server of the SaaS application on a daily, weekly, or monthly basis, API call available time refers to the time during which calls can be made from the server of the SaaS application, response parameter price refers to the data price assigned according to the type of data output, and API response time refers to the time it takes for the server of the SaaS application to respond when calling the API.

[0044] By adding call information to API specifications, SaaS application providers will be more proactive in providing APIs, as the benefits of API calls will increase based on call information. Furthermore, operators of SaaS-integrated systems will be able to provide a more objective cost structure to users of their SaaS-integrated systems, resulting in an increase in users satisfied with the reasonable cost structure and increased usage fees.

[0045] The programming unit (130) can automatically generate a calling program that calls the API using the information included in the API specification. The programming unit (130) can receive the API specification as input and automatically generate client or server code for the corresponding API.

[0046] The programming unit (130) can automatically generate a calling program that can call an API and return a response parameter when a user inputs a calling parameter, and obtains information necessary for such automatic programming from information in the API specification in text format.

[0047] The programming unit (130) can create a program that provides an output value obtained by calling one API of one SaaS application (20) as a result value, a program that processes output values ​​obtained by calling multiple APIs of one SaaS application (20) for a desired purpose and provides them as result values, a program that processes output values ​​obtained by calling one or more APIs of multiple SaaS applications (20) for a desired purpose and provides them as result values, etc., and whether or not to provide a result value in such a program can be decided by a developer or a user, and the programming unit (130) performs programming based on this decision.

[0048] The form generation unit (140) can input call parameters into the call program generated by the programming unit (130) to call the API and check whether the response parameters are output normally.

[0049] The form generation unit (140) obtains call parameters and response parameters from the API specification, inputs the call parameters to run the calling program, and can perform a verification procedure to check whether the expected response parameters expected to be returned by the calling program are returned.

[0050] For example, if the API performs a function that returns the employee's annual salary as a response parameter by using the employee's name as a call parameter, the form generation unit (140) checks whether the correct annual salary is returned as a response parameter when the calling program is driven to call the API by entering the name of an employee whose annual salary is already known as a call parameter.

[0051] This verification procedure is to confirm in advance whether the automatic programming of the programming unit (130) has been performed accurately.

[0052] In addition, this verification procedure is to check in advance for malfunctions that may occur when a calling program programmed based on an old version of the API specification calls a new version of the API, as there may be differences in functionality between the old version of the API specification and the updated new version of the API when the API is updated after the API has been converted to an API specification.

[0053] If the returned response parameters are not the same as the expected response parameters, the API conversion unit (110) reconverts the API into a text-based API specification, and the programming unit (130) can regenerate a calling program that calls the API based on the reconverted API specification.

[0054] The form generation unit (140) may periodically perform a verification process to check for errors in such calling programs. In order to compare the returned response parameters and the expected response parameters through the verification process, the form generation unit (140) may provide the developer or the user with a table displaying call parameters, response parameters, and call information for each API, as shown in FIG. 2. In addition, the form generation unit (140) may prepare verification call parameters and verification response parameters whose values ​​are already known for the verification process and provide them to the developer or the user.

[0055] The programming unit (130) can create a calling program that calls multiple APIs based on multiple API specifications as call parameters and outputs processed output values ​​using the returned response parameters. For example, in FIG. 2, the employee name "Kim Cheol-su" is used as a call parameter to call SaaS01_API01, which is an API provided by Company A's HR SaaS application, and SaaS02_API01, which is an API provided by Company B's accounting SaaS application, so that this year's salary details are returned from SaaS01_API01 and this year's corporate card usage details are returned from SaaS02_API01, so that the salary and corporate card usage details received by an employee named Kim Cheol-su this year can be edited and output so that they can be viewed at once.

[0056] Additionally, the programming unit (130) may be programmed to generate a calling program based on an API specification containing call information, such that the calling program displays the call information and obtains the user's consent before calling the API. This display of call information and consent process allows the user to confirm the cost, thereby preventing future disputes related to costs.

[0057] The user authentication unit (150) can perform user authentication for the SaaS application (20) when a calling program is run and accesses the SaaS application (20) through an API.

[0058] The user authentication unit (150) can perform access authentication of the calling program for all SaaS applications (20) in advance, and thus, if the user performs access authentication for the SaaS linked system (100) once through the user authentication unit (150), there is no need to perform access authentication again for all SaaS applications (20). Accordingly, the user can eliminate the inconvenience of having to authenticate each time he or she accesses each SaaS application (20).

[0059] The user authentication unit (150) can also perform other types of authentication.

[0060] The user authentication unit (150) can receive authentication unique numbers consisting of n natural numbers transmitted from the SaaS application (20) to the user terminal (10) when the user logs in to each of the SaaS applications (20) in the following manner (where n is a natural number). Here, the authentication unique number is a number that must be entered in addition to the user ID and password when logging in to the corresponding SaaS application (20).

[0061] The user authentication unit (150) is randomly arranged with n natural numbers (M) having values ​​from 1 to n, M1 to M n It is written as [M1M2M3...M n ] is transmitted to the user terminal (10) (wherein, M1 is the natural number of the first digit of the input proposal number, M2 is the natural number of the second digit of the input proposal number, M3 is the natural number of the third digit of the input proposal number, and M n (is a natural number of the nth digit of the input proposal number), the user sequentially inputs the M1 digits of each authentication unique number into the user authentication unit (150) through the user terminal (10), then sequentially inputs the M2 digits of each authentication unique number, and repeats the same method to finally input the M of each authentication unique number. nYou can complete the submission number by entering the numbers in order.

[0062] The user authentication unit (150) groups the entered submission number into n groups G1 to G having the same number of numbers. n (G1, G2... G n ) and, in case of user authentication for a specific SaaS application, G1 to G n Extract the first numbers from each group of G1, so that the first number of G1 is located at the M1th, the first number of G2 is located at the M2nd, and so on, repeating the same way to finally obtain G n The first number of M n After generating an authentication input number, which is a combination of numbers located at the second position, enter it into the above-mentioned SaaS application, and until the authentication input number and authentication unique number match and authentication is completed, it is G1 to G n In each group, the next digits of the first digits, i.e. the second digits, can be extracted and the same process repeated to complete the authentication.

[0063] Through this authentication process, the user does not need to remember the authentication unique number for each SaaS application, but only configures the initial submission number and enters it into the user authentication section (150), and the input suggestion number [M1M2M3...M] is input as pre-information. n ], the user authentication unit (150) automatically reconstructs each authentication input number based on the entered submission number and repeatedly inputs it until authentication is completed. The user authentication unit (150) also no longer needs to store authentication unique numbers for each SaaS application. In addition, even if the submission number is leaked during transmission due to hacking, the damage from the leakage of authentication unique numbers can be reduced because the numbers are mixed according to a predetermined rule called the input suggestion number.

[0064] For example, the user authentication unit (150) receives a 6-digit first authentication unique number "438782" received from the first SaaS application, a 6-digit second authentication unique number "129283" received from the second SaaS application, and a 6-digit third authentication unique number "241298" received from the third SaaS application when the user logs in to each of the SaaS applications (20).

[0065] The user authentication unit (150) transmits the input proposal number "563421" to the user terminal (10), and the user inputs "889", which is the 5th digit of each authentication unique number, into the user authentication unit (150) through the user terminal (10), then inputs "238", which is the 6th digit of each authentication unique number, then inputs "891", which is the 3rd digit of each authentication unique number, then inputs "722", which is the 4th digit of each authentication unique number, then inputs "324", which is the 2nd digit of each authentication unique number, and then inputs "412", which is the 1st digit of each authentication unique number, to complete and input the submission number "889238891722324412".

[0066] Afterwards, the user authentication unit (150) separates the input submission number into 6 groups so that the G1 group is "889", the G2 group is "238", the G3 group is "891", the G4 group is "722", the G5 group is "324", and the G6 group is "412", and the first number "8" of the G1 group is positioned at the 5th position as "_ _ _ _ 8 _", the first number "2" of the G2 group is positioned at the 6th position as "_ _ _ _ 8 2", the first number "8" of the G3 group is positioned at the 3rd position as "_ _ 8 _ 8 2", the first number "7" of the G4 group is positioned at the 4th position as "_ _ 8 7 8 2", and the first number "3" of the G5 group is positioned at the 3rd position as "_ 3 8 7 8 2". The first number "4" of the G6 group is positioned at the second position, and the first authentication input number "438782" is completed as "4 3 8 7 8 2". The user authentication unit (150) completes the second authentication input number "129283" and the third authentication input number "241298" in the same manner.

[0067] The user authentication unit (150) can complete authentication for each SaaS application by sequentially entering the first authentication input number to the third authentication input number for each SaaS application and repeating the process until an authentication input number that matches the authentication unique number is output.

[0068] The functional operations described in this specification and the embodiments of the present subject matter can be implemented in digital electronic circuits, computer software, firmware, or hardware, or in a combination of one or more of these, including the structures disclosed herein and their structural equivalents.

[0069] Embodiments of the subject matter described herein may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible program medium for execution by or controlling the operation of a data processing device. The tangible program medium may be a radio signal or a computer-readable medium. A radio signal is an artificially generated signal, such as a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to a suitable receiver device for execution by a computer. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a combination of materials that affect a machine-readable radio signal, or a combination of one or more of these.

[0070] A computer program (also known as a program, software, software application, script or code) may be written in any programming language, including compiled or interpreted languages, a priori or procedural languages, and may be deployed in any form, including as a standalone program, a module, a component, a subroutine or other unit suitable for use in a computing environment.

[0071] Computer programs do not necessarily correspond to files in a file system. A program may be stored within a single file provided to the requested program, within multiple interacting files (e.g., a file storing one or more modules, subprograms, or portions of code), or within a file containing other programs or data (e.g., one or more scripts stored within a markup language document).

[0072] A computer program may be deployed to run on a single computer or on multiple computers located at a single site or distributed across multiple sites and interconnected by a communications network.

[0073] Additionally, the logical flow and structural block diagrams described herein describe corresponding functions and corresponding acts and / or specific methods supported by the disclosed structural means, and can also be used to construct corresponding software structures and algorithms and their equivalents.

[0074] The processes and logic flows described herein are executable by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output.

[0075] Processors suitable for executing computer programs include, for example, general-purpose and special-purpose microprocessors, as well as any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from read-only memory, random-access memory, or both.

[0076] The core elements of a computer are one or more memory devices for storing instructions and data, and a processor for executing instructions. Additionally, a computer will typically be coupled to or include one or more mass storage devices, such as magnetic, magneto-optical, or optical disks, to receive data from, transfer data to, or both of these operations. However, a computer need not include such devices.

[0077] This description presents the best mode of the invention and provides examples to illustrate the invention and to enable those skilled in the art to make and use the invention. The specification, as written, is not intended to limit the invention to the specific terms set forth herein.

[0078] Accordingly, while the present invention has been described in detail with reference to the above-described examples, those skilled in the art will appreciate that modifications, variations, and variations can be made to these examples without departing from the scope of the present invention. In short, it is to be understood that to achieve the intended effects of the present invention, not all functional blocks depicted in the drawings must be separately included, nor must all orders depicted in the drawings be followed in the exact order depicted. Even if this is not the case, the technical scope of the present invention as set forth in the claims may still be encompassed.

[0079] [Explanation of symbols]

[0080] 100: SaaS Linked System

[0081] 110: API conversion section

[0082] 120: Call information generation unit

[0083] 130: Programming Department

[0084] 140: Form generation section

[0085] 150: User authentication section

Claims

1. In a SaaS linkage system for linking SaaS applications, An API conversion unit that converts APIs provided by one or more SaaS applications into API specifications; A call information generation unit that adds call information for calling the API to the API specification; and Includes a programming section that generates a calling program that calls the API based on the API specification, A SaaS-linked system characterized in that the call information includes information for selecting a call program and calculating the operating cost.

2. In paragraph 1, A SaaS linkage system, characterized in that the API specification converted by the API conversion unit includes information on call parameters and response parameters.

3. In paragraph 2, the call information is A SaaS linkage system characterized by including at least one of an API call price, an API call count limit, an API call available time, a response parameter price, and an API response time.

4. In paragraph 1, the SaaS linkage system, A SaaS linkage system characterized by further including a form generation unit that calls an API by inputting call parameters into a call program generated by a programming unit and checks whether expected response parameters corresponding to the input call parameters are normally output.

5. In paragraph 4, The form generation part obtains call parameters and response parameters from the API specification. A SaaS linkage system characterized by driving a calling program by inputting calling parameters and checking whether expected response parameters expected to be returned by the calling program are output.

6. In paragraph 5, The form generator performs a validation procedure to check whether the returned response parameters are identical to the expected response parameters. If the returned response parameters are not identical to the expected response parameters, The API conversion part reconverts the API into a text-based API specification, A SaaS-linked system characterized in that the programming section regenerates a calling program that calls an API based on a reconverted API specification.

7. In paragraph 5, the form generating unit A SaaS linkage system characterized by providing a table displaying call parameters, response parameters, and call information for each API.

8. In paragraph 1, the SaaS linkage system A SaaS linkage system further comprising a user authentication unit that performs user authentication when a calling program is run and accesses a SaaS application via an API.

9. In paragraph 1, The programming department creates a calling program that returns response parameters when calling the API with call parameters based on the API specification. A SaaS linkage system characterized by generating a calling program that outputs processed output values ​​using response parameters returned for each of multiple APIs.

10. In paragraph 1, The programming department creates a calling program that returns response parameters when calling the API with call parameters based on the API specification. A SaaS-linked system characterized by generating a calling program that causes the calling program to display call information and execute a step of obtaining user consent for the call information before the calling program calls the API.

Images