Version 1.17.0
| Issue ID | Description |
|---|---|
| 410727 | The following methods have been updated to return messages with more information on the error:
|
| 423866 | The listener supports endpoint where the certificate uses AIA extension. |
Version 1.16.0
| Issue ID | Description |
|---|---|
| 343993 | Token requests can fail when a password contains certain special characters. This has been fixed. |
Version 1.15.0
| Issue ID | Description |
|---|---|
| 274462 | A new Job field, siteId, has been added. Intended for support case diagnostics. |
| 382004 | A new Job field, submittedTime, has been added. |
| 405247 | The s3Bucketname field on the SourceFile model is not part of the API specification. It has been removed. |
| 397697 | In some cases, errors from the translation provider do not get propagated into an error on the Content API request and statusupdate models. This has been fixed. |
| 399581 | The POST /oauth2/token method now returns an error on invalid authProvider values. |
Version 1.14.0
| Issue ID | Description |
|---|---|
| 345640 | A new property, requiredJobFields, has been added to a Provider's capabilities. It is a array of required job fields optionally set by the provider. If present, values listed in this property must be included on the job when submitting. |
| 274354 | Added optional paging support for these GET methods:
|
| 381588 | A size limit has been added to POST /jobs/{jobId}/requests/add. |
| 382245 | There is now a limit on string length on jobName (250), requestName(250) and fileName (100). |
| 396331 | There was an intermittent issue when multiple translation requests with the same source and target languages shared the same SourceFile, some of the request statuses were not updated. This issue has been resolved. |
Version 1.13.0
| Issue ID | Description |
|---|---|
| 383177 | In version 1.11.0 of the API, when multiple translation requests with the same source and target languages shared the same SourceFile, the status of only one request was updated. This issue has been resolved. |
Version 1.11.0
You can use the new GET/jobs/{jobId}/sourcefiles/{fileId}/retrieve method to retrieve source content.
| Issue ID | Description |
|---|---|
| 343736 | Previously, the job summary displayed REVIEW_TRANSLATION status when the items in the job had COMPLETED status. This issue has been resolved: When all items in a job have COMPLETED status, the job summary now also displays COMPLETED status. |
Version 1.10.0
The new optional providerReference field enables you to retrieve reference information from your translation provider. You can retrieve this reference information on the Job or Request objects returned from the API methods.
| Issue ID | Description |
|---|---|
| 274430 | Previously, the fetchType parameter in job-fetch endpoints did not function properly when the fullWithStats option was specified. This issue has been resolved.
The fetchType parameter now supports only the full option.
|
| 339313 | Previously, when there was a redelivery to a job with COMPLETED status, the job status did not change. This issue has been resolved. When there is a redelivery to a job with COMPLETED status, the job status now changes to REVIEW_TRANSLATION, which is the correct behavior. |
| 338385 | On rare occasions, the job submission was delayed by several hours. This issue has been resolved. |
Version 1.9.0
| Issue ID | Description |
|---|---|
| 274414 | Previously, submitting the DELETE /jobs/{jobId} method did not return a response. This issue has been resolved. This method now returns the 200 response code, indicating that the request was successfully processed. |
| 288818 | Previously, after submitting multiple unsupported target languages in a pair with a source language using the POST /jobs/{jobId}/requests/addfile method, the response returned the failure reason of only one unsupported language pair. This issue has been resolved. In this scenario, the response now returns the failure reason of all unsupported language pairs. |
| 289793 |
Previously, the following methods did not support the Try it out! feature on the API reference page:
This issue has been resolved. The methods listed above now support the Try it out! feature. |
| 292403 | Previously, when a listener created by the POST /statusupdates/listeners method was invoked on status updates, it did not accept response codes that indicated URL redirection. This issue has been resolved. A listener created by this method now accepts response codes that indicate URL redirection. |
| 292653 | The bottleneck in the PUT /jobs/{jobId}/submit method has been resolved. |
Version 1.8.1
| Issue ID | Description |
|---|---|
| 287524 | The Try it out! feature did not work for some of the methods on the API reference page. This issue has been resolved. |
| 287525 | Some methods returned response codes for successful calls that differed from the API specification. This issue has been resolved. |
Version 1.8.0
| Issue ID | Description |
|---|---|
| REST-483 | Previously, after sending a request with unexpected headers failed, the API reused input parameters from a previous request. This security vulnerability has been resolved. |
Version 1.7.0
GET jobs/{jobId}/requests/{requestId}/retrieve
method now returns only the latest TranslatedContent in a one-element array. Previously, this
method returned an array, where the latest TranslatedContent was at the start of the array, which was sorted by time.