API errcode 11 XML Parsing Error. unclosed token

Question

So my Quickbase app records are created via an API. I've had no issues and been able to solve all XML errors thus far. This one stumped me.
All tags are closed in the XML. I've checked multiple times. What could be causing this error?
&lt;qdbapi&gt;&lt;usertoken&gt;xxxxxxxxxxxx&lt;/usertoken&gt;&lt;field fid="75"&gt;2024&lt;/field&gt;&lt;field fid="76"&gt;9&lt;/field&gt;&lt;field fid="15"&gt;103032696&lt;/field&gt;&lt;field fid="28"&gt;03-16-2024&lt;/field&gt;&lt;field fid="9"&gt;70050&lt;/field&gt;&lt;field fid="12"&gt;162191.45&lt;/field&gt;&lt;field fid="53"&gt;Trace3 &nbsp;LLC&lt;/field&gt;&lt;field fid="54"&gt;588&lt;/field&gt;&lt;field fid="55"&gt;Cisco Global Maintenance Support 3 years BL 1130&lt;/field&gt;&lt;field fid="256"&gt;640400&lt;/field&gt;&lt;field fid="21"&gt;654127&lt;/field&gt;&lt;field fid="152"&gt;SA&lt;/field&gt;&lt;field fid="188"&gt;2024-02-27&lt;/field&gt;&lt;field fid="6"&gt;&lt;/field&gt;&lt;field fid="158"&gt;fake.name2@fakecompany.com&lt;/field&gt;&lt;field fid="153"&gt;L1_OTHER&lt;/field&gt;&lt;field fid="154"&gt;L2_GIS&lt;/field&gt;&lt;field fid="155"&gt;L3_ENTPR_INFRASTRUCTURE&lt;/field&gt;&lt;field fid="156"&gt;L4_CORP_FUNCTIONS&lt;/field&gt;&lt;field fid="48"&gt;fakename@fakecompany.com&lt;/field&gt;&lt;field fid="49"&gt;Fake Name&lt;/field&gt;&lt;field fid='8' filename=""&gt;&lt;/field&gt;&lt;field fid='60' filename=""&gt;&lt;/field&gt;&lt;/qdbapi&gt;
Thanks
Deepa------------------------------Deepa Prashant------------------------------

chayceduncan · Answer

Is this an example of the actual payload that is failing?
Did anything change with the structure or did you add any new fields recently? Your file fields are mixing ' and " in the same input which probably isn't the issue but stood out.&nbsp;------------------------------Chayce Duncan------------------------------

deepaprashant · Answer

Hi Chayce,
I am using a software called Alteryx to parse my data and pull out of SAP to figure which line items need to be added to my Quickbase app. That software needs me to use the inverted commas in that fashion to make it work.&nbsp;
I have not added any new fields...as you can see all the fields I am trying to add data to in the QB app, have an FID#. This morning, the API_Add call went through properly and added a record in QB. But just this one from Feb 27th (entry date) did not make it through.
Would like to depend upon the API calls to create the records and not miss any. Hence, want to understand why this line failed to load into QB and yes....that is the actual payload that is failing...just x'ed out the names and emails and user token.
Thanks!------------------------------Deepa Prashant------------------------------

deepaprashant · Answer

It appears I forgot to mention the exact error I get.
Here it is...

&lt;?xml version="1.0" ?&gt;

&lt;qdbapi&gt;

&lt;action&gt;API_AddRecord&lt;/action&gt;

&lt;errcode&gt;11&lt;/errcode&gt;

&lt;errtext&gt;Could not parse XML input&lt;/errtext&gt;

&lt;errdetail&gt;XML Parsing Error. unclosed token at line 1 column 907 (which is byte 908)&lt;/errdetail&gt;

&lt;/qdbapi&gt;

So I tried to find the 907th byte...and that is the very last part of the payload. 907+ remaining bytes shown below.

&gt;&lt;/qdbapi&gt;

So confused.------------------------------Deepa Prashant------------------------------

chayceduncan · Answer

In the data you've omitted, do you have any special characters like &amp; or &lt; in any of the inputs? If it worked prior, then with no changes to the API call it sounds like there is something in the actual data that is being interpreted in the XML and corrupting the payload. For example having &amp; typically has to be escaped as &amp;amp; - do you have any occurrence of invalid characters anywhere in the example that is failing?&nbsp;------------------------------Chayce Duncan------------------------------

deepaprashant · Answer

Hi Chayce,
I've checked and do not have any such characters. In my original post above, I've actually inserted the actual XML string (only x'ed out the usertoken and any emails and names). Typically for such errors, I see XML parsing failed.&nbsp;
This error reads Unclosed token...that is a new one for me.
Thanks!------------------------------Deepa Prashant------------------------------

<?xml version="1.0" ?>
<qdbapi>
	<action>API_AddRecord</action>
	<errcode>11</errcode>
	<errtext>Could not parse XML input</errtext>
	<errdetail>XML Parsing Error. unclosed token at line 1 column 907 (which is byte 908)</errdetail>
</qdbapi>

Forum Discussion

API errcode 11 XML Parsing Error. unclosed token

6 Replies

Related Content

Could not parse XML input. XML Parsing Error. unclosed CDATA section at line 9605 column 81

Parse data

How can I add my JavaScript app as a CodePage when it uses npm, Restfull API, fetch API, and complex JSON parsing?

Parse JSON field value in Pipelines based on another field value from the object

Pipelines bug: JSON value not being parse when specifying the JSON records path

Recent Discussions

What is the matter with my API Button formula?

Reports & Charts - Managing Client-Specific Name Visibility

When the Expiration Date is On or Before Today, Change the Contract Status to Expired

Share your feedback on the new Qrew Discussions

File Attachment Field in Pipelines