A page of the organization's gift cards

GET /gift-cards

A page of the organization's gift cards, newest issued first, limit per page (1–200, 50 when omitted) from offset, with the total; ?last4= finds a card by its code's last four characters and ?status= narrows to active, disabled or depleted.

A card shows its balance, expiry and history, never its code. Appends nothing: a read of the gift cards.

Access

Requires payments:read.

How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.

AI agent tool

Agents call this as fulfillment_list_gift_cards (Fulfillment: List gift cards), in the tenders toolset. It only reads.

Connecting an agent: AI agents.

Example

curl

curl -X GET 'https://fulfillment.getmanifold.io/gift-cards?last4=K7QM' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://fulfillment.getmanifold.io/gift-cards?last4=K7QM", {
  method: "GET",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}` },
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

Response · 200 · application/json

{
  "items": [
    {
      "id": "gcd_01a15912-6e02-7b3c-9d4e-5f6a7b8c9d0e",
      "last4": "K7QM",
      "currency": "AUD",
      "initialCents": 5000,
      "balanceCents": 5000,
      "status": "active",
      "expiresOn": "2029-10-21",
      "recipientId": "psn_01a1588a-0c41-7d2e-9a10-3b5c6d7e8f90",
      "note": "Birthday raffle prize",
      "issuedAt": "2026-10-21T03:02:11.000Z",
      "entries": [
        {
          "kind": "issued",
          "amountCents": 5000,
          "at": "2026-10-21T03:02:11.000Z"
        }
      ]
    }
  ],
  "total": 1
}

The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: fulfillment-manager.openapi.json. Base URL https://fulfillment.getmanifold.io.

Errors

Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.

`401`

Refusal	What it means	What to do
`Unauthorized` reason	The token is missing, expired or not one Manifold issued.	Get a fresh token and send the call again.
`TokenAlreadyUsed` tokenId	A single-use app token was already spent.	Mint a new token for this call.

`402`

Refusal	What it means	What to do
`SubscriptionRequired` status	The organization's subscription has lapsed, so writes are refused.	An owner settles billing. Reads still work meanwhile.

`403`

Refusal	What it means	What to do
`TenantRequired` userId	The token names no organization.	Choose the organization, then get a new token.
`ScopeRequired` required	The token's roles do not grant the scope this call needs.	Ask an owner or admin for a role that grants it.

`409`

Refusal	What it means	What to do
`MirroredFromSource` source	This area is fed by your source system until the organization goes live.	Make the change in the source system, or go live first.

`503`

Refusal	What it means	What to do
`RequestLogUnavailable` tokenId, reason	The service could not record the request, so it did nothing.	Try again shortly.

How refusals work everywhere: Errors.

Used in

Store credit and gift cards, step 6: Find the card by its last four