<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with json]]></title><description><![CDATA[A list of topics that have been tagged with json]]></description><link>https://fusionauth.io/community/forum/tags/json</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Jul 2026 03:41:56 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/json.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Receiving &#96;[invalidJSON]&#96; error when making FusionAuth API calls]]></title><description><![CDATA[<p dir="auto">HTTP clients, not just Axios, may impose their own requirements for building a valid request or have their own quirks to deal with.</p>
<p dir="auto">In this case the error can be resolved by providing a Content-Length header with the length of the JSON request data when making the API request via Axios.</p>
<p dir="auto">If you experience issues with a particular HTTP client, it may be helpful to compare the behavior with another client or check whether there are HTTP headers that may be required by the client.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2333/receiving-invalidjson-error-when-making-fusionauth-api-calls</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2333/receiving-invalidjson-error-when-making-fusionauth-api-calls</guid><dc:creator><![CDATA[spencer]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Invalid JSON  error when trying to retrieve users using user API]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/20">@dan</a> Oops! thank you so much Dan, it worked as a charm. I was fooled into leaving this header in because I tried the exact same request setup using one of these free api endpoints instead of fusionauth api and it worked with the content-type included. Thanks again</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2120/invalid-json-error-when-trying-to-retrieve-users-using-user-api</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2120/invalid-json-error-when-trying-to-retrieve-users-using-user-api</guid><dc:creator><![CDATA[munkith.abid]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Changing the fusionauth logging format]]></title><description><![CDATA[<p dir="auto">Worth re-emphasizing that this voids any warranty you might have from FusionAuth, <a href="https://fusionauth.io/license" rel="nofollow ugc">per the license</a>, exhibit A section 5.1.</p>
<p dir="auto">You can't get support from FusionAuth if you modify the software.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/441/changing-the-fusionauth-logging-format</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/441/changing-the-fusionauth-logging-format</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>