Swagger UI
< Back to Translation Set API v2

Differences between Translation Set API v1 and v2

Feature V1 V2 Notes
Callback URL Declared per request Declared once for project (details below) If you edit and publish a value from WOVN.io dashboard (translate page, translations, glossary edit etc), a callback will be sent to your registered callback URL.
Normalize ✅ (See details) ❌
Unescape ✅ (See details) ❌
Format ❌ ✅ (See details)
return_only_requested_terms option
 ✅ (See details) ❌ (The callback contains only the modified terms)
Separate requests for managing sets and terms ❌ ✅ (See details) In V2, the translation set is auto-created if it doesn't exist
Max terms per page N/A 10,000 This is customizable at the project level by admin
Max terms per project N/A 1,000,000 This is customizable at the project level by admin
Value "status" field ✅ ❌ The value status, it can be "in_progress", "translated" or "error"
User supplied translation ❌ ✅ Create or update the translations via the API

Callback URL:

  • V1:
    • callback_url is declared per request with the key callback_url, example: 
                                
{
  "project_token": "MC4NRc",
  "callback_url": "https://webhook.site/3c3ff904-4d78-4ace-9c63-f267281d0189",
  "translation_sets": []
}
  • V2:
    • Instead of sending the callback_url in the request the callback_url is set in project settings on every terms update a callback will be sent for that URL.
    • Note: You can setup the callback URL and its credentials in your project settings: Security / Translation Set API Management