This section provides solutions to common errors that you may see while working with the API Platform.
If you have other issues, please post them to the Developer Forum.
Using Curl on Windows
All of the example commands use Linux/Unix command line syntax for quoting arguments. A single quote can be used as a wrapper for double-quote characters inside a pair of single quotes.
If you are using cURL from a Windows command prompt, Windows does not provide such multi-layered quoting. Under Windows, the outermost quotes must be the double-quote character and quotes within that string must doubled, two double-quote characters, where the following examples have one.
curl and HTTPS
The Apigee API requires SSL (https). If you encounter SSL Certificate problems in response to your cURL commands, you can:
- Update your certs file.
- Use a command line option to specify an alternate certs file.
- Manually decide that you can trust the api.enterprise.apigee.com site and use either the -k or --insecure options to the curl command to override the SSL certificate requirement.
Protocol https not supported or disabled in libcurl
Usually seen on machines running Windows. This means that you downloaded and installed a version of curl that did not include the libcurl package. Download a different package from http://curl.haxx.se/download.html, and make sure it includes libcurl for SSL.
HTTP Errors
HTTP 403: This an authorization failure. It means that the username and password combination you are using is not valid for the organization you specified. To test your credentials, login to https://enterprise.apigee.com/login. Once logged in check your account settings to see the organization name. In some situations, you may belong to multiple organizations. Make sure that you are using the correct credentials for you organization. Check your spelling. If you need an account, sign up here: https://enterprise.apigee.com/trial.
HTTP 404: The object wasn't found. This is usually happens because of misspelling in your request URL, but it may also happen if you try to update an object that doesn't exist (for example, the wrong revision of an API).
CLASSIFICATION_FAILURE
You may see this error when you submit a request to your API proxy after you deploy it to the Apigee platform. This error means that Apigee cannot determine which API proxy your request should be routed to. This usually happens because your request URL does not match the base path for any API proxies currently deployed in the environment. (Note that Apigee validates that all base paths are unique when a new API proxy is imported.)
- Verify the URI for your API by logging in to the Apigee UI at https://enterprise.apigee.com. Select the link to your API. At the top of the page, the URI for you API including the base path, displays at the top of the page.
- Make sure your API proxy is deployed. Your API proxy may be imported to Apigee, but may not be deployed to an environment. API proxies can only be invoked after they have been successfully deployed to an environment. (Note that the deploy tool used in this quick start both imports and deploys your API proxy to the environment you specify.)
- Make sure your request is being sent to the correct environment: http://{myorg}-test.apigee.net/weather versus http://{myorg}-prod.apigee.net/weather, for example.
Deploy Tool Errors
If you see the following result on import, it indicates that you are running the deploy tool from the wring directory.
Import failed to /v1/organizations/myorg/apis?action=import&name=weatherapi with status 500:
{
"code" : "messaging.config.beans.ImportFailed",
"message" : "Failed to import the bundle : java.util.zip.ZipException: ZIP file must have at least one entry",
"contexts" : [ ]
}
Get Help
If you have other issues, please post them to the Developer Forum.
