How Does a Gift Card API Work? Catalogs, Orders and Delivery Explained

A gift card API is what sits behind every “here’s a $10 Amazon card for finishing our survey” email you’ve ever received. Your software asks a provider for a card, the provider gets it from the brand, and a code lands in the recipient’s inbox seconds later, with nobody on your team copying codes out of a spreadsheet.

Most explanations stop at that diagram. If you’re about to build on one, you need the unglamorous parts too: what a request actually looks like, what happens when an order fails halfway, how you stop the same reward going out twice and who deals with a code that won’t redeem. We’ll walk through all of it, starting with a distinction most guides skip entirely.

What Is a Gift Card API?

A gift card API is a set of endpoints that lets software issue, order, deliver and track gift cards without manual work. There are two quite different kinds, and it’s worth knowing which one you’re looking at before you read any docs.

	Merchant gift card API	Multi-brand gift card API
What it does	Creates and manages your own store’s gift cards	Orders other brands’ cards from a catalog
Typical actions	Create, activate, load, redeem, deactivate	Browse catalog, place order, deliver, track status
Who uses it	Retailers, restaurants, POS and e-commerce platforms	Rewards, incentive, fintech and loyalty platforms
Example	Square’s Gift Cards API	Phaze, Tremendous, Runa, Giftbit, Tango

Square’s version is a good picture of the merchant kind: one API creates and retrieves cards, and a separate Gift Card Activities API activates them, loads funds and redeems balances at checkout. The rest of this guide covers the multi-brand kind, which is what most people mean when they search for a gift card API.

How a Gift Card API Works, Step by Step

Authenticate. Every request carries an API key, and some providers also sign requests. Phaze’s developer hub, for example, shows an API key sent alongside a SHA-256-based signature header.
Fund your account. Most multi-brand providers work from a balance you top up in advance, so each order draws down money you’ve already sent.
Pull the catalog. You fetch the brands available in each country, with their currencies and allowed amounts. Some brands come in fixed denominations, such as 10, 25 or 50, while others accept any amount within a range.
Place an order. Your backend sends the brand, amount, currency, recipient details and your own reference for the order.
Fulfillment. The provider issues the card from the brand and returns a code, a redemption link or card details, sometimes straight away and sometimes a few seconds later.
Delivery. Either the provider emails or texts the reward, or you show the code inside your own app.
Status updates. Webhooks tell your system when each order completes or fails, so you can update balances, notify the user or retry.
Reconciliation. At month end you match every order against the balance deductions, using the references you sent with each order.

What a Gift Card API Request Looks Like

Field names differ by provider, so treat this as an illustration of the shape rather than any one vendor’s schema. An order request usually carries five things:

{
  "external_id": "survey-4471-reward",
  "brand_id": "amazon-us",
  "amount": 25.00,
  "currency": "USD",
  "recipient": { "email": "maria@example.com" }
}

The first response often just confirms the order was accepted:

{
  "order_id": "ord_7Hk2Q9",
  "external_id": "survey-4471-reward",
  "status": "processing"
}

A few seconds later a webhook, or a status check, reports completed with the code or redemption link, or failed with a reason. The external_id is the field doing the quiet work here: it ties the provider’s order back to the survey, purchase or referral in your own database.

Where Gift Card API Integrations Go Wrong

The happy path takes an afternoon to build. These are the cases that cost money or support time later:

Duplicate orders. A network timeout makes your code retry, and the recipient gets two cards. Send your own unique reference with every order and reuse it on retries. Square’s example for creating a gift card includes an idempotency key for this reason, and Giftogram treats a repeated external_id as the same order instead of creating a new one.
Telling the user too early. If the first response says “processing”, wait for it to be completed before you show “your reward is on its way”, because some orders fail after they’re accepted.
Catalog drift. Brands go out of stock and allowed amounts change, so refresh the catalog you cache at least daily instead of hard-coding brand IDs.
The wrong country. A US card sent to someone in Canada is a support ticket waiting to happen, which is why catalogs filter by country.
Treating codes casually. A delivered code behaves like cash, so check your provider’s cancellation policy before launch and keep codes out of logs.

How Gift Card APIs Are Priced

There are three common models. Some providers charge face value with no fee on gift cards and make money elsewhere: Tremendous lists gift cards at face value and a 4% fee (minimum $0.25) on PayPal and Venmo payouts on its pricing page. Others offer usage-based plans, such as Xoxoday Plum’s pay-when-redeemed option of a platform fee plus a per-transaction fee. And some share the brand margin with you, so you earn on each card: Phaze says platforms can earn up to 3 to 5% on transactions.

How to Test a Gift Card API Integration

Build against the provider’s sandbox before you touch real money. Phaze runs a separate sandbox host and issues credentials through support@phaze.io, Giftbit offers a free sandbox called Testbed with a virtual balance, and Tremendous has its own sandbox environment. Before you go live, run these checks:

Submit the same order twice and confirm only one card is issued.
Order a brand that isn’t available in the recipient’s country and confirm you get a clear error.
Force a failed order and confirm the user isn’t told their reward was sent.
Replay a webhook and confirm your system doesn’t credit or notify twice.

Our guide to webhooks covers the last check in more depth.

Build Gift Card Rewards on the Phaze API

Phaze gives you one API for 2,500+ gift card brands, prepaid cards and mobile top-ups across 150+ countries, with catalog filtering by country, category and denomination, status webhooks and white-label delivery under your brand. Integration is free and partners earn a margin on every card. Book a discovery call and we’ll get you sandbox access.

Gift Card API FAQ

What is a gift card API?

It’s a set of endpoints that lets software issue, order, deliver and track gift cards automatically, either your own store’s cards or other brands’ cards from a provider’s catalog.

What’s the difference between a gift card API and a gift card reseller API?

A reseller or aggregator API connects you to many brands through one provider. “Gift card API” is the broader term and can also mean a merchant’s API for its own cards.

How long does a gift card API integration take?

A basic integration can take days rather than months; Runa, for example, says companies typically take a week or two to get running on its API. Error handling, webhooks and reconciliation add most of the extra time.

Are gift cards delivered instantly through an API?

Usually within seconds. Some orders return a code immediately and others confirm a few seconds later by webhook, so build for both.

Can I create my own store’s gift cards with an API?

Yes. Merchant gift card APIs, such as Square’s Gift Cards API, let you create, activate, load and redeem your own branded cards.