XML to JSON API

POST

Parse any raw XML payload into structured JSON.

XML to JSON converts raw XML strings into structured JSON objects. Send any valid XML payload to receive an organized JSON tree preserving tags, attributes, and child elements.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/xmltojson

Body

xmlstring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "note": {
      "children": [
        {
          "to": {
            "content": "Tove"
          }
        },
        {
          "from": {
            "content": "Jani"
          }
        },
        {
          "heading": {
            "content": "Reminder"
          }
        },
        {
          "body": {
            "content": "Don't forget me this weekend!"
          }
        }
      ]
    }
  }
}

About the XML to JSON API

XML to JSON works by analyzing the XML content provided and converting it to JSON. It uses advanced algorithms to convert the XML content to JSON and returns the JSON representation of the XML.

What people use it for

Legacy SOAP Integration: When ingesting legacy SOAP web service responses, modern frontend microservices parse the returned XML body into JSON before processing client requests.
RSS Feed Ingestion: News aggregators translate incoming XML syndication feeds into standard JSON records to index articles directly into document databases.
Supply Chain Invoices: To process electronic data interchange documents, logistics platforms convert supplier XML invoices into JSON payloads for internal billing services.
Webhook Payload Normalization: Convert XML notifications from payment gateways and partner APIs into JSON before passing event payloads to serverless event brokers.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use XML to JSON

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets

Questions.

Common questions about the XML to JSON API.

Read the docs →

How many XML conversions does the Free plan cover?

The Free plan covers 100 conversions each month at 2 credits per request. If you need higher volume, the Starter plan supports 100,000 conversions per month, which works out to about $0.30 per 1,000 conversions.

Can I submit raw XML strings directly in the request?

Yes. You send the XML content as a string parameter in a POST request. The XML to JSON API processes the string directly without requiring multipart file uploads.

How are nested child tags structured in the returned JSON?

Child elements are organized into an array under the root object. Each entry retains the element tag and its text content, preserving the structural hierarchy of your source document.

Will this handle third-party SOAP responses and RSS feeds?

Yes, as long as you pass the payload as an XML string. The converter parses the document hierarchy regardless of whether the source is a syndication feed, SOAP response, or custom export.

Does the returned JSON require additional cleanup before use?

No. The response returns valid JSON ready to be parsed by standard JSON libraries in your programming language.

Request parameters — POST /v1/xmltojson

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`xml`Required	string	`<?xml version="1.0"?><root><item>value</item></root>`	The XML content to convert to JSON

Example request

curl -X POST "https://api.apiverve.com/v1/xmltojson" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"xml":"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<note>\n  <to>Tove</to>\n  <from>Jani</from>\n  <heading>Reminder</heading>\n  <body>Don'\''t forget me this weekend!</body>\n</note>"}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — POST /v1/xmltojson

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "note": {
      "children": [
        {
          "to": {
            "content": "Tove"
          }
        },
        {
          "from": {
            "content": "Jani"
          }
        },
        {
          "heading": {
            "content": "Reminder"
          }
        },
        {
          "body": {
            "content": "Don't forget me this weekend!"
          }
        }
      ]
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`note`	object	`{...}`	Root element converted from XML structure
`children`	array[4]		Array of child elements from parsed XML content
`to`	object	`{...}`
`content`	string	`"Tove"`	Recipient field value from XML element

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	XML to JSON calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — POST /v1/xmltojson

No SDK to install — this is a plain HTTPS call to /v1/xmltojson with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/xmltojson" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/xmltojson-apiSource, issues and the examples this page is built from.ReferenceXML to JSON API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/xmltojsonnpm APIVerve.API.XMLtoJSONNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — POST /v1/xmltojson

Install the Node.js SDK, then call the XML to JSON API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/xmltojson

Node.js

const res = await fetch("https://api.apiverve.com/v1/xmltojson", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/xmltojsonThe published Node.js client, versioned and signed.GitHubapiverve/xmltojson-apiSource, issues and the examples this page is built from.ReferenceXML to JSON API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.XMLtoJSONNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/xmltojson

No SDK to install — this is a plain HTTPS call to /v1/xmltojson with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/xmltojson",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/xmltojsonnpm APIVerve.API.XMLtoJSONNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — POST /v1/xmltojson

Install the C# / .NET SDK, then call the XML to JSON API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.XMLtoJSON

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/xmltojson");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.XMLtoJSONThe published C# / .NET client, versioned and signed.GitHubapiverve/xmltojson-apiSource, issues and the examples this page is built from.ReferenceXML to JSON API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/xmltojsonnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/xmltojson

No SDK to install — this is a plain HTTPS call to /v1/xmltojson with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/xmltojson", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/xmltojsonnpm APIVerve.API.XMLtoJSONNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/xmltojson

No SDK to install — this is a plain HTTPS call to /v1/xmltojson with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/xmltojson");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/xmltojsonnpm APIVerve.API.XMLtoJSONNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/xmltojson

No SDK to install — this is a plain HTTPS call to /v1/xmltojson with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/xmltojson")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/xmltojsonnpm APIVerve.API.XMLtoJSONNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Data Conversion

View all 33 →

All articles →

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

Generate PDFs from HTML with an APIConvert HTML to PDF programmatically. Tutorial covering invoices, reports, receipts, and certificates with code examples.Read

Automating Visual Testing With ScreenshotsCatch visual bugs before users do. Here's how to add screenshot-based testing to your workflow.Read

XML to JSON API

Try it — live request, no key required

About the XML to JSON API

What people use it for

Ways to call it

Other ways to use XML to JSON

Questions.

Request parameters — POST /v1/xmltojson

Required

Authentication

Response — POST /v1/xmltojson

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/xmltojson

Resources

Also published for

Call it from Node.js — POST /v1/xmltojson

Resources

Also published for

Call it from Python — POST /v1/xmltojson

Resources

Also published for

Call it from C# / .NET — POST /v1/xmltojson

Resources

Also published for

Call it from Go — POST /v1/xmltojson

Resources

Also published for

Call it from PHP — POST /v1/xmltojson

Resources

Also published for

Call it from Ruby — POST /v1/xmltojson

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — XML to JSON API

Data Conversion

Related articles

Ready to build with XML to JSON? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog