---
title: "Invite Eligibility"
method: GET
path: "/clinic/invite/eligibility"
tags: ["clinic"]
---

# Invite Eligibility

`GET /clinic/invite/eligibility`

## Request

- Base URL: `https://api.projectindi.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.projectindi.com/clinic/invite/eligibility`
- Auth: none declared

Can the signed-in account claim this invite?

Runs the same two gates ``accept_invite`` does, in the same order, off the
same helpers - so the pre-flight can't drift from the write it predicts.
Unlike accept, a "no" is a 200 with a reason rather than an error: the
caller is asking a question, and the answer is the point.

## Query parameters

- `token` string, nullable

## Response `200`

Successful Response

- InviteEligibilityResponse
  - `can_claim` boolean, required
  - `reason` 'eligible' | 'already_in_this_organisation' | 'already_in_organisation' | 'invite_for_another_address' | 'no_pending_invite' | 'invite_expired', required
  - `email` string, required
  - `current_organisation_name` string, nullable

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/projectindi/apis/indi-agent-api-first-principles.md) - [All operations](https://skmtc.dev/projectindi/apis/indi-agent-api-first-principles/llms.txt) - [OpenAPI document](https://skmtc.dev/projectindi/apis/indi-agent-api-first-principles/revisions/25a7813e21fd?raw)