---
title: "List prepay purchase receipts"
method: GET
path: "/billing/receipts"
tags: ["Billing"]
---

# List prepay purchase receipts

`GET /billing/receipts`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/billing/receipts`
- Auth: HTTP bearer

Completed μ prepay purchases for the caller's organization, as receipts. The prepay counterpart of GET /billing/invoices: a prepay customer has receipts and no invoices. Requires org owner or admin.

## Query parameters

- `product` 'research' | 'design' | 'develop' | 'operate' | 'canon' | 'unattributed' | 'all'

## Response `200`

Receipt list

- object
  - `receipts` Receipt[], required
    - `id` string, required
    - `created` integer, required
    - `amountPaidCents` integer, required
    - `currency` string, required
    - `mmu` integer, nullable, required: μ credited in mmu at the face peg (1 cent = 1000 mmu). Null for a non-usd charge, which has no defined face value here.
    - `mu` string, nullable, required: The same credited amount expressed in native μ as a decimal string (1μ = 1000 mmu), emitted alongside `mmu` (MNE-6767, μ-native migration). Null whenever `mmu` is null.
    - `status` string, required
    - `receiptUrl` string, nullable, required
    - `instrument` object, nullable, required
      - `kind` string, required
      - `brand` string, nullable
      - `last4` string, nullable
      - `expMonth` integer, nullable
      - `expYear` integer, nullable
  - `stripeLinked` boolean, nullable, required

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.
- `502`: An upstream dependency returned an invalid response.
- `503`: An upstream dependency is currently unavailable. The request was not processed; retry after the cooldown window.

---

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