> ## Documentation Index
> Fetch the complete documentation index at: https://help.skillsdb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Careers

> The competency models a company defines — careers, the families they group under, and the single scale every grade points at

<Info>
  **Quick Summary:** A career is not a flat record — it is a complete competency model of levels, sections, skill groups, skills and learnings. This group is the model itself. Who *holds* a career is a [career assignment](/api-docs/resources/career-assignment) in [Team Data](/api-docs/concepts/team-data).
</Info>

## The resources

| Resource                                           | What it is                                                                 |
| -------------------------------------------------- | -------------------------------------------------------------------------- |
| [Career](/api-docs/resources/career)               | The competency model: levels, sections, skill groups, skills and learnings |
| [Career type](/api-docs/resources/career-type)     | The families careers are grouped under, such as *Job Role* and *Group*     |
| [Grading scale](/api-docs/resources/grading-scale) | The single company-wide scale every benchmark and grade references         |

## Read the whole model in one call

The career object is the library entry. `GET /api/v1/careers/{id}/definition` returns the entire competency model — levels, sections, groups, skills and learnings — in a single response, which is what an integration rendering a career should use rather than walking the parts.

## One scale, company-wide

There is exactly one [grading scale](/api-docs/resources/grading-scale) per company, and it is **read-only over the API**. Every benchmark on every career and every achieved grade references a **rung** of that scale by id. Grades and benchmarks are always returned as resolved rungs (`{ id, grade, label }`), never as bare integers — an integer alone does not rank meaningfully.

The scale locks once any grade is in use, which is why it is not writable here.

## Deleting is guarded

A career type cannot be deleted while careers still use it. This is the pattern across the library resources: definitions that other records point at refuse deletion rather than orphan those records.

## Activity

`GET /api/v1/careers/{id}/activity` is the fullest activity feed on the API — roughly 40 event types covering lifecycle, settings, skills, sections, levels, groups, learnings, assignments, labels and flags. It accepts `from`/`to` date filters, which makes it the feed a [poller](/api-docs/rest/polling) should watch.