CN117687623A - API code-free automatic receiving method and device - Google Patents
API code-free automatic receiving method and device Download PDFInfo
- Publication number
- CN117687623A CN117687623A CN202311850977.8A CN202311850977A CN117687623A CN 117687623 A CN117687623 A CN 117687623A CN 202311850977 A CN202311850977 A CN 202311850977A CN 117687623 A CN117687623 A CN 117687623A
- Authority
- CN
- China
- Prior art keywords
- information
- api
- data
- api call
- code
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 26
- 238000012545 processing Methods 0.000 claims description 16
- 230000000977 initiatory effect Effects 0.000 claims description 9
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 108091029480 NONCODE Proteins 0.000 claims 6
- 238000011161 development Methods 0.000 abstract description 11
- 238000004519 manufacturing process Methods 0.000 abstract description 3
- 238000007726 management method Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- WSFSSNUMVMOOMR-UHFFFAOYSA-N Formaldehyde Chemical compound O=C WSFSSNUMVMOOMR-UHFFFAOYSA-N 0.000 description 3
- 238000012795 verification Methods 0.000 description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an API code-free automatic receiving method and device, wherein the method comprises the following steps: acquiring a platform API call information table, wherein the platform API call information table is used for recording detailed information of each API call, and comprises configuration codes and form codes; acquiring a platform API call configuration table, wherein the platform API call configuration table comprises the configuration code, and the platform API call information table and the platform API call configuration table are associated through the configuration code or the form code; and generating an API access module according to the platform API call information table and the platform API call configuration table. According to the method and the device for automatically receiving the API code-free, the API access module is generated according to the platform API call information table and the platform API call configuration table, so that the threshold of API access is reduced, product personnel can access various types of API data to perform unified scheduling management, repeated development work is reduced, data access efficiency is improved, and data production cost is reduced.
Description
Technical Field
The invention relates to the technical field of database development, in particular to an API code-free automatic receiving method and device.
Background
At present, code-free integration platforms such as Zapier, integromat and n8n, etc., allow users to create workflows through a graphical interface, connecting different applications and services together. These platforms provide a number of pre-built API (Application Programming Interface ) connectors that enable users to implement the delivery and handling of data streams through simple drag and drop operations.
Low code development platforms, such as Microsoft Power Platform and OutSystems, provide more advanced custom functionality, allowing users to create complex business logic and applications with a small amount of code. These platforms typically include code-free reception functionality that allows a user to easily interact with external APIs.
Server code-free platforms, such as AWS Lambda, *** Cloud Functions, azure Functions, etc., allow developers to run code without having to manage the server. These platforms provide event-driven programming models that enable developers to associate functions with different events.
However, for complex financial data access, the existing code-free and low-code platforms have insufficient support for special data processing in the financial field, and are difficult to meet the requirement of high customization in the financial industry, so that the access difficulty is high. In the financial data access, due to the universality of the prior art, additional coding work is required for special requirements and highly customized financial data processing, so that development cost is increased, and cost control of enterprises is not facilitated.
It is therefore desirable to provide a method and apparatus for automatically receiving API code-free signals, which can solve the above-mentioned problems.
Disclosure of Invention
The invention provides an API code-free automatic receiving method and device aiming at the problems and the defects existing in the prior art.
The invention solves the technical problems by the following technical proposal:
the invention provides an API code-free automatic receiving method, which comprises the following steps:
acquiring a platform API call information table, wherein the platform API call information table is used for recording detailed information of each API call, and comprises configuration codes and form codes;
acquiring a platform API call configuration table, wherein the platform API call configuration table comprises the configuration code, and the platform API call information table and the platform API call configuration table are associated through the form code or the configuration code;
and generating an API access module according to the platform API call information table and the platform API call configuration table.
Preferably, the platform API call information table further includes:
URL, API interface code, call parameter information, file storage path, data source code for subsequent data processing;
the warehouse-in database and the warehouse-in table are called fully in English and are used for recording the storage position of data;
a valid flag for identifying whether the current record is valid;
the file storage path, the warehouse-in database and the form information cannot be empty at the same time;
when the file storage path is empty, the file storage path indicates that the file is not required to be stored in a file form, and the data is stored in a specified database form;
and when the warehouse-in database and the form information are empty, the data are stored in a specified file storage path, wherein the data do not need to be stored in the database.
Preferably, the platform API call configuration table further comprises:
the system comprises a data source, a call type and Token information, wherein the data source is used for defining the call mode of an API, authenticating and returning result processing, the data source is used for designating the data source of the API call, the call type is used for defining the call mode of the API, and the Token information is used for storing Token information of authenticating;
the system comprises an update time and a valid mark, wherein the update time is used for marking and tracking the update and deletion of data, and the valid mark is used for marking the validity of a record.
Preferably, the Token information has a valid period, the Token information is stored in a file, the file is read before an API is called to obtain the Token information, when the Token information is invalid when the valid period is exceeded, new Token information is obtained again, and the new Token information is covered by the invalid Token information.
Preferably, the API access module queries configuration information according to the configuration code:
if the acquisition is incremental, acquiring date information at the end of the last acquisition through a log table to acquire newly added data;
initiating a data acquisition request to a data terminal, and exiting if multiple retries fail;
and if the data is successfully acquired, judging to put the data in storage or store the file according to the information in the platform API call configuration table.
The invention also provides an API code-free automatic receiving device, which comprises:
the platform API call information table acquisition unit is used for acquiring a platform API call information table, wherein the platform API call information table is used for recording detailed information of each API call, and comprises configuration codes and form codes;
a platform API call configuration table obtaining unit, configured to obtain a platform API call configuration table, where the platform API call configuration table includes the configuration code, and the platform API call information table and the platform API call configuration table are associated by the form code or the configuration code;
and the API access module generating unit is used for generating an API access module according to the platform API call information table and the platform API call configuration table.
Preferably, the platform API call information table further includes:
URL, API interface code, call parameter information, file storage path, data source code for subsequent data processing;
the warehouse-in database and the warehouse-in table are called fully in English and are used for recording the storage position of data;
a valid flag for identifying whether the current record is valid;
the file storage path, the warehouse-in database and the form information cannot be empty at the same time;
when the file storage path is empty, the file storage path indicates that the file is not required to be stored in a file form, and the data is stored in a specified database form;
and when the warehouse-in database and the form information are empty, the data are stored in a specified file storage path, wherein the data do not need to be stored in the database.
Preferably, the platform API call configuration table further comprises:
the system comprises a data source, a call type and Token information, wherein the data source is used for defining the call mode of an API, authenticating and returning result processing, the data source is used for designating the data source of the API call, the call type is used for defining the call mode of the API, and the Token information is used for storing Token information of authenticating;
the system comprises an update time and a valid mark, wherein the update time is used for marking and tracking the update and deletion of data, and the valid mark is used for marking the validity of a record.
Preferably, the Token information has a valid period, the Token information is stored in a file, the file is read before an API is called to obtain the Token information, when the Token information is invalid when the valid period is exceeded, new Token information is obtained again, and the new Token information is covered by the invalid Token information.
Preferably, the API access module queries configuration information according to the configuration code:
if the acquisition is incremental, acquiring date information at the end of the last acquisition through a log table to acquire newly added data;
initiating a data acquisition request to a data terminal, and exiting if multiple retries fail;
and if the data is successfully acquired, judging to put the data in storage or store the file according to the information in the platform API call configuration table.
Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:
the method and the device for automatically receiving the API code comprise the steps of obtaining a platform API call information table, wherein the platform API call information table is used for recording detailed information of each API call, and comprises configuration codes and form codes; acquiring a platform API call configuration table, wherein the platform API call configuration table comprises the configuration code, and the platform API call information table and the platform API call configuration table are associated through the form code or the configuration code; the system is an expanding type access tool, so that the product personnel can access various types of API data to perform unified scheduling management, development repeatability development work is reduced, data access efficiency is improved, and data production cost is reduced;
further, the Token information has a valid period, the Token information is stored in a file, the file is read before calling the API to obtain the Token information, when the Token information is invalid when the valid period is exceeded, new Token information is obtained again, the new Token information is covered by the invalid Token information, therefore, one Token is not required to be applied again every time data is requested, and the efficiency of calling the API is greatly improved;
further, the API access module queries configuration information according to the configuration code: if the acquisition is incremental, acquiring date information at the end of the last acquisition through a log table to acquire newly added data; initiating a data acquisition request to a data terminal, and exiting if multiple retries fail; if the data is successfully acquired, the data is put in storage or stored according to the information in the platform API call configuration table, so that the efficiency of automatically receiving the data by the API is improved, and the data receiving process is accelerated.
Drawings
FIG. 1 is a flow chart of an API code-free automatic receiving method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an API code-free automatic receiving device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The technical scheme of the invention is described in detail below by specific examples. The following embodiments may be combined with each other, and some embodiments may not be repeated for the same or similar concepts or processes.
Based on the problems existing in the prior art, as shown in fig. 1, the invention provides an API code-free automatic receiving method, which comprises the following steps:
step S101: acquiring a platform API call information table, wherein the platform API call information table is used for recording detailed information of each API call, and comprises configuration codes and form codes;
step S102: acquiring a platform API call configuration table, wherein the platform API call configuration table comprises the configuration code, and the platform API call information table and the platform API call configuration table are associated through the form code or the configuration code;
step S103: and generating an API access module according to the platform API call information table and the platform API call configuration table.
In a specific implementation, the platform API call information table further includes:
URL (Uniform Resource Locator, uniform resource location system), API interface code, call parameter information, file storage path, data source code for subsequent data processing;
the warehouse-in database and the warehouse-in table are called fully in English and are used for recording the storage position of data;
a valid flag for identifying whether the current record is valid;
the file storage path, the warehouse-in database and the form information cannot be empty at the same time;
when the file storage path is empty, the file storage path indicates that the file is not required to be stored in a file form, and the data is stored in a specified database form;
and when the warehouse-in database and the form information are empty, the data are stored in a specified file storage path, wherein the data do not need to be stored in the database.
Specifically, the platform API call information table further includes fields such as a data flag, release time, update ID, and the like. The platform API call information table is a key table in the system and is used for recording key information of each API call. The table structure comprises fields such as configuration codes, form codes, API interface codes and the like, record calling parameters, data source codes, data storage paths and the like. Through the platform API call information table, the system can track and manage the call condition of the API, and ensure the validity of the data. The design of each field enables it to provide detailed API call information, including update time, valid flags, etc., providing necessary support for system operation and data management.
In a specific implementation, the platform API call configuration table further includes:
the system comprises a data source, a calling type and Token information, wherein the data source is used for defining the calling mode of an API, verifying identity and returning result processing, the data source is used for designating the data source of the API calling, the calling type is used for defining the calling mode of the API, and the Token information is used for storing Token information of verifying identity;
the system comprises an update time and a valid mark, wherein the update time is used for marking and tracking the update and deletion of data, and the valid mark is used for marking the validity of a record.
Specifically, the platform API call configuration table further includes fields such as a data source account, a data source password, an information header type, information header information, an API interface code name, a call parameter form, a field name, a return result path, an update ID name, a delete time name, a release time, and an update ID.
Configuration ID: associated with a particular configuration in the system, each API call is associated with a corresponding configuration, and parameters and settings of the call are determined.
Data source: the data source of the API call is specified, defining from which data source the data is to be retrieved.
Data source account and data source password: authentication information associated with the data source connection is stored to ensure that the system has access to the specified data source.
Information header type and information header information: the information header used in the set API request, including type and specific information, may contain authentication or other custom information.
Call type: defining calling modes of the API, such as GET, POST and the like, and guiding the system how to communicate with the data source.
Token information: storing token information for authentication ensures that the API call is safe and compliant.
API interface code name: the code name of the API interface is identified for use in constructing the complete API request address.
Calling parameter forms: the form of parameters used in the API call is specified, such as JSON, XML, etc.
Field name: fields that need to be used in the data obtained from the data source are defined to help the system identify and process the returned information.
Return result path: indicating where the system should store the results returned by the API call, possibly a file path or database table.
Update ID, update time, delete time: update and delete operations for identifying and tracking data, support data synchronization and version management.
Valid tag name: the validity of the record is identified, ensuring that only valid API call configurations are used by the system.
The comprehensive use of these fields forms a complete platform API call configuration table, ensuring that the system can flexibly and safely interact with different data sources according to configuration.
In a specific implementation, the Token information has a valid period, the Token information is stored in a file, the file is read before an API is called to obtain the Token information, when the Token information is invalid when the valid period is exceeded, new Token information is obtained again, and the new Token information is covered by the invalid Token information.
In a specific implementation, the API access module queries configuration information according to the configuration code:
if the acquisition is incremental, acquiring date information at the end of the last acquisition through a log table to acquire newly added data;
initiating a data acquisition request to a data terminal, and exiting if multiple retries fail;
and if the data is successfully acquired, judging to put the data in storage or store the file according to the information in the platform API call configuration table.
Specifically, configuration information (request link, request parameters, etc.) is filled in the database, the config_ids of the same category are the same (e.g. 1001), and different data tab_ids of the same category are different (e.g. 10010050); the request is initiated by the dispatch initiation client with a parameter of configuration id (config_id). The server receives the request, and queries the database for configuration information according to the configuration id.
Based on the problems existing in the prior art, as shown in fig. 2, the present invention further provides an API code-free automatic receiving device, which includes:
a platform API call information table obtaining unit 21, configured to obtain a platform API call information table, where the platform API call information table is used to record detailed information of each API call, and the platform API call information table includes a configuration code and a form code;
a platform API call configuration table obtaining unit 22, configured to obtain a platform API call configuration table, where the platform API call configuration table includes the configuration code, and the platform API call information table and the platform API call configuration table are associated through the form code or the configuration code;
an API access module generating unit 23, configured to generate an API access module according to the platform API call information table and the platform API call configuration table.
In a specific implementation, the platform API call information table further includes:
URL, API interface code, call parameter information, file storage path, data source code for subsequent data processing;
the warehouse-in database and the warehouse-in table are called fully in English and are used for recording the storage position of data;
a valid flag for identifying whether the current record is valid;
the file storage path, the warehouse-in database and the form information cannot be empty at the same time;
when the file storage path is empty, the file storage path indicates that the file is not required to be stored in a file form, and the data is stored in a specified database form;
and when the warehouse-in database and the form information are empty, the data are stored in a specified file storage path, wherein the data do not need to be stored in the database.
In a specific implementation, the platform API call configuration table further includes:
the system comprises a data source, a call type and Token information, wherein the data source is used for defining the call mode of an API, authenticating and returning result processing, the data source is used for designating the data source of the API call, the call type is used for defining the call mode of the API, and the Token information is used for storing Token information of authenticating;
the system comprises an update time and a valid mark, wherein the update time is used for marking and tracking the update and deletion of data, and the valid mark is used for marking the validity of a record.
In a specific implementation, the Token information has a valid period, the Token information is stored in a file, the file is read before an API is called to obtain the Token information, when the Token information is invalid when the valid period is exceeded, new Token information is obtained again, and the new Token information is covered by the invalid Token information.
In a specific implementation, the API access module queries configuration information according to the configuration code:
if the acquisition is incremental, acquiring date information at the end of the last acquisition through a log table to acquire newly added data;
initiating a data acquisition request to a data terminal, and exiting if multiple retries fail;
and if the data is successfully acquired, judging to put the data in storage or store the file according to the information in the platform API call configuration table.
The implementation of the present invention will be described below by taking a specific example as an example of an API that generates the platform API call configuration table pfm_api_call_config.
Firstly, filling configuration information in an API access module, wherein the configuration information comprises a data source account, a data source password, an information head type, token information, an API interface code name, a field name and the like.
The data source account and the password are used for storing authentication information related to the data source connection, so that the system is ensured to have access to the designated data source; the information header type is authorization, and is used for setting the information header in the API request, including type and specific information, and possibly including identity verification or other customized information; token information: storing token information for identity verification, and ensuring that the API call is safe and compliant; the calling type is a GET method, and the guidance system communicates with the data source in a GET mode; the call parameter form is apikey=um 7S3pjo & begin_date= { start time } & end_date= { END time } & pagesize= { page size } & pagenum= { page number }, apiKey: a key for authentication, identifying the identity of the caller to ensure that the API call is legitimate and secure, begin_date: a parameter representing a start time, typically used to specify a starting point of a time range in which data needs to be acquired, end_date: a parameter indicating an end time, specifying an end point of a time range in which data is acquired, pageSize: the method is used for specifying the data quantity returned by each page, controlling the number of data pieces acquired by each call and the pageNum: the number of pages requested is specified for paging the acquired data, particularly in the case of a large amount of data, so as to effectively manage the amount of data.
The platform API call configuration table and the platform API call information table are associated through config_id, call_para_info in the platform API call information table is used as a parameter to be transmitted to call_para_form in the platform API call configuration table, the starting time and the ending time are configured by the platform, and a URL field and a call_para_info field in the platform API call information table are spliced into a complete request URL in a call_para_form form, for example:
URL：
http://open.sseinfo.com/api/v1/sseForSZJR/externalCall/szse_jjjjj/openAPI/szse_lrb?
call_para_info：{}&{}&{200}&{}
call_para_form: apikey=um 7S3pjo & begin_date= { start time } & end_date= { END time } & pageSize = { page size } & pageNum = { page number }
Complete request URL:
http://open.sseinfo.com/api/v1/sseForSZJR/externalCall/szse_jjjjj/openAPI/szse_lrbBEGIN_DATE=2022-01-01&END_DATE=2022-12-31&pageSize=50&pageNum=1
data is requested from the server specified by the URL and stored in the corresponding database table.
In summary, the method and device for automatically receiving an API without code provided by the embodiments of the present invention acquire a platform API call information table, where the platform API call information table is used to record detailed information of each API call, and the platform API call information table includes a configuration code and a form code; acquiring a platform API call configuration table, wherein the platform API call configuration table comprises the configuration code, and the platform API call information table and the platform API call configuration table are associated through the form code or the configuration code; the system is an expanding type access tool, so that the product personnel can access various types of API data to perform unified scheduling management, development repeatability development work is reduced, data access efficiency is improved, and data production cost is reduced;
further, the Token information has a valid period, the Token information is stored in a file, the file is read before calling the API to obtain the Token information, when the Token information is invalid when the valid period is exceeded, new Token information is obtained again, the new Token information is covered by the invalid Token information, therefore, one Token is not required to be applied again every time data is requested, and the efficiency of calling the API is greatly improved;
further, the API access module queries configuration information according to the configuration code: if the acquisition is incremental, acquiring date information at the end of the last acquisition through a log table to acquire newly added data; initiating a data acquisition request to a data terminal, and exiting if multiple retries fail; if the data is successfully acquired, the data is put in storage or stored according to the information in the platform API call configuration table, so that the automatic data receiving efficiency of the API is improved, and the data receiving process is accelerated;
furthermore, the user can realize the standardization and automatic processing of the data through configuration, so that the repeated work of manually processing the data is avoided, and the consistency and accuracy of data access are improved;
furthermore, because no deep programming knowledge is needed, the developer can complete the financial data access task more quickly, and the training cost and the development period are reduced, so that the overall development cost is reduced;
further, through the visual interface, a user can easily manage and monitor the configuration and the running state of the data, so that the centralized management of the financial data access is realized, and the maintainability and the monitoring performance of the system are improved;
further, more people can participate in the development and management of the API, the flexibility and the efficiency of the service are improved, powerful support is provided for digital transformation, and enterprises are promoted to adapt to changing market environments more rapidly.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.
Claims (10)
1. An API code-less automatic reception method, the method comprising:
acquiring a platform API call information table, wherein the platform API call information table is used for recording detailed information of each API call, and comprises configuration codes and form codes;
acquiring a platform API call configuration table, wherein the platform API call configuration table comprises the configuration code, and the platform API call information table and the platform API call configuration table are associated through the form code or the configuration code;
and generating an API access module according to the platform API call information table and the platform API call configuration table.
2. The API non-code automatic reception method as recited in claim 1, wherein said platform API call information table further comprises:
URL, API interface code, call parameter information, file storage path, data source code for subsequent data processing;
the warehouse-in database and the warehouse-in table are called fully in English and are used for recording the storage position of data;
a valid flag for identifying whether the current record is valid;
the file storage path, the warehouse-in database and the form information cannot be empty at the same time;
when the file storage path is empty, the file storage path indicates that the file is not required to be stored in a file form, and the data is stored in a specified database form;
and when the warehouse-in database and the form information are empty, the data are stored in a specified file storage path, wherein the data do not need to be stored in the database.
3. The API non-code automatic reception method as recited in claim 1, wherein said platform API call configuration table further comprises:
the system comprises a data source, a call type and Token information, wherein the data source is used for defining the call mode of an API, authenticating and returning result processing, the data source is used for designating the data source of the API call, the call type is used for defining the call mode of the API, and the Token information is used for storing Token information of authenticating;
the system comprises an update time and a valid mark, wherein the update time is used for marking and tracking the update and deletion of data, and the valid mark is used for marking the validity of a record.
4. The API non-code automatic reception method as set forth in claim 3, wherein said Token information has a valid period, said Token information is stored in a file, said file is read before calling an API to acquire Token information, when said Token information is invalid when said valid period is exceeded, new Token information is acquired again, and said new Token information is covered with said already invalid Token information.
5. The API transcoding automatic reception method of claim 3, wherein said API access module queries configuration information according to said configuration code:
if the acquisition is incremental, acquiring date information at the end of the last acquisition through a log table to acquire newly added data;
initiating a data acquisition request to a data terminal, and exiting if multiple retries fail;
and if the data is successfully acquired, judging to put the data in storage or store the file according to the information in the platform API call configuration table.
6. An API code-less automatic receiving device, the device comprising:
the platform API call information table acquisition unit is used for acquiring a platform API call information table, wherein the platform API call information table is used for recording detailed information of each API call, and comprises configuration codes and form codes;
a platform API call configuration table obtaining unit, configured to obtain a platform API call configuration table, where the platform API call configuration table includes the configuration code, and the platform API call information table and the platform API call configuration table are associated by the form code or the configuration code;
and the API access module generating unit is used for generating an API access module according to the platform API call information table and the platform API call configuration table.
7. The API non-code automatic receiving device of claim 6, wherein the platform API call information table further comprises:
URL, API interface code, call parameter information, file storage path, data source code for subsequent data processing;
the warehouse-in database and the warehouse-in table are called fully in English and are used for recording the storage position of data;
a valid flag for identifying whether the current record is valid;
the file storage path, the warehouse-in database and the form information cannot be empty at the same time;
when the file storage path is empty, the file storage path indicates that the file is not required to be stored in a file form, and the data is stored in a specified database form;
and when the warehouse-in database and the form information are empty, the data are stored in a specified file storage path, wherein the data do not need to be stored in the database.
8. The API non-code automatic receiving device of claim 6, wherein the platform API call configuration table further comprises:
the system comprises a data source, a call type and Token information, wherein the data source is used for defining the call mode of an API, authenticating and returning result processing, the data source is used for designating the data source of the API call, the call type is used for defining the call mode of the API, and the Token information is used for storing Token information of authenticating;
the system comprises an update time and a valid mark, wherein the update time is used for marking and tracking the update and deletion of data, and the valid mark is used for marking the validity of a record.
9. The API non-code automatic reception apparatus as recited in claim 8, wherein the Token information has a valid period, the Token information is stored in a file, the file is read before calling the API to acquire the Token information, when the Token information is invalid when the valid period is exceeded, new Token information is acquired again, and the new Token information is covered with the already invalid Token information.
10. The API transcoding method of claim 8, wherein said API access module queries configuration information in accordance with said configuration code:
if the acquisition is incremental, acquiring date information at the end of the last acquisition through a log table to acquire newly added data;
initiating a data acquisition request to a data terminal, and exiting if multiple retries fail;
and if the data is successfully acquired, judging to put the data in storage or store the file according to the information in the platform API call configuration table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311850977.8A CN117687623B (en) | 2023-12-29 | 2023-12-29 | API code-free automatic receiving method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311850977.8A CN117687623B (en) | 2023-12-29 | 2023-12-29 | API code-free automatic receiving method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117687623A true CN117687623A (en) | 2024-03-12 |
| CN117687623B CN117687623B (en) | 2024-04-26 |
Family
ID=90137138
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311850977.8A Active CN117687623B (en) | 2023-12-29 | 2023-12-29 | API code-free automatic receiving method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117687623B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111104535A (en) * | 2019-11-20 | 2020-05-05 | 中国第一汽车股份有限公司 | Data management system and data management method |
| CN112069218A (en) * | 2020-11-16 | 2020-12-11 | 浙江岩华文化科技有限公司 | Big data real-time processing method and device, electronic device and storage medium |
| CN113127280A (en) * | 2021-04-14 | 2021-07-16 | 北京优奥创思科技发展有限公司 | API interface automatic input method and system |
| CN113485824A (en) * | 2021-04-24 | 2021-10-08 | 中电长城网际***应用广东有限公司 | API (application programming interface) interface management method of integrated operation and maintenance platform |
| CN114493884A (en) * | 2022-02-16 | 2022-05-13 | 中国工商银行股份有限公司 | Data interaction method, device and system |
| CN114490124A (en) * | 2022-01-19 | 2022-05-13 | 平安普惠企业管理有限公司 | Method, device, equipment and medium for calling Application Programming Interface (API) |
| CN115543280A (en) * | 2022-10-10 | 2022-12-30 | 武汉众邦银行股份有限公司 | Method and device for realizing data interface based on dynamic configuration |
| CN116225422A (en) * | 2023-03-12 | 2023-06-06 | 天翼云科技有限公司 | OpenAPI calling method and device |
| US20230401225A1 (en) * | 2022-06-10 | 2023-12-14 | Capital One Services, Llc | Methods and system for detecting unmanaged resources in cloud-based data warehousing system |
-
2023
- 2023-12-29 CN CN202311850977.8A patent/CN117687623B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111104535A (en) * | 2019-11-20 | 2020-05-05 | 中国第一汽车股份有限公司 | Data management system and data management method |
| CN112069218A (en) * | 2020-11-16 | 2020-12-11 | 浙江岩华文化科技有限公司 | Big data real-time processing method and device, electronic device and storage medium |
| CN113127280A (en) * | 2021-04-14 | 2021-07-16 | 北京优奥创思科技发展有限公司 | API interface automatic input method and system |
| CN113485824A (en) * | 2021-04-24 | 2021-10-08 | 中电长城网际***应用广东有限公司 | API (application programming interface) interface management method of integrated operation and maintenance platform |
| CN114490124A (en) * | 2022-01-19 | 2022-05-13 | 平安普惠企业管理有限公司 | Method, device, equipment and medium for calling Application Programming Interface (API) |
| CN114493884A (en) * | 2022-02-16 | 2022-05-13 | 中国工商银行股份有限公司 | Data interaction method, device and system |
| US20230401225A1 (en) * | 2022-06-10 | 2023-12-14 | Capital One Services, Llc | Methods and system for detecting unmanaged resources in cloud-based data warehousing system |
| CN115543280A (en) * | 2022-10-10 | 2022-12-30 | 武汉众邦银行股份有限公司 | Method and device for realizing data interface based on dynamic configuration |
| CN116225422A (en) * | 2023-03-12 | 2023-06-06 | 天翼云科技有限公司 | OpenAPI calling method and device |
Non-Patent Citations (2)
| Title |
|---|
| S SIVABALAN等: "Heterogeneous Data Integration with ELT and Analytical MPP Database for Data Analysis Application", 《2021 INNOVATIONS IN POWER AND ADVANCED COMPUTING TECHNOLOGIES (I-PACT)》, 8 February 2022 (2022-02-08), pages 1 - 5 * |
| 王世杰: "基于异构数据源的交通数据服务***设计与实现", 《CNKI优秀硕士学位论文全文库 信息科技辑》, no. 04, 15 April 2021 (2021-04-15), pages 138 - 314 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117687623B (en) | 2024-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108319547B (en) | Test case generation method, device and system | |
| WO2015074554A1 (en) | Method and device for message synchronization | |
| WO2019080460A1 (en) | Management method for official wechat account, electronic device and computer-readable storage medium | |
| US8073887B2 (en) | Representational state transfer (REST) service import editor | |
| CN107133160B (en) | Server and client | |
| CN111367531B (en) | Code processing method and device | |
| CN114443905A (en) | Interface document updating method and device, electronic equipment and readable storage medium | |
| CN117687623B (en) | API code-free automatic receiving method and device | |
| JP2024508452A (en) | Hosting event-based applications | |
| CN113485927A (en) | Test data generation method, device, equipment and storage medium | |
| CN110457010B (en) | Method and device for batch changing task list based on collaboration platform | |
| CN112241625A (en) | Method and system for automatically generating contract document based on java language | |
| Ma et al. | Modularized and Flow-Based Approach to Chatbot Design and Deployment. | |
| CN115185841A (en) | System reconfiguration test method, device, equipment and storage medium | |
| CN114928603A (en) | Client software upgrading method and device, electronic equipment and medium | |
| CN114186966A (en) | Document approval method, system, device and computer readable storage medium | |
| CN111400245B (en) | Art resource migration method and device | |
| CN114416386A (en) | Resource processing method and device | |
| CN113672225A (en) | User interface processing method, device, equipment and storage medium | |
| CN112433946A (en) | Interface test management method, device, equipment and storage medium | |
| KR102589989B1 (en) | System for managing simple approval requests using email and the operating method thereof | |
| CN113626409B (en) | Test data processing method, device, equipment and storage medium | |
| CN109445964B (en) | Method and device for data transmission with SAP system in external system | |
| CN112579215B (en) | Scheduling function generation method and device | |
| CN100512136C (en) | Command processing in a telecommunications network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |