Localization QA API API ID: 12798

Checks translated JSON, localization strings, placeholders, ICU messages, missing keys, extra keys, empty values, untranslated values, and multi-locale consistency.
Use this API from your AI agent via MCP
Works with OpenClaw, Claude Code/Desktop, Cursor, Windsurf, Cline and any MCP-compatible AI client.
Docs & setup
Create a skill by wrapping this MCP: https://mcp.zylalabs.com/mcp?apikey=YOUR_ZYLA_API_KEY

Localization QA API checks translated JSON and localization strings for common localization QA issues.

The API handles localization QA data including missing keys, extra keys, empty values, untranslated values, placeholder mismatches, missing placeholders, extra placeholders, ICU message syntax, ICU variable consistency, plural message structure, locale-specific QA results, multi-locale comparison, usage status, safety notes, and disclaimer.

The API returns QA issue lists, issue type, message key, source value, target value, locale, missing keys, extra keys, empty values, untranslated values, placeholder issues, ICU issues, comparison results by locale, and warnings.

This API is useful for developers, SaaS builders, localization teams, translation workflow platforms, i18n services, product teams, frontend teams, backend teams, QA teams, agencies building multilingual apps, ecommerce platforms, support platforms, CRM services, HR platforms, fintech services, legaltech platforms, edtech platforms, healthtech platforms, B2B software companies, and internal tooling teams.

The API checks localization JSON, placeholders, ICU syntax, and locale comparison results from submitted request data. It does not hack, brute force, attempt logins, scan private systems, scrape restricted content, change customer data, send emails, create calendar events, approve or reject translations, guarantee translation quality, guarantee legal compliance, replace human translation review, or replace professional localization review.

The API response includes a data_disclaimer field explaining that the QA result is based only on submitted localization JSON, placeholder, ICU message, and locale comparison data and is provided for technical review purposes. Results should be reviewed before use in localization, QA, legal, compliance, operational, or business decisions.

API Documentation

Endpoints


Checks source and translated localization JSON for missing keys, extra keys, empty values, untranslated values, placeholder issues, ICU issues, locale-specific QA results, warnings, and status information.



                                                                            
POST https://api-nrl-rugby-data.zylalabs.com/api/12798/localization+qa+api/25151/localization+qa+check
                                                                            
                                                                        

Localization QA Check - Endpoint Features

Object Description
Request Body [Required] Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS


API EXAMPLE RESPONSE

{"ok":true,"score":100,"grade":"A","summary":{"total_keys":2,"issue_count":0,"error_count":0,"warning_count":0,"info_count":0},"issues":[],"warnings":[]}

Localization QA Check - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/12798/localization+qa+api/25151/localization+qa+check' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{
  "source": {
    "hello": "Hello {name}",
    "cart": "{count, plural, one {# item} other {# items}}"
  },
  "target": {
    "hello": "Bonjour {name}",
    "cart": "{count, plural, one {# article} other {# articles}}"
  },
  "locale": "fr-CH"
}'

    

Compares multiple target locale JSON files against a base locale to find missing keys, extra keys, empty values, untranslated values, placeholder mismatches, ICU issues, per-locale results, and warnings.



                                                                            
POST https://api-nrl-rugby-data.zylalabs.com/api/12798/localization+qa+api/25152/compare+locales
                                                                            
                                                                        

Compare Locales - Endpoint Features

Object Description
Request Body [Required] Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS


API EXAMPLE RESPONSE

{"ok":false,"locales":[{"locale":"fr-CH","ok":false,"summary":{"base_key_count":2,"target_key_count":1,"missing_key_count":1,"extra_key_count":0},"missing_keys":["cart.items"],"extra_keys":[],"issues":[{"severity":"error","locale":"fr-CH","key":"cart.items","source_value":"{count} items","message":"Missing target key.","fix_hint":"Add this key to the target locale."}]},{"locale":"de-CH","ok":true,"summary":{"base_key_count":2,"target_key_count":3,"missing_key_count":0,"extra_key_count":1},"missing_keys":[],"extra_keys":["extra.key"],"issues":[{"severity":"info","locale":"de-CH","key":"extra.key","target_value":"Extra","message":"Extra target key.","fix_hint":"Remove this key if it is not used by the app."}]}],"summary":{"locale_count":2,"total_missing_keys":1,"total_extra_keys":1,"total_issues":2}}

Compare Locales - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/12798/localization+qa+api/25152/compare+locales' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{
	"base": {
		"hello": "Hello",
		"cart.items": "{count} items"
	},
	"targets": {
		"fr-CH": {
			"hello": "Bonjour"
		},
		"de-CH": {
			"hello": "Hallo",
			"cart.items": "{count} Artikel",
			"extra.key": "Extra"
		}
	}
}'

    

Checks source and target localization strings for placeholder mismatches, missing placeholders, extra placeholders, dynamic variable consistency, issue details, locale information, and warnings.



                                                                            
POST https://api-nrl-rugby-data.zylalabs.com/api/12798/localization+qa+api/25179/check+placeholders
                                                                            
                                                                        

Check Placeholders - Endpoint Features

Object Description
Request Body [Required] Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS


API EXAMPLE RESPONSE

{"ok":false,"source_placeholders":["{count}"],"target_placeholders":[],"missing":["{count}"],"extra":[]}

Check Placeholders - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/12798/localization+qa+api/25179/check+placeholders' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{
	"source_value": "You have {count} items",
	"target_value": "Vous avez des articles",
	"locale": "fr-CH"
}'

    

Checks ICU message syntax, ICU variable consistency, plural message structure, locale-specific ICU issues, issue details, warnings, and status information.



                                                                            
POST https://api-nrl-rugby-data.zylalabs.com/api/12798/localization+qa+api/25182/check+icu+messages
                                                                            
                                                                        

Check ICU Messages - Endpoint Features

Object Description
Request Body [Required] Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS


API EXAMPLE RESPONSE

{"ok":true,"source_valid":true,"target_valid":true,"source_variables":["count"],"target_variables":["count"],"missing_variables":[],"extra_variables":[],"errors":[]}

Check ICU Messages - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/12798/localization+qa+api/25182/check+icu+messages' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{
	"source_value": "{count, plural, one {# item} other {# items}}",
	"target_value": "{count, plural, one {# article} other {# articles}}",
	"locale": "fr-CH"
}'

    

API Access Key & Authentication

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 Localization QA API simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Localization QA API FAQs

Each endpoint returns structured JSON data for localization QA checks. The Localization QA Check endpoint returns summary counts, issue details, warnings, and status. The Compare Locales endpoint returns per-locale comparisons, missing keys, extra keys, issue details, and totals.

Key fields include "ok" (status), "score" (quality score), "grade" (evaluation grade), "summary" (overview of issues), and "issues" (detailed problems). For instance, "issues" may list missing keys or extra keys with severity levels.

Parameters vary by endpoint but generally include source and target JSON data, locale values, and optional settings for detailed checks. For example, the Check Placeholders endpoint uses source and target strings to compare placeholder consistency.

Response data is organized into a main object containing status indicators, summaries, and issue lists. For example, the Compare Locales endpoint groups results by locale, provides a summary for each locale, and lists specific issues found.

Each endpoint provides localization QA information such as missing keys, extra keys, empty values, untranslated values, placeholder mismatches, ICU message syntax issues, variable consistency checks, locale results, issue details, warnings, and status information.

Data accuracy is maintained through systematic checks for localization issues, including validation of JSON structure and ICU syntax. The API does not guarantee translation quality but identifies potential errors for review.

Typical use cases include validating localization for software applications, ensuring consistency across multiple languages, and identifying issues in translation workflows. Teams can use the API to streamline QA processes in multilingual projects.

Users can review the returned issue list, severity values, affected keys, locales, source values, target values, placeholder details, ICU details, and warnings to identify localization items that may need review.

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

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.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

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.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs