---
title: "List Interested"
method: GET
path: "/api/roles/{role_id}/interested"
tags: ["roles"]
---

# List Interested

`GET /api/roles/{role_id}/interested`

## Request

- Base URL: `https://api.parlel.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.parlel.com/api/roles/{role_id}/interested`
- Auth: none declared

The people who put their hand up for one of YOUR roles.

Owner-only, through ``_owned_role``, so a stranger gets the same 404 they get
for a draft. This is the payoff of the whole feature and it is also the most
sensitive read in the company surface: it is a list of named people who are
looking, attached to a specific job.

Each person is rendered by ``_directory_profile`` -- the SAME serialiser the
candidate search uses. That is deliberate and load-bearing: it is a hard
allowlist that cannot carry a contact field in any mode, so showing interest
hands a company a profile to read and never an email address to mail. If a
candidate wants to be contactable they open their contact gate, which is one
decision they make once, on their own page, rather than a side effect of
pressing a button on a job.

Newest first, because the question a company opens this with is "who is new
since I last looked".

## Path parameters

- `role_id` string, required

## Headers

- `authorization` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/parlel/apis/parlel-api.md) · [All operations](https://skmtc.dev/parlel/apis/parlel-api/llms.txt) · [OpenAPI document](https://skmtc.dev/parlel/apis/parlel-api/revisions/4d41a8f5cfc9?raw)