# H5 Application FAQ

# 1. How to Register Custom APIs

Registering custom APIs for H5 applications is consistent with Mini-Programs, but does not support configuration via the FinClipConf.js file. Registration must be performed using loadExtApi. Debugging can be done using FinClip Studio version 2.0.25 or later.

For details, refer to ft.loadExtApi.

# 2. How Internal Requests Are Handled in H5 Applications

H5 applications are opened using an internal protocol, not the http(s) protocol.

Under the internal protocol, if a web request within the project uses a relative path address—for example, requesting /some/file.png—the underlying system will process it as a GET file request. It will then search for the file within the project directory; if found, it returns the file content; if not, it returns a request error.

Based on this rule, if you need to request an external service, the request URL must be specified as a complete address, for example: https://some.com/some/request.

# 3. Base Library Version Used by H5 Applications

Since H5 applications do not involve compilation and the Base Library version used is packaged and uploaded along with the application, it is not related to the online Base Library version.

In FinClip Studio, the version of the Base Library currently loaded for the H5 application can be viewed in the devtool's log panel. This will be the same version used after uploading or previewing.

© FinClip with ❤ , Since 2017