GIFQ API· For developers

One gift card API for 5,000+ brands in 90+ countries

You want your app to hand someone a gift card. Without us that's an account with Amazon, another with Starbucks, another with whoever matters in Germany — each with its own API, its own idea of what a "product" is, and its own way of telling you something broke. With us it's one POST, and it's the same call whether you send one card or ten thousand.

One endpoint, every brand

Free sandbox — build before you pay anything

Face value. We don't mark the cards up

Already running on GIFQ

  • CoinGate Gift Cards
  • Rizon
  • ACEB
  • JumpTask
  • LBank

Every brand has its own API, and none of the catalogs line up

We ran gift card operations for years before we built this. Every brand had its own integration, its own idea of what a product was, and its own outage schedule. When a card didn't arrive, we usually heard it from the customer before our own systems noticed.

Adding one brand meant a contract, a sandbox, and a fortnight. Adding a country meant doing the whole thing again, often in a language nobody on the team spoke. GIFQ is the integration we wanted to exist — one that covers the lot, so nobody has to do that again.

How it works

  1. 1

    Get a token

    Every request carries an X-Api-Token header. Point it at api-sandbox.gifq.com and you can build the entire integration before you spend anything.

  2. 2

    Ask what you can actually sell

    GET /api/products gives you the brands that work in the country you care about — not a global list you have to filter down yourself and hope you got right.

  3. 3

    Order the card

    POST /api/orders with a brand, an amount, a currency, and a country. Attach your own reference and the order stays findable from your side as well as ours.

  4. 4

    Find out what happened

    GET /api/orders/:id for where it got to. /api/balances for what's left. /api/transactions for every order you've ever placed, which is the one finance will ask for.

What that actually buys you

Ten cards or ten thousand, same call

There's no batch format to learn and no separate bulk contract to sign. You loop. Ordering at volume is a property of your code rather than a different product with its own paperwork.

Adding a brand costs you nothing

Who's available, in which country, at what denominations — that's ours to keep current. When someone asks for one more brand next quarter, you don't renegotiate anything. You just start requesting it.

One balance, one ledger

Every order draws down the same balance and lands in the same transaction list. When finance asks what you spent last month, that's a query, not a folder of PDFs from eleven suppliers.

Break it in the sandbox first

api-sandbox.gifq.com behaves like production and costs nothing. Test your error handling against it properly — the interesting bugs only show up when a card fails, and you'd rather meet them there.

See all 5,000+ brands first

Before you talk to anyone, check we actually carry what your people want — including in the markets you care about. We'll send the full catalog over.

One email. No sequence, no drip campaign, unsubscribe whenever.

Questions we get asked

The rest of the platform

Every line runs on the same catalog, balance, and ledger, so adding another one later doesn't mean starting over.

Go and read the docs

The sandbox is free and the reference is public, so you can find out whether this fits before talking to anyone. If you'd rather ask a person first, that works too.

One email. No sequence, no drip campaign, unsubscribe whenever.