Troubleshooting API

Common Reasons Why API Calls to FLG Fail

Error: 'No post data was provided'

Our server didn't receive the XML request it was expecting. This may be because:

• You made a HTTP GET request instead of POST - we expect the XML as the body/payload of the POST request.
• The POST didn't have the correct Content-Type header - use Content-Type: application/xml so our server knows you're sending XML.
• Whitespace before the XML content can cause problems - check for this too.

Error: 'The input could not be parsed'

We received something, but it didn't look like valid XML. This is almost always because:

• You didn't send XML - that's the only data format the API accepts.
• One or more XML tags weren't closed properly or don't match up - look for <tag><tag> or <tag></tagg> (should be <tag></tag>).
• Special characters weren't encoded - use predefined entities to describe &quot;, &amp;, &apos;, &lt; and &gt;. Learn more about XML's predefined entities.

Further Help

To help you troubleshoot, please send us a trace of the request and response. Pipedream is a great tool for this - it acts as a proxy between your server and the API, giving you full visibility into what was sent and received.

• It's very difficult for us to help without a trace - please get hold of one before getting in touch.
• Once you have it, we're ready to help!