Get a Skill Version

Description

Retrieves metadata for a single Skill version by version number, without content. Retrieve content with Download Skill Version Content.

Path

GET /api/v1/forward/skills/{id}/versions/{version}

Request headers

Header	Required	Description
`Authorization`	Yes	`Bearer <PAT or SAT>`

Path parameters

Parameter	Type	Required	Description
`id`	string	Yes	Skill ID.
`version`	string	Yes	Version number. • Recommended: A 16-digit Unix microsecond timestamp such as `1759178010641129`; • Compatibility: Legacy incremental counters such as `"1"` or `"2"` still resolve to the same version during migration. The literal `latest` is not supported and returns 400. Call Get a Skill, read `latest_version`, and use that value in the path.

Query parameters

Parameter	Type	Required	Description
`identity_id`	string	No	For Identity-owned resources only. PATs may supply this query parameter; omitting it uses the administrator scope. SAT ownership is determined by the credential; any SAT (including Admin SAT) explicitly supplying this parameter, even with an empty value, receives HTTP 400. Versions inherit ownership from their Skill. See Identity ownership.

Example request

curl -X GET "https://api.qoder.com/api/v1/forward/skills/skill_xxx/versions/1786973491821648" \
  -H "Authorization: Bearer $QODER_ACCESS_TOKEN"

Legacy number compatibility example:

curl -X GET "https://api.qoder.com/api/v1/forward/skills/skill_xxx/versions/2" \
  -H "Authorization: Bearer $QODER_ACCESS_TOKEN"

Example response

HTTP 200 OK

{
  "id": "skillver_xxx",
  "skill_id": "skill_xxx",
  "version": "1786973491821648",
  "name": "customer-reply",
  "description": "Customer reply skill",
  "directory": "customer-reply",
  "content_size": 2607,
  "content_sha256": "9de8ae3a296bc6198cd080f5ce31d523a34fd0a52e2e64365055fa79a0d3383d",
  "status": "active",
  "created_at": "2026-08-17T13:31:31.917881Z",
  "metadata": {}
}

Response fields

The response is a Skill version object. See Legacy version-number compatibility for compatibility rules.

Errors

HTTP	Type	Trigger
400	`invalid_request_error`	The version format is invalid, such as `latest` or a nonnumeric string, or any SAT explicitly supplies query `identity_id` (even with an empty value).
401	`authentication_error`	The authentication token is missing or invalid.
403	`permission_error`	An owner mismatch occurs in the administrator scope, or a downstream service denies access.
404	`not_found_error`	The Skill or version does not exist or is not visible in the current Identity scope; the Identity specified by the PAT is invalid, disabled, deleted, or outside the caller's ownership.
500/502/503	`api_error`	Forward or a dependent service failed.

​Description

​Path

​Request headers

​Path parameters

​Query parameters

​Example request

​Example response

​Response fields

​Errors