> For the complete documentation index, see [llms.txt](https://docs.tiny.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiny.plus/api/endpoints/cvs.md).

# CVs

{% hint style="warning" %}
Submission packs are invite only for now, so these requests answer only for accounts we've invited; [`/me`](https://docs.tiny.plus/api/endpoints/me.md#integrations) carries `integrations.submissions`.
{% endhint %}

A CV holds one team member's experience for submissions: their title, a summary of up to 150 words, registrations, years in practice and at the firm, education, memberships and languages, the expertise and sectors they are tagged with, and the projects worth naming, in order, each with a one-line role. A person can keep more than one, told apart by `variant` (Healthcare, Transport, Short), with one of them their default. CVs come with submission packs, a Pro plan feature an account admin turns on under Account Settings → Submissions.

CVs live at `/v2/cvs`. They support every request on the [Records](https://docs.tiny.plus/api/endpoints/records.md) page: list, get, history, create, update, delete and search.

## Who sees a CV

Everyone in the account reads every CV. A CV belongs to the team member it is about: they are its assigned user, so they can change it, as can records admins and anyone with the Submissions role; for anyone else a write answers 403. The finished pack is a document on its project, which anyone who sees the project can open.

## Fields

`GET /v2/fields/cvs` lists them. The ones that aren't plain text:

| Field               | Holds                                                                                                                       |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| `team_member`       | The team member's id. Required. Setting it makes them the CV's `assigned_user`.                                             |
| `variant`           | What sets this CV apart from the person's others. The name is filled in from the person and the variant when it isn't sent. |
| `is_default`        | `1` for the CV a pack picks first. A person has exactly one: the first CV made for them, or the one most recently marked.   |
| `summary`           | Up to 150 words. A longer summary is refused.                                                                               |
| `availability_note` | For the office; never printed in a pack.                                                                                    |
| `notable_projects`  | The projects the CV names, in order, each with its `role`: tiny+ projects and ones from a previous firm. See below.         |
| `hero`              | The photo. It starts as the person's own.                                                                                   |

Expertise and sectors are tags: `GET /v2/form_structure/cvs/view` lists the categories and their tags, and a record carries them as `tags_{id}`, as [Tags](https://docs.tiny.plus/api/concepts/record-types.md#tags) describes.

## Notable projects

A record read on its own carries `notable_projects`: the projects in the order the CV lists them, each with its `role`. A tiny+ project has its `id` and `name`; a project from before the person's time at the firm, typed onto the CV, has its `name`, `client` and `year` and no `id`.

```json
{
    "id": "219201",
    "name": "Maya Lin — Healthcare",
    "team_member": "191",
    "variant": "Healthcare",
    "is_default": "1",
    "notable_projects": [
        {"id": "8814", "name": "Tasman Health new wing", "role": "Project architect"},
        {"name": "Westfield Medical Centre", "client": "Westfield Health", "year": "2019", "role": "Design lead"}
    ]
}
```

To change them, send `notable_projects` as the whole list in the order wanted: a tiny+ project as `{"id", "role"}`, any other as `{"name", "client", "year", "role"}` (`client` and `year` optional). Up to 20 lines; a pack prints the first eight.

```bash
curl -X PATCH "https://api.tiny.plus/v2/cvs/{{id}}" \
  -H "Authorization: Bearer {{user_access_token}}" \
  -H "Content-Type: application/json" \
  -d '{
        "notable_projects": [
            {"id": "8814", "role": "Project architect"},
            {"name": "Westfield Medical Centre", "client": "Westfield Health", "year": "2019", "role": "Design lead"}
        ]
      }'
```

A line left out is taken off the CV. A tiny+ project the token's user can't see is ignored, as is a typed line with no name. A list of bare ids still works, with `notable_roles` as an object of role by id.

## Creating a CV

```bash
curl -X POST "https://api.tiny.plus/v2/cvs" \
  -H "Authorization: Bearer {{user_access_token}}" \
  -H "Content-Type: application/json" \
  -d '{
        "team_member": "191",
        "variant": "Healthcare",
        "title": "Senior Architect",
        "summary": "Fourteen years of hospital and aged care work, from masterplanning to delivery."
      }'
```

```javascript
{
    "id": "219201"
}
```

| Case                                        | Response                                                                 |
| ------------------------------------------- | ------------------------------------------------------------------------ |
| No `team_member`, or one not on the account | `400 {"error": "A processing error occurred while adding this record."}` |
| A summary over 150 words                    | `400 {"error": "A processing error occurred while adding this record."}` |
| Submission packs not on for the account     | The type is still there, and so are its records; the menus hide them.    |
