Why is the API not connecting? - Error 500 or 400

This article covers two connection errors you may see when calling the iplicit API: error 500 and error 400. Each has a different cause and a different fix, covered separately below.

---

Error 500 when connecting to the iplicit API

An error 500 ("Internal Server Error") from the iplicit API is a generic response meaning the server hit a problem it couldn't complete the request through – for example, a database connection issue. This is a system-side problem, not something wrong with your request.

In most cases, error 500 is temporary. Try these steps in order:

1. Check the iplicit status page for any known issue affecting the API
2. If nothing is reported, wait a moment and resubmit the same request – it will often succeed on retry

If the error persists with no known status issue, contact iplicit support.
See 'What details do you need to troubleshoot an API issue' for what to include.

---

Error 400 when connecting to the iplicit API

An error 400 ("Bad Request") from the iplicit API means something in the request you sent needs correcting, rather than a problem on iplicit's side. You'll need to fix the request and resubmit it.

Work through these checks:

1. Look for typos, extra whitespace, or invalid JSON formatting in the request
2. If you're using an API tool such as Postman, use it to verify the data you're sending is correct
3. Compare the request against the iplicit API guide and iplicit API reference, checking:
   • The request headers
   • The parameters in the request body
   • The query parameters
   • The HTTP method being used
4. If the request contains special characters, try turning off encoding in your API tool.

If the error persists after checking all of the above, contact iplicit support with a screenshot of the error. 
See 'What details do you need to troubleshoot an API issue' for the full list of what to include.