{
"note": {
"to": "Ana",
"@id": "1"
}
}
curl --location --request POST 'https://zylalabs.com/api/14222/xml+yaml+and+json+converter+api/35299/xml+to+json' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw 'Ana '
<?xml version="1.0" encoding="UTF-8"?>
<note>
<to>Ana</to>
</note>
curl --location --request POST 'https://zylalabs.com/api/14222/xml+yaml+and+json+converter+api/35300/json+to+xml' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"note":{"to":"Ana"}}'
{
"name": "Ana",
"tags": [
"a",
"b"
]
}
curl --location --request POST 'https://zylalabs.com/api/14222/xml+yaml+and+json+converter+api/35301/yaml+to+json' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw 'name: Ana
tags: [a, b]'
name: Ana
tags:
- a
- b
curl --location --request POST 'https://zylalabs.com/api/14222/xml+yaml+and+json+converter+api/35302/json+to+yaml' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"name":"Ana","tags":["a","b"]}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the XML YAML and JSON Converter API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Convert XML to JSON (attributes kept), JSON to XML, YAML to JSON and JSON to YAML. Send the document, get the converted result.
Each endpoint returns converted data in a specific format: XML to JSON returns a JSON object, JSON to XML returns an XML document, YAML to JSON returns a JSON object, and JSON to YAML returns a YAML document. For example, the XML to JSON endpoint returns attributes prefixed with "@".
The key fields vary by format. For JSON responses, fields are typically key-value pairs, such as "to" and "@id" in the XML to JSON response. In XML responses, elements like `<to>` are used. YAML responses use indentation to represent structure.
The returned data format depends on the endpoint: JSON responses are structured as key-value pairs, XML responses are hierarchical with tags, and YAML responses use indentation for structure. Each format maintains the original data's integrity.
Each endpoint allows conversion of structured data: XML to JSON retains attributes, JSON to XML converts objects to tags, YAML to JSON translates YAML structures into JSON format, and JSON to YAML reformats JSON into a human-readable YAML structure.
Response data is organized based on the format: JSON responses are in key-value pairs, XML responses are in nested tags, and YAML responses use indentation. This organization helps users easily parse and utilize the data in their applications.
Typical use cases include data interchange between systems, converting configuration files, and transforming data for APIs. For example, converting XML data from a legacy system to JSON for modern applications or vice versa for compatibility.
Users can customize requests by sending specific XML, JSON, or YAML documents to the respective endpoints. The API processes the provided document and returns the converted result, allowing flexibility in data formats based on user needs.
Data accuracy is maintained through consistent conversion algorithms that ensure the integrity of the original data is preserved across formats. The API is designed to handle standard data structures, minimizing errors during conversion.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund