What details do you need to troubleshoot my API issue?

This article covers what our support team needs to troubleshoot an issue with the iplicit API. Providing this information upfront speeds up investigation, particularly for error 500 and error 400 responses.

---

Information to provide for any API issue

Include the following whenever you raise an API issue with iplicit support:

1. The customer name - only needed if you're a partner or developer working on their behalf
2. The iplicit environment you were using
3. What you were trying to do
4. The endpoint you were trying to reach
5. The exact error message you received
6. A screenshot of the error
7. A copy of the JSON - paste the text rather than a screenshot, so it can be checked directly.

---

Additional checks for error 500

If you're seeing an error 500 from the iplicit API, check the iplicit status page before contacting support – the issue may already be known and in progress.

---

Additional checks for error 400

An error 400 usually means something in the request itself needs correcting. Before contacting support, check:

• The response and request headers against the iplicit API reference
• The parameters in the request body against the iplicit API documentation
• The request for syntax errors – typos, extra whitespace, or invalid JSON formatting.

If you've checked all of the above and the issue persists, see 'Why is the API not connecting? – Error 500 or 400'.