---
title: "Get an UMA invitation by code"
method: GET
path: "/invitations/{invitationCode}"
tags: ["Invitations"]
---

# Get an UMA invitation by code

`GET /invitations/{invitationCode}`

Retrieve details about an UMA invitation by its invitation code.

## Path parameters

- `invitationCode` string, required

## Response `200`

Invitation retrieved successfully

- UmaInvitation
  - `code` string, required — The unique code of the invitation
  - `createdAt` string, date-time, required — When the invitation was created
  - `claimedAt` string, date-time — When the invitation was claimed if it has been claimed
  - `url` string, required — The URL where this invitation can be claimed.
  - `expiresAt` string, date-time — When the invitation expires (if at all)
  - `inviterUma` string, required — The UMA address of the inviter
  - `inviteeUma` string — The UMA address of the invitee
  - `status` 'PENDING' | 'CLAIMED' | 'EXPIRED' | 'CANCELLED', required — The status of the invitation
  - `firstName` string — The inviter's first name. Will be displayed when the recipient clicks the invite link
  - `amountToSend` CurrencyAmount
    - `amount` integer, required — Amount in the smallest unit of the currency (e.g., cents for USD/EUR, satoshis for BTC)
    - `currency` Currency, required
      - `code` string — Three-letter currency code (ISO 4217) for fiat currencies. Some cryptocurrencies may use their own ticker symbols (e.g. "BTC" for Bitcoin, "USDC" for USDC, etc.)
      - `name` string — Full name of the currency
      - `symbol` string — Symbol of the currency
      - `decimals` integer — Number of decimal places for the currency

## Other responses

- `401` — Unauthorized
- `404` — Invitation not found
- `500` — Internal service error

## Changes

- **2026-05-28** `d0bce562bffd` — 6 warning
  - added the new `REQUEST_ID_MISSING` enum value to the `code` response property for the response status `401`
  - added the new `UMA_NOT_FOUND` enum value to the `code` response property for the response status `404`
  - added the new `WALLET_SIGNATURE_BODY_MISMATCH` enum value to the `code` response property for the response status `401`
  - added the new `WALLET_SIGNATURE_INVALID` enum value to the `code` response property for the response status `401`
  - …2 more
- **2026-03-03** `efe0d983985f` — 3 breaking, 15 info
  - the response's body type/format changed from ``/`` to `object`/`` for status `401`
  - the response's body type/format changed from ``/`` to `object`/`` for status `404`
  - the response's body type/format changed from ``/`` to `object`/`` for status `500`
  - removed `#/components/schemas/Error401_UNAUTHORIZED, #/components/schemas/Error401_INVALID_SIGNATURE` from the response body `oneOf` list for the response status `401`
  - …14 more
- …earlier changes not shown

[Full history](https://skmtc.dev/lightsparkdev/apis/grid-api/changes/invitations/:invitationCode/get.md)

---

[API](https://skmtc.dev/lightsparkdev/apis/grid-api.md) · [All operations](https://skmtc.dev/lightsparkdev/apis/grid-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/lightsparkdev/grid-api/revisions/d0bce562bffd/schema)