---
title: "Show Interest"
method: POST
path: "/api/roles/{role_id}/interest"
tags: ["roles"]
---

# Show Interest

`POST /api/roles/{role_id}/interest`

## 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}/interest`
- Auth: none declared

Put your hand up for a role. Idempotent.

## Why a profile is required

422 for an account with no ``user_profiles`` row. What a company receives is a
list of people, and a person with no profile is a line that says nothing: no
name, no headline, no skills, nothing to decide on. Sending that is worse than
sending nothing, because it costs the company a click to find out it was
empty and it tells the candidate their interest was registered when in
practice it cannot be acted on. The message names the fix and the client links
to it.

Note what is NOT required: a PUBLIC profile. A private profile 404s for
strangers, but expressing interest is a deliberate, per-role disclosure to one
company, and requiring publication would make "let this one employer see me"
impossible without also making "let everybody see me" true. The interest is
the consent, and it is scoped to the role it was given on.

## Why you cannot show interest in your own role

409, because it is a category error rather than a permission problem, and
because a company appearing in its own candidate list would be the first bug
reported.

## 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)