You can use OpenAPI to send requests to FlightHub 2's on-premises deployment service. Include the corresponding Header / Path / Query / Body parameters in the request according to the interface specification. The system returns processing results based on the request handling.Service Endpoint#
The endpoint domain is determined by your on-premises deployment. Please confirm with the deployment party; all interface paths are prefixed with /openapi/v2.0/.The complete call address is in the form:https://<your-private-domain>/openapi/v2.0/...
The on-premises version does not have the multi-Region endpoints of the public cloud; all calls point to your private domain.
Communication Protocol#
It is recommended to use the HTTPS protocol for request communication. Whether to enable HTTP concurrently is determined by the on-site deployment; for production environments, it is recommended to enable HTTPS only.Character Encoding#
Requests and return results are encoded using the UTF-8 charset. JSON request bodies should explicitly specify:Content-Type: application/json; charset=utf-8
Request Method#
According to the specific definition of each interface, choose GET / POST / PUT / DELETE to initiate the request.File Upload Convention#
FlightHub 2 OpenAPI does not accept direct file uploads: the caller first uploads the file to object storage using the temporary credentials (STS) of the object storage, and then calls the "Upload Completion Callback" interface of the corresponding business module to complete the entry. See Common Foundation for details.Interface Limits#
The specific rate limits / request body size / timeout thresholds are determined by your on-premises deployment gateway. Please confirm with the deployment party and design reasonable client retry and backoff strategies; business-dimension limits (such as concurrency per organization / per project) are subject to each interface documentation.