Glossary not found · Lingo.dev

The API answers 404 Not Found with this problem. Its type is https://lingo.dev/docs/api/errors/glossary-not-found. See Errors and status codes for the shape every error shares.

Glossary <id> not found

Fields#

Besides the standard type, status, title and detail members, the body carries these fields. The detail text is built from them, so a client can show its own text instead.

Field	Type
`id`	`string`

Example#

json

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

Returned by#

DELETE /v2/glossaries/{id}
GET /v2/glossaries/{glossaryId}/terms
GET /v2/glossaries/{id}
PATCH /v2/glossaries/{id}
POST /v2/engines/{engineId}/glossary-terms/extract-from-vtt
POST /v2/glossaries/{glossaryId}/terms
POST /v2/glossaries/{glossaryId}/terms/create-many
POST /v2/glossaries/{glossaryId}/terms/delete-many
POST /v2/glossaries/{glossaryId}/terms/update-many
PUT /v2/service-api-keys/{id}/content-scope