# Accredible Skills Frameworks API

**Canonical:** https://apis.io/apis/accredible/accredible-skills-frameworks-api/  
**Provider:** Accredible — https://apis.io/providers/accredible/  
**Base URL:** https://api.accredible.com/v1  
**Documentation:** https://docs.api.accredible.com/

Accredible Skills Frameworks API is one of 14 APIs that [Accredible](https://apis.io/providers/accredible/) publishes on the [APIs.io](https://apis.io/) network, described by a machine-readable OpenAPI specification. Tagged areas include Skills Frameworks. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

A Skills Framework is a structured taxonomy of skills. Accredible maintains external frameworks such as O*NET, ESCO and NACE, and your organization can upload its own custom frameworks. Tagging a Group against a framework replaces the free-text `learning_outcomes` list with skills that carry a stable identifier and a known position in a recognized taxonomy. These endpoints are **read-only**. Uploading frameworks, editing their skills, publishing and retiring versions are all managed in the [Accredible Dashboard](https://dashboard.accredible.com/) — the API lets you discover the frameworks available to you, search their skills, and select those skills on a Group. ## Frameworks are versioned You always tag against a **version**, never a framework. Each framework in the list response carries a `versions` array; take the `id` of the version you want and send it as `skill_framework_version_id` when you create or update a Group. Only published versions (`active` and `retired`) are ever returned. The version's status decides what a write does. Tagging against the `active` version attaches your skills. Tagging against a `retired` version never fails the request — the Group is still created or updated, but the skills are ignored and the response is a `207` with a `version_retired` error. ## Skills know where they live A skill sits at a position in its framework's hierarchy, and in some taxonomies it legitimately sits in more than one. The skills search response returns one row per skill with a `breadcrumbs` array — one trail per placement, each trail listing the skill's ancestors from the root down to its immediate parent. When you attach a skill to a Group you send both the skill `id` and the `breadcrumb_ids` of the trail you mean, so the placement is unambiguous. The ids in a `breadcrumbs` trail are exactly what `breadcrumb_ids` expects — you can copy them straight from a search result into a Group request. Because the pair `(id, breadcrumb_ids)` identifies a placement, the same skill id may appear more than once with different trails. ## Reading skills back off a credential You do not need to call these endpoints to display a credential's skills. [Credential](#tag/Credentials) responses carry a `skills` array for the Group the credential was issued from, with each skill's external `identifier` and its `breadcrumbs` trail, so a consumer pulling credentials can render skills without a second request. The framework those skills belong to is a property of the Group, not of the credential, so it is not repeated on every credential. Follow the credential's `group_id` to [View a Group](#operation/View%20a%20Group) and read `skill_framework` — the Group response carries the same `skills` array alongside it. The array is empty when the Group uses free-text `learning_outcomes`, when it has a framework selected but no skills that can be tagged, and when the credential has no Group at all. ## Relationship to existing Group fields Framework skills and free-text `learning_outcomes` can both be set on a Group; neither is rejected or cleared by the other. Where a credential displays a single skills list, framework skills take precedence. `skill_category_id` is a separate, unrelated classification and is unaffected. ## Skills that cannot be attached return a 207, not a failed write When skills cannot be attached — because the version is retired, the framework is not available to the Department, a skill id is not in the version, or a breadcrumb trail is invalid — the Group write does not fail. The Group is still created or updated, every valid skill is attached, the rest are ignored, and each reason is itemized in the `errors` array of a `207 Multi-Status` response. Attachment is per-skill, so one invalid skill does not stop the others from attaching. Read `skill_framework` and `skills` off a `207` response to see exactly what was saved. There is one exception. If your plan does not include access to skills frameworks and you send framework parameters for a Group that is **already** framework-backed, [Update a Group](#operation/Update%20a%20Group) returns a hard `403` and nothing in the request is saved, including changes to unrelated fields. The Group's framework and skills stay saved and readable, and moving it to free-text skills with `"framework_skills": null` is still allowed. See [Skills Frameworks Error Handling](#section/Errors/Skills-Frameworks-Error-Handling) for the full list of codes.

## Operations (2)

| Method | Path | Summary |
|---|---|---|
| GET | `/v1/skill_frameworks` | View all Skill Frameworks |
| GET | `/v1/skill_frameworks/{skill_framework_id}/versions/{version_id}/skills` | Search Skills in a Framework Version |

## Machine-readable artifacts (5)

- **OpenAPI** — https://raw.githubusercontent.com/api-evangelist/accredible/refs/heads/main/openapi/accredible-skills-frameworks-api-openapi.yml
- **Documentation** — https://docs.api.accredible.com/
- **APIReference** — https://docs.api.accredible.com/
- **PostmanCollection** — https://raw.githubusercontent.com/api-evangelist/accredible/refs/heads/main/collections/accredible.postman_collection.json
- **OpenCollection** — https://raw.githubusercontent.com/api-evangelist/accredible/refs/heads/main/collections/accredible.opencollection.json

## Other Accredible APIs (12)

- [Accredible Analytics API](https://apis.io/apis/accredible/accredible-analytics-api/)
- [Accredible Credentials API](https://apis.io/apis/accredible/accredible-credentials-api/)
- [Accredible Departments API](https://apis.io/apis/accredible/accredible-departments-api/)
- [Accredible Designs API](https://apis.io/apis/accredible/accredible-designs-api/)
- [Accredible Evidence Items API](https://apis.io/apis/accredible/accredible-evidence-items-api/)
- [Accredible Groups API](https://apis.io/apis/accredible/accredible-groups-api/)
- [Accredible References API](https://apis.io/apis/accredible/accredible-references-api/)
- [Accredible SSO API](https://apis.io/apis/accredible/accredible-sso-api/)
- [Accredible Team Members API](https://apis.io/apis/accredible/accredible-team-members-api/)
- [Accredible Attributes API](https://apis.io/apis/accredible/accredible-attributes-api/)
- [Accredible Collections API](https://apis.io/apis/accredible/accredible-collections-api/)
- [Accredible Data Exports API](https://apis.io/apis/accredible/accredible-data-exports-api/)

## Tags

Skills Frameworks

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/accredible/accredible-skills-frameworks-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/accredible/.