엔진을 찾을 수 없음

API는 이 오류가 발생하면 404 Not Found 응답을 반환합니다. type 값은 https://lingo.dev/docs/api/errors/engine-not-found입니다. 모든 오류의 공통 구조는 오류 및 상태 코드를 참고하세요.

<id> 엔진을 찾을 수 없음

필드#

응답 본문에는 표준 멤버인 type, status, title, detail 외에 다음 필드가 포함됩니다. detail 텍스트는 이 필드를 바탕으로 생성되므로, 클라이언트에서 원하는 문구로 바꿔 표시할 수 있습니다.

예시#

{
  "detail": "Engine <id> not found",
  "id": "<id>",
  "type": "https://lingo.dev/docs/api/errors/engine-not-found",
  "status": 404,
  "title": "Engine not found"
}

이 오류를 반환하는 엔드포인트#

• DELETE /v2/engines/{engineId}/predefined-rules/{id}
• DELETE /v2/engines/{id}
• DELETE /v2/engines/{id}/brand-voices/{brandVoiceId}
• DELETE /v2/engines/{id}/glossaries/{glossaryId}
• DELETE /v2/engines/{id}/rulesets/{rulesetId}
• GET /v2/engines/{engineId}/glossary-terms
• GET /v2/engines/{engineId}/model-configs
• GET /v2/engines/{engineId}/predefined-rules
• GET /v2/engines/{id}
• GET /v2/engines/{id}/brand-voices
• GET /v2/engines/{id}/recent-directories
• GET /v2/engines/{id}/rulesets
• PATCH /v2/engines/{id}
• POST /v2/engines/{engineId}/engine-suggestions/from-text
• POST /v2/engines/{engineId}/engine-suggestions/generate
• POST /v2/engines/{engineId}/glossary-terms/extract-from-vtt
• POST /v2/engines/{engineId}/model-configs
• POST /v2/engines/{engineId}/provisioning/jobs
• POST /v2/organizations/{orgId}/localization/estimates
• POST /v2/organizations/{orgId}/localization/jobs
• POST /v2/organizations/{orgId}/service-api-keys
• POST /v2/provisioning/jobs/{id}/retry
• PUT /v2/engines/{engineId}/model-configs/order
• PUT /v2/engines/{engineId}/predefined-rules/{id}
• PUT /v2/engines/{id}/glossaries/{glossaryId}
• PUT /v2/engines/{id}/rulesets/{rulesetId}
• PUT /v2/service-api-keys/{id}/engines