[
{
"value": 200
}
]
curl --location --request POST 'https://zylalabs.com/api/13845/structured+data+validator+api/31835/validate+json-ld+document' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[
{
"types": [
{
"type": "Article",
"properties": {
"headline": "string",
"author": "object"
}
},
{
"type": "Pers",
"properties": []
}
]
}
]
curl --location --request GET 'https://zylalabs.com/api/13845/structured+data+validator+api/31836/get+schema.org+types' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
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 Structured Data Validator 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.
(Save 2 months with annual billing 🎉)
The POST endpoint returns a validation report for submitted JSON-LD documents, detailing compliance with schema.org standards. The GET endpoint returns a structured list of schema.org types, including their properties and relationships, serving as a reference for developers.
The POST endpoint returns a validation report for submitted JSON-LD documents, detailing compliance with schema.org standards. The GET endpoint returns a structured list of schema.org types, including their properties and relationships, useful for implementing structured data.
For the POST endpoint, key fields include validation status and error details. For the GET endpoint, key fields include "type" (the schema type) and "properties" (the attributes associated with that type).
The POST endpoint response includes fields indicating validation status and errors, while the GET endpoint response includes fields for "type" and "properties" of schema.org types, providing essential information for structured data implementation.
The POST endpoint returns a JSON object with validation results, while the GET endpoint returns a JSON array of schema types, each containing a "type" and its associated "properties" in a structured format.
The POST endpoint organizes its response as an array of validation results, each detailing specific issues found in the JSON-LD document. The GET endpoint organizes its response as an array of schema types, each containing a "type" and its associated "properties."
The POST endpoint provides information on validation errors for JSON-LD documents, such as missing properties or incorrect formats. The GET endpoint offers a comprehensive list of schema.org types, including their properties and relationships for structured data.
The POST endpoint provides validation results for JSON-LD documents, identifying issues like missing properties. The GET endpoint offers a comprehensive list of schema.org types, including their properties and relationships for structured data implementation.
Typical use cases include validating structured data for SEO optimization, ensuring compliance with schema.org standards, and referencing schema types to enhance content visibility in search engines.
Users can customize their requests to the POST endpoint by submitting different JSON-LD documents for validation. For the GET endpoint, users can specify queries to retrieve specific schema.org types or properties based on their structured data needs.
Users can customize requests to the POST endpoint by submitting different JSON-LD documents for validation. The GET endpoint does not require parameters, as it returns all available schema types.
Data accuracy is maintained by adhering to the latest schema.org standards and performing comprehensive checks on JSON-LD documents. The API identifies issues by path, ensuring that users can rectify errors effectively.
Data accuracy is maintained through adherence to schema.org standards and comprehensive validation checks performed by the API, ensuring that the structured data meets required formats and properties.
Users can expect standard data patterns such as required properties for schema types, correct data formats for dates and currencies, and nested entities. The API's validation checks help ensure these patterns are followed in submitted JSON-LD documents.
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