Jobs

Remove strings from job

Changed on

Remove strings from a job. Any strings removed from the job will also be unauthorized within Smartling.

If strings are successfully removed from a job, a 200 status will be returned. When the system can't quickly add the strings to the job, a 202 response is returned. The response contains a link to check the progress of the request. When a 202 is received, the process of removing the content from the job will not be complete until the returned process has completed.

post/jobs-api/v3/projects/{projectId}/jobs/{translationJobUid}/strings/remove

Request

  • Base URL
    https://api.smartling.com
  • Auth
    HTTP bearer

Path parameters

projectIdstring required

Unique identifier of a Smartling project — 9 lowercase alphanumeric characters.

Example:84c012a33

A unique project identifier. This can be found in the Smartling Dashboard under Account Settings > API.

translationJobUidstring required

Translation job unique identifier — 12 lowercase alphanumeric characters.

Example:j45v1uvsi3tx

Request body

hashcodesHashcode[]

The hashcodes (string identifiers) that should be removed from the job.

localeIdsLocaleId[]

(Optional) The array of localeIds that the strings should be removed from. If not specified, the strings will be removed from all locales within that job.

Example request

{
  "hashcodes": [
    "d41d8cd98f00b204e9800998ecf8427e"
  ],
  "localeIds": [
    "fr-FR"
  ]
}

Response

OK

Changes

    • breaking

      added the pattern ^[a-z0-9]{12}$ to the path request parameter translationJobUid

    • breaking

      added the pattern ^[a-z0-9]{9}$ to the path request parameter projectId

    • breaking

      added the pattern ^[a-f0-9]{32}$ to the request property /

    • breaking

      added the pattern ^[a-z]{2}(-[A-Z]{2})?$ to the request property /

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • breaking

      the response property /// became nullable for the status

    • info

      the // response's property pattern ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$ was added for the status

    • breaking

      the /// response's property type changed from string to integer for status

    • breaking

      the /// response's property type changed from string to integer for status