# ProjectLink

A named external URL pinned to a project, such as a staging environment, a design file or a repository. Deleting one is permanent, and every write bumps the owning project's `updated_at` and lands in the project's activity timeline.

## Used by
- GET /api/v2/project-links: List project links (ProjectLinkList)
- POST /api/v2/project-links: Create a project link (ProjectLink)
- GET /api/v2/project-links/{project_link}: Read a project link (ProjectLink)
- PATCH /api/v2/project-links/{project_link}: Update a project link (ProjectLink)

## ProjectLink fields
- id (integer, required): Unique identifier.
- project_id (integer, required): Owning project.
- project (Ref or ProjectSummary, required): The project this link belongs to.
- name (string ≤ 255, required): Link name as shown in the UI, e.g. `Staging`. This is the default sort key.
- url (string, required, multiline): The link target, e.g. `https://staging.example.test`.
- created_at (timestamp (YYYY-MM-DDThh:mm:ssZ), required): Creation timestamp.
- updated_at (timestamp (YYYY-MM-DDThh:mm:ssZ), required): Last-write timestamp; use for incremental sync.
- links (ProjectLinkLinks, required)
  - self (url, required): The canonical URI of this record.

## Variants

### ProjectLinkList

What a collection returns, and what `?view=summary` returns on a single record.

8 fields.
Identical to the detail object above.

### ProjectLinkSummary

The embedded form: what you get when another resource carries this one and you did not `include` it.

3 fields.
Omits: project_id, project, created_at, updated_at, links

### ProjectLinkLinks

The `links` object on this resource.

Keys: self

## Example
```json
{
  "id": 1,
  "project_id": 1,
  "project": {
    "id": 1
  },
  "name": "Staging",
  "url": "https://staging.example.test",
  "created_at": "2026-03-04T09:15:00Z",
  "updated_at": "2026-03-04T09:15:00Z",
  "links": {
    "self": "https://<your-url>/api/v2/work-items/1"
  }
}
```
