On this page

Show all

Help Center/ API Request Signing Guide/ Developer Guide/ FAQs/ What Should I Do If "The API does not exist or has not been published in the environment." Is Displayed?

What Should I Do If "The API does not exist or has not been published in the environment." Is Displayed?

Updated on 2023-09-11 GMT+08:00

View PDF

If an open API in APIG failed to be called, troubleshoot the failure by performing the following operations:

The domain name, request method, or path used for calling the API is incorrect.
- For example, an API created using the POST method is called with GET.
- Missing a slash (/) in the access URL will lead to a failure in matching the URL in the API details. For example, URLs http://7383ea59c0cd49a2b61d0fd1d351a619.apigw.region.cloud.com/test/ and http://7383ea59c0cd49a2b61d0fd1d351a619.apigw.region.cloud.com/test represent two different APIs.
The API has not been published. APIs can be called only after they have been published in an environment. For details, see Publishing an API. If the API has been published in a non-production environment, check whether the X-Stage header in the request is the name of the environment.
The domain name is resolved incorrectly. If the domain name, request method, and path for calling the API are correct and the API has been published in an environment, the API may not be correctly resolved to the group to which the API belongs. For example, if you have multiple API groups and each group has an independent domain name, the API may be called using the independent domain name of another group. Ensure that the API is being called using the correct domain name.
Check whether the API allows OPTIONS cross-region requests. If yes, enable cross-origin resource sharing (CORS) for the API, and create an API that uses the OPTIONS method. For details, see CORS.

Parent topic: FAQs

Previous topic: What Should I Do If the App Authentication Information Is Incorrect?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot