Each key inside a request requires a text key with the content to translate.

The source language of the content in the order. Should contain a two-letter ISO 639-1 language code

The target language to which the content should be translated. Should contain a two-letter ISO 639-1 language code.

"machine", "postediting","translation", "localization", or "expert". The quality level in which the request will be translated.

In options (see example). The content of this url will be shown to translators to let them know the context in which the sentences will be used. Please don't provide generic landing pages that are not contextually relevant to the translation. If you do not have a context url, you can can leave it empty.

In options (see example). Max 255 characters. A name so it can be identified easily in the clients application UI.

In options (see example). These instructions will be shown to translators in addition to the style guide.

In options (see example). Max 255 characters. Immediately after the translation request is reviewed and accepted we will call this url. It will contain the same payload as the one in the GET request.

In options (see example). The email of one of your editors. If present, the request will be assigned to that editor.

In options (see example). By default, keys that contain tags will be parsed as html. If none of your content is html, setting this to true will prevent parse errors.

In options (see example). Preferred date for translation to be completed. Only used for prioritizing translation requests of the same client. Date format iso 8601

In options (see example). Code used by client to organize requests