---
title: "Read a clan command receipt for the current account"
method: GET
path: "/v1/clans/operations/{operationId}"
tags: ["clans"]
---

# Read a clan command receipt for the current account

`GET /v1/clans/operations/{operationId}`

## Request

- Base URL: `https://app.legend.trade/api/rest`
- URL: `https://app.legend.trade/api/rest/v1/clans/operations/{operationId}`
- Auth: HTTP bearer

Unknown means no committed receipt is visible. It does not prove rejection. Retry the original command with the same operationId and input only while the outcome is unknown. Every receipt is terminal, including rejection. An explicit new attempt after rejection needs a new UUID. Refresh related reads after either terminal outcome. A rejection can complete domain cleanup, such as the decline of an obsolete membership request. Receipts have no expiry.

## Path parameters

- `operationId` string, uuid, required

## Response `200`

Successful response

- ClanOperation
  - `operationId` string, uuid, required
  - `status` 'unknown' | 'succeeded' | 'rejected', required
  - `operation` string, nullable, required
  - `error` object, nullable, required
    - `code` string, required
    - `message` string, required

## Other responses

- `400`: Invalid input data
- `401`: Authorization not provided
- `403`: Insufficient access
- `404`: Not found
- `500`: Internal server error

## Changes

- **2026-10-25** `8d368659667e`: 1 breaking, 1 info
  - the response property `operation` became nullable for the status `200`
  - response property `operation` list-of-types was narrowed by removing types `null` from media type `application/json` of response `200`
- **2026-10-15** `31e6c9235b61`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/legend/apis/legend-api/changes/v1/clans/operations/:operationId/get.md)

---

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