ThirdPartyAPI-v2
Call the ThirdPartyAPI-v2 extension to configure web APIs and call third-party APIs.
Notes and Constraints
- The ThirdPartyAPI-v2 extension requires certificate verification. Custom certificate is not supported.
- If the API return code is not 2XX, the operation fails.
Adding the Extension with GUI
Add the ThirdPartyAPI-v2 extension when you orchestrate a pipeline. Set parameters as show in Table 1.
Parameter |
Description |
---|---|
Name |
Extension name.
|
API Method |
Select GET, POST, PATCH, PUT, or DELETE. |
API URL |
API that can be called by the public network. Certificate verification is required. |
API Header |
Configure key-value pairs. |
API Parameter |
Configure key-value pairs. |
API Body |
If the request method is POST, PATCH, or PUT, enter the body in JSON format. |
API Output |
The root object name is response, which includes multiple outputs.
|
Adding the Extension with YAML
Add the ThirdPartyAPI-v2 extension when you orchestrate a pipeline. Configure the YAML syntax as follows:
- ThirdPartyAPI-v2
uses: official_third_part_invoke with: API_METHOD: GET API_URL: htps://demo API_HEADER: '[{"key":"Content-Type","value":"application/json"}]' API_PARAM: '[{"key":"name","value":"value"}]' API_BODY: "{}" API_OUTPUT: '[{"key":"code","value":"response.status"}]'
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot