Transifex lets you specify a webhook and get notified whenever a target language of a resource has fully been translated, reviewed, or proofread, as well as when translation fill-ups are done. This way, you can pull translations as soon as they are ready without constantly checking Transifex for updates.
Adding webhooks to a project
đNote: For webhooks to work, you'll need a web server to listen for the webhook calls and an application to react to those. The webhooks are triggered automatically in Transifex.
Webhooks can be added to any project in an Organization. To do this:
From the Dashboard, head to the project you want to set up webhooks for
Click on Settings. Only Project Maintainers and Organization Admins can access this menu
In the submenu, click on Webhooks
Click on Add webhook
In the popup, enter your webhook URL and secret key (the secret key is optional). Then choose whether you'd like to be notified about all events or only a specific one
The callback URL should listen for a POST request with the following variables:
project: The slug of the project this notification is for
resource: The slug of the resource this notification is for
language: The language code of the translation that was modified
translated: An integer representing the completion percentage of translations for the particular resource in the specific language. If a resource is fully reviewed or proofread in a particular language, a variable named reviewed or proofread, respectively, will be used instead of the translated one
event: A string that describes the webhook type, which you can use to filter webhooks. The possible values are:
translation_completed: When a target language of a resource is 100% translated, then the webhook will be triggered. The following data will be returned:
{
"project": "project_slug",
"translated": 100,
"resource": "resource_slug",
"event": "translation_completed",
"language": "lang_code"
}review_completed: When a target language of a resource is 100% reviewed, then the webhook will be triggered. The following data will be returned:
{
"resource": "resource_slug",
"language": "lang_code",
"reviewed": 100,
"project": "project_slug",
"is_final": true/false,
"event": "review_completed"
}Note
The parameter "is_final" is false if the second review step (proofread) has been enabled and only the first review step has been completed.
proofread_completed: When a target language of a resource is 100% proofread, then the webhook will be triggered. The following data will be returned:
{
"resource": "resource_slug",
"language": "lang_code",
"reviewed": 100,
"project": "project_slug",
"is_final": true/false,
"event": "review_completed"
}fillup_completed: When TM or MT fill-up tasks are completed.
{
"machine translation": 0,
"resource": "resource_slug",
"language": "lang_code",
"project": "project_slug",
"translated": 50,
"translation memory": 50,
"event": "fillup_completed"
}translations_updated: When a 100% translated resource has a translation updated (edited).
{
"project": "project_slug",
"translated": 100.0,
"resource": "resource_slug",
"event": "translation_completed_updated",
"language": "lang_code"
}task Tag created: When a set of strings is selected in the editor, and the âCreate Taskâ button is pressed, the webhook will be triggered. The following data will be returned:
{
"project": "project_slug",
"language": "lang_code",
"tag": "tag_name",
"url": "https://example.com/org_slug/project_slug/translate/lang_code/resource_slug?q=tags%3AtxtaskENqwertyuiop12",
"event": "task_tag_created"
}task Tag completed: When a set of strings for which a task has already been created is fully translated, the webhook will be triggered. The following data will be returned:
{
"project": "project_slug",
"language": "lang_code",
"tag": "tag_name",
"url": "",
"event": "task_tag_completed"
}
When you're done, click Save changes.
When the event(s) you specified happens, an update is fired via a POST request from Transifex to the provided URL. The body of the post will be a JSON payload of the variables mentioned above.
Headers
If you've defined a secret key, then each webhook will include two headers:
X-TX-Signature: This is the computed signature generated by Transifex. It's used to tell whether the request is valid or not.
User-Agent: Transifex itself.
Verifying a webhook
The latest version of the Transifex webhook provides an extensible way to notify third-party services of changes in the progress of a resource in Transifex.
To validate that the webhook is coming from Transifex, you must first set a shared secret with Transifex. This will be used to calculate the webhook signature. When the webhook is received, we then calculate the signature on our end and check if it matches the submitted signature.
To calculate the signature, you need to concatenate (one element per line) the following:
The method type, e.g. POST
The URL path where your webhook listener listens
The submission date (taken from the
Dateheader)The hash of the contents of the webhook calculated through md5
After that, the signature is extracted by encrypting the concatenated data with the SHA256 algorithm using the shared secret. Finally, we encode the calculated hash in Base64.
Here's a sample of the webhook content:
{
"project": <project slug>,
"translated": <completion percentage>,
"resource": <resource slug,
"event": "translation_completed" || âreview_completedâ || âproofread_completedâ || âfillup_completedâ,
"language": <language_code>
}
Below are a series of code samples that demonstrate the required validation procedure.
PHP
$http_verb = 'POST';
$received_json = file_get_contents("php://input", TRUE);
$webhook_sig = $_SERVER['X-TX-Signature-V2'];
$http_url_path = $_SERVER['X-TX-Url'];
$http_gmt_date = $_SERVER['Date'];
$content_md5 = md5($received_json);
$msg = join(PHP_EOL, array('POST', $http_url_path, $http_gmt_date, $content_md5));
$sig = base64_encode(hash_hmac('sha256', $msg, TRANSIFEX_SECRET, true));
return $sig == $webhook_sig
Node
const sign_v2 = (url, date, data, secret) => {
const content_md5 = md5(data);
const msg = ['POST', url, date, content_md5].join('\n');
const hmac = crypto.createHmac('sha256', secret);
return hmac.update(msg).digest().toString('base64');
};
Python
import base64
import hmac
import hashlib
# Both http_gmt_date and http_url_path can be found through the response headers namely in the HTTP_DATE and HTTP_X_TX_URL headers respectively
http_verb = 'POST'
http_url_path = 'http://www.test.com/page/'
http_gmt_date = 'Wed, 08 Feb 2017 09:49:18 GMT'
secret = 'secret_key'
response_payload = '{"project": "project-slug", "translated": 100.0, "resource": "resource-slug", "event": "translation_completed", "language": "de"}'
content_md5 = hashlib.md5(response_payload).hexdigest()
msg = b'\n'.join([
http_verb, http_url_path, http_gmt_date, content_md5
])
tx_signature = base64.b64encode(
hmac.new(
key=secret,
msg=msg,
digestmod=hashlib.sha256
).digest()
)
Ruby
require 'openssl'
require 'base64'
HMAC_DIGEST_256 = OpenSSL::Digest.new('sha256')
http_verb = 'POST'
http_date = 'Fri, 17 Feb 2017 08:24:07 GMT'
url = 'https://app.transifex.com/'
secret = 'some secret'
content = '{"project": "project-slug", "translated": 100, "resource": "resource-slug", "event": "translation_completed", "language": "de"}'
content_md5 = Digest::MD5.hexdigest content
data = [http_verb, url, date, content_md5].join("\n")
Base64.encode64(
OpenSSL::HMAC.digest(HMAC_DIGEST_256, secret, data)
).strip