Skip to main content
Versions

Get a Skill Version

Forward API reference.

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

HeaderRequiredDescription
AuthorizationYesBearer <PAT or SAT>

Path parameters

ParameterTypeRequiredDescription
idstringYesSkill ID.
versionstringYesVersion 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.

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

HTTPTypeTrigger
400invalid_request_errorThe version format is invalid, such as latest or a nonnumeric string.
401authentication_errorThe authentication token is missing or invalid.
403permission_errorThe caller cannot access the Skill.
404not_found_errorThe Skill or version does not exist.
500/502/503api_errorForward or a dependent service failed.