Confirm Terms and Continue Translation

Manually kick off the translation phase — only applicable when the task was created with auto_apply_terms=false and TB_SCAN has already completed. Equivalent to the "Confirm & Continue" button in the console.

When to call

Integration flow (auto_apply_terms=false):

1. POST /tasks/create with auto_apply_terms: false → returns task_id immediately
2. Backend runs TB_SCAN; on completion you receive term_scan.completed with detail.requires_confirmation=true
3. Call GET /tasks/terms to list scanned terms (each carries an id)
4. Review — edit via /tasks/terms/update, remove via /tasks/terms/delete
5. Call this endpoint → TRANSLATE workflow starts; resume normal tmMatching / ... / task.completed callbacks

Endpoint

POST {BASE_URL}/api/open/v1/tasks/confirm-terms

Authentication Headers

Identical to Create Translation Task.

Body

Param	Type	Required	Description
task_id	string	Yes	Target task ID

Response

Success (HTTP 200):

{
  "success": true,
  "code": 0,
  "msg": "ok",
  "trace_id": "...",
  "data": {
    "task_id": "68a12cb7e1f9a88b4ea23c77",
    "job_id": "translate_open_...",
    "execution_id": "projects/.../executions/..."
  }
}

Error Codes

code	Description
400	Missing task_id
401	Signature invalid
403	Task does not belong to this App Key
404	Task not found
409	Task is not in the "waiting for confirmation" state (possibly auto_apply_terms was not false at creation, TB_SCAN is still running, or TRANSLATE was already triggered)
502	Workflow trigger failed
500	Internal error

Example

APP_KEY="5685414646a54423c891d87194d87f3f"
APP_SECRET="<your App Secret>"
TASK_ID="68a12cb7e1f9a88b4ea23c77"
BASE_URL="https://api.loxily.com"

TIMESTAMP=$(date +%s)
BODY="{\"task_id\":\"${TASK_ID}\"}"
SIGN=$(printf '%s' "${TIMESTAMP}${BODY}${APP_SECRET}" | md5)

curl -s -X POST "${BASE_URL}/api/open/v1/tasks/confirm-terms" \
  -H "Content-Type: application/json" \
  -H "X-Loxily-AppKey: ${APP_KEY}" \
  -H "X-Loxily-Timestamp: ${TIMESTAMP}" \
  -H "X-Loxily-Sign: ${SIGN}" \
  --data "${BODY}"

Console Parity

The "Confirm & Continue" button in the Loxily console and this API trigger the same underlying action — whichever caller wins advances the task from waiting_confirmation into TRANSLATE; the other side will observe the state flip to "triggered".