REST API quick registration method, device and system

Abstract

The invention discloses a REST (Representational State Transfer) API (Application Programming Interface) quick registration method, device and system. The method includes that an API registration table device receives basic information of a REST API input by a user; an API analyzer extracts a parameter list and a calling example of the REST API from a request packet and a response packet of the REST API so as to implement the whole REST API registration process. According to the invention, through extracting input / output parameters and a calling request / response example of the API from the request packet and the response packet of the REST API, complex parameter and example recording processes are avoided, so that flexible, quick and consistent REST API registration management is realized.

Description

technical field [0001] The invention relates to the field of interface opening in the mobile Internet field, in particular to a RESTAPI quick registration method, device and system. Background technique [0002] REST (Representational State Transfer, Representational State Transfer) API (Application Programming Interface, Application Programming Interface) is a lightweight service interface based on HTTP (HyperText Transfer Protocol, Hypertext Transfer Protocol), which has become the mainstream interface form of major open platforms . [0003] The REST API needs to be registered and published in the open platform before it can be opened to the outside world for third-party viewing and calling, such as figure 1 The prior art REST API registration management methods shown all have some problems, and it is difficult to adapt to the requirements of the rapid increase in the number of APIs in the API economy era. [0004] Manual registration method: manually enter the informati...

AI Technical Summary

Problems solved by technology

However, most REST APIs have not yet been modeled. Before registration, model scripts must be written for the API, which requires additional API model editing and maintenance workload, and the current three API description models (Swagger, APIBlueprint, and RAML) are not perfect. It is impossible to describe all REST API forms. For example, none of the three supports the emerging YAML (Yet Another Markup Language, another markup language) data format and Token token data type. Only RAML supports XML (Extensible Markup Language, Extensible Markup Language ), the registration method based on the API model is less flexible

Images