Avoiding Common Problems

This page discusses a wide range of issues that you might encounter when making requests to our API, along with suggestions for resolving them. If your problem is not listed here, please visit the Phone.com API Developer Community for further support.

Issues discussed include:

Connection Problems

If your application fails to connect to the Phone.com API service, check the following:

  • Are you are using the correct protocol? Our API requires connecting via HTTPS.
  • Is your client able to resolve the DNS name for our API servers: v1.api.phone.com
  • Can your client reach our API servers? Try pinging v1.api.phone.com.

Also, if you are receiving an HTTP error code, check our list of extended errors, which provides a detailed description of why your request is failing.

Application Not Receiving Events

If your application is not receiving call-control events (for inbound calls and asynchronous requests) or inbound SMS messages, check the following:

  • Make sure the main and backup (optional) URLs defined for your application are correct.
  • If you are including a fallback URL in your call-control script, make sure the URL is correct.
  • Note that the Phone.com API will send events using HTTP and HTTPS.
  • If you are using HTTPS, the server must have a valid certificate. Self-signed certificates will not be accepted.

JSON Syntax Errors

While JSON syntax is simple, it is easy to make small mistakes that are difficult to track. If our API returns an error indicating a problem with the syntax of the JSON document in your request (HTTP 400 Invalid Request code 400, Extended Error Code 10020), check the following:

  • Keys need to be enclosed in double quotes
  • Non-numeric values also need to be in double quotes
  • The last element of a list or array should not be followed by a comma

For more information, review JSON Syntax guidelines, and use a JSON validation tool to check your syntax.

Learn More: