Rewordin
  • Features
    ⚡ Bulk Gift Card API🔌 HRIS Integrations🌍 Global Rewards🎁 Reward Marketplace📊 Analytics & ReportingView all features →
  • Use Cases
    💰 Sales Teams📣 Marketing Teams🤝 Channel Partners👥 HR & People Ops⚙️ Engineering Teams🎧 Customer Support📊 Finance & AccountingView all use cases →
  • Resources
    🎁 Employee Rewards👏 Employee Recognition📈 Employee Engagement🏭 Industries🏆 Customers📝 Blog💰 Pricing🏢 About Us🧮 ROI Calculator
FeaturesBulk Gift Card API NewUse CasesEmployee RewardsEmployee RecognitionEmployee EngagementIndustriesBlogAboutROI CalculatorPricing
Log In
RewordinREWORDIN

The global employee rewards platform. Recognize, reward, and retain your best talent worldwide.

Platform

FeaturesBulk Gift Card APIHow It WorksIntegrationsPricingSecurityAll Use Cases

Solutions

HR & People OpsSales TeamsEngineering TeamsMarketing TeamsCustomer SupportFinance & AccountingChannel Partners

Resources

Employee RewardsEmployee RecognitionEmployee EngagementIndustriesROI CalculatorBlogRecognition Software 2026Tax-Free Gifts PolandROI of RecognitionRewards Program GuideHRIS Integration Guide

Company

AboutCustomers
hello@rewordin.com
Wrocław, Poland

Get the latest insights on employee rewards.

Secure Payment Methods

Visa
Mastercard
American Express
PayPal
Apple Pay
Google Pay
Samsung Pay
Stripe
Klarna
Amazon Pay
Shop Pay
Square
Discover
Maestro
UnionPay
Alipay
Bitcoin
Ethereum
BitPay
MetaMask
Cash App
Skrill
Payoneer
Western Union
MoneyGram
Gumroad

And 100+ more payment methods available worldwide

© 2026 Rewordin. All rights reserved.

Privacy PolicyTerms of ServiceSecurity

Book a Demo

We'll contact you within 24 hours to schedule your demo

For developers & procurement teams

Bulk Gift Card API — Volume Discounts for B2B | Rewordin

Send Steam, Razer Gold, PlayStation, Nintendo, Xbox, Apple, iTunes, Amazon, and Airbnb gift cards to your customers and employees via a single REST API. Volume discounts built in. Delivery in under 60 seconds.

9 brands in one API
Volume discounts
Developer-first docs
Signed webhooks
Brands available via the API

9 high-demand brands, one integration

The brands your recipients actually want, reachable from a single endpoint. Every brand has its own regional catalog, currency set, and delivery speed. We pick the right one per recipient automatically.

Steam

Gaming credits, USD/EUR/GBP/RUB/PLN/BRL and 30+ more currencies. Best for: gaming platforms, esports rewards.

Razer Gold

Top-up for 33M+ Razer users globally, redeemable across 8,000+ games. Best for: APAC & LATAM gaming rewards.

PlayStation (PSN)

PSN wallet top-ups in 70+ countries. PS Store, games, DLC, subscriptions. Best for: console gaming, creator payouts.

Nintendo (eShop)

eShop funds in 40+ countries. Switch, 3DS, switchable to local currency at redemption. Best for: family-friendly rewards, EMEA & NA.

Xbox

Xbox Live and Microsoft Store credits globally. Subscriptions, games, DLC. Best for: cross-platform gaming rewards.

Apple

App Store & iTunes credits in 175+ countries. Apps, games, music, movies, iCloud+ subscriptions. Best for: developer rewards, global teams.

iTunes

Legacy iTunes credit in 175+ countries. Music, movies, TV, books. Best for: entertainment-lover personas.

Amazon

Region-specific Amazon balance (Amazon.com, .co.uk, .de, .jp, etc.). Anything Amazon sells, in the recipient region. Best for: universal default reward.

Airbnb

Airbnb gift credits globally. Best for: travel rewards, executive-level recognition, milestone gifts.

What it is

What is a bulk gift card API?

A definition, the difference vs. one-off web purchases, and where Rewordin fits in.

A bulk gift card API is a programmatic interface that lets a business send large volumes of digital gift cards directly from its own software — without a human clicking “Buy” for each one. Instead of browsing a marketplace, picking a brand, paying with a credit card, and forwarding an email, your system makes a single POST /v1/orders call with a list of recipients, and the gift cards are delivered automatically.

The “bulk” part is what separates a true API from a one-off web purchase. A bulk API is built for repeated, automated, high-volume use: it includes things you would never need for a single gift card (idempotency keys, signed webhooks, batch endpoints, sandbox environments, audit logs) and it includes things you would never get from a one-off flow (volume discount tiers, batch reconciliation, contracted pricing). The unit economics change once you cross a few hundred cards a month, and the engineering shape of the integration changes once you cross a few thousand.

Rewordin sits in this market as a B2B gift card supplier with a developer-first API. We carry 9 of the highest-demand brands (Steam, Razer Gold, PlayStation, Nintendo, Xbox, Apple, iTunes, Amazon, and Airbnb) and the full 5,000+ brand catalog behind the same endpoint. We do not white-label a third-party catalog — every brand is a direct partnership, with its own delivery SLA, regional availability, and reconciliation flow. If you are sourcing gift cards at scale, that distinction is the whole game.

Why Rewordin

Why B2B buyers choose Rewordin for bulk delivery

Five structural benefits that show up the moment your order volume crosses a few hundred cards a month. No prices — just the shape of the platform.

9 brands in one API

Steam, Razer Gold, PlayStation, Nintendo, Xbox, Apple, iTunes, Amazon, and Airbnb — all reachable from a single POST. One integration, one set of credentials, one contract.

Volume discount tiers

Per-card cost drops automatically as your monthly order volume grows. No renegotiation, no separate SKU. Your current tier is always visible in the dashboard.

Webhooks for every state

order.created, order.processing, order.delivered, order.failed — signed with HMAC, retried with exponential backoff, fully logged. No polling, no scraping.

Multi-region delivery

One API call can hit a recipient in Tokyo and a recipient in São Paulo. We pick the correct regional catalog for each recipient, convert currency, and apply local tax.

Single contract, single invoice

One MSA, one onboarding call, one monthly invoice in your base currency. No per-brand reseller paperwork, no per-region tax documents for your finance team.

Volume discounts

How volume discounts work

Discounts grow as your monthly order volume grows. We negotiate once, you send more, your per-card cost drops automatically. No quarterly renegotiation, no separate SKUs, no manual approval chain.

Tier 1
StarterStandard list pricing, no volume commitment. Available to every account from day one.
Default at signup
Tier 2
GrowthUnlocks once your trailing-30-day order volume crosses the Growth threshold. The dashboard shows the next-tier requirement in real time.
Automatic — no contract change
Tier 3
ScaleSustained monthly volume. Per-card pricing drops further; webhook volume, batch size, and custom SLAs become available.
Includes priority support
Enterprise
EnterpriseForward-rate locks, contracted volume pricing, dedicated integration engineer, custom delivery windows. Talk to your account manager.
Tailored to your rollout

How the discount actually applies

When you create an order via the API, the response includes a unit_price for each line item. That price is the discounted price for your current tier — not the list price. If you cross into a higher tier mid-month, the next order automatically uses the new tier’s pricing. You never negotiate the discount; you simply earn it as your volume grows. The dashboard always shows your current tier, the next tier’s threshold, and how many cards you need to clear it.

Locking rates for predictable budgeting

For finance teams that don’t want surprise cost variance on a quarterly accrual, Enterprise customers can lock their per-card rate forward by quarter. The rate you see at the moment of lock is the rate you pay on every order for the next 90 days, regardless of tier drift. This is standard for our Enterprise rollouts running a $50K+ monthly volume.

Developer quickstart

Make your first order in 10 minutes

One endpoint, one API call, one signed response. We return the order ID and a per-recipient tracking URL — no polling, no scraping, no fragile scraping logic to maintain.

cURL · POST /v1/orderssandbox.rewordin.com
curl https://api.rewordin.com/v1/orders \
  -H "Authorization: Bearer sk_test_REDACTED" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: ord_2026_06_10_abc123" \
  -d '{
    "external_id": "campaign-q2-launch-2026",
    "recipients": [
      {
        "email": "alex@customer.com",
        "country": "US",
        "brand": "amazon",
        "amount": 5000,
        "currency": "USD",
        "message": "Thanks for being an early supporter!"
      },
      {
        "email": "lin@partner.io",
        "country": "JP",
        "brand": "playstation",
        "amount": 10000,
        "currency": "JPY",
        "message": "Q2 partner award — great work."
      }
    ],
    "metadata": {
      "campaign": "q2-launch",
      "cost_center": "marketing-rewards"
    }
  }'

200 OK — order accepted

The API returns the order ID and a per-recipient status. Each delivery is also confirmed asynchronously via a signed webhook event (order.delivered or order.failed) so you never have to poll.

Response · application/json200 OK
{
  "id": "ord_01HXYZABCDEF...",
  "object": "order",
  "status": "processing",
  "external_id": "campaign-q2-launch-2026",
  "created_at": "2026-06-10T13:18:42Z",
  "tier": "scale",
  "currency": "USD",
  "totals": {
    "subtotal_cents": 8250,
    "discount_cents": 412,
    "total_cents": 7838
  },
  "recipients": [
    {
      "id": "rcp_01...",
      "status": "delivered",
      "brand": "amazon",
      "country": "US",
      "tracking_url": "https://rewordin.com/r/rcp_01...",
      "delivered_at": "2026-06-10T13:18:51Z"
    },
    {
      "id": "rcp_02...",
      "status": "processing",
      "brand": "playstation",
      "country": "JP",
      "tracking_url": "https://rewordin.com/r/rcp_02..."
    }
  ]
}

What you get out of the box

  • OpenAPI 3.1 spec at https://api.rewordin.com/v1/openapi.json
  • Postman collection, downloadable from the dashboard
  • Official SDKs for JavaScript/Node, Python, and Go (beta)
  • Sandbox environment with test brands — no real cards, no real money
  • Webhook signing with HMAC-SHA256, exponential-backoff retries, idempotent event IDs
  • Idempotency keys on every order so a network retry never creates a duplicate
  • Live test in the dashboard: paste a payload, see the response, copy the working code
Capability matrix

Bulk API vs. one-off Web Buy

The honest side-by-side. The bulk API is a developer surface designed for programmatic, high-volume use. The Web Buy flow is the dashboard checkout for ad-hoc orders. Different products, different use cases.

Capability
Bulk API
Web Buy
REST endpoints (orders, status, cancel, refund)
Full
Basic
Signed webhooks for every state change
Yes
No
Volume discount tiers
Yes
No
Multi-region, multi-currency batches
Yes
No
Custom branding on the recipient page
Yes
No
Order tracking dashboard + per-recipient audit log
Yes
Email only
Batch orders (1 to 100,000 recipients in one call)
Yes
No
Idempotency keys (safe retry on network errors)
Yes
No
Sandbox environment with test brands
Yes
No
OpenAPI 3.1 spec + Postman collection
Yes
No
Use cases

Where the bulk API fits

Four patterns we see repeatedly across our API customers. Each one runs hands-off once the integration is live.

SaaS platforms that reward users

Cashback, referral bonuses, milestone unlocks — emitted as a gift card from your own platform. Most customers wire our API into the same webhook that fires on signup or first-purchase. The user never knows Rewordin is in the loop.

Best fit: a SaaS sending $5-500 rewards at >1k/month.

HR-tech, payroll, recognition platforms

White-label the delivery. Your brand on the email, your colors on the page, your domain on the link — but the actual catalog, FX, and tax work is on us. Webhook back to your platform so you can record the redemption in the employee file.

Best fit: HR-tech platforms with 50+ enterprise customers.

Loyalty & cashback programs

Member earns points, cashes them out for a gift card. We deliver instantly, you keep the engagement loop. Per-recipient metadata (member ID, campaign ID, redemption code) flows through the API so attribution works end-to-end.

Best fit: consumer loyalty with >10k active members.

E-commerce returns & promotions

Replace refund-to-store-credit with refund-to-gift-card-from-9-brands. Average uplift on a returns program using branded gift card over cash refund: 18% retained margin. Promo code drops at checkout integrate via the same API.

Best fit: DTC e-commerce with >$5M annual GMV.

The common thread across these use cases: the gift card is the output of something else that already happens in your product. A user converts points, closes a deal, hits a milestone, or refers a friend — and our API turns that event into a delivery, end-to-end. The HR-tech and SaaS patterns in particular pair well with our broader recognition playbook for tech teams and the points-based vs. gift card analysis in the blog. If you are weighing gift cards against cash bonuses, the case for branded rewards is worth a read.

For HR-tech and People Ops teams building a budget case, the CFO-ready budget framework walks through the exact spreadsheet a finance team needs to greenlight a programmatic rewards program. And if you are choosing between building in-house vs. using an API, the procurement buyer’s guide lays out the build-vs-buy math.

Coverage

Delivery & regional coverage

The 9 brands are not equal in regional coverage. Some are global, some are region-locked, some have country-specific storefronts. The API picks the right catalog per recipient automatically.

Steam

Global, 30+ currencies. USD, EUR, GBP, RUB, PLN, BRL, JPY, and more. Top-up to Steam wallet.

Razer Gold

130+ countries. Strongest in APAC, MENA, and LATAM. PIN-style codes plus wallet top-up.

PlayStation (PSN)

70+ countries. Region-locked — we pick the right PSN region per recipient automatically.

Nintendo (eShop)

40+ countries. Single-use codes that work in the recipient’s local eShop.

Xbox

Global. Microsoft Store and Xbox Live credits in 25+ currencies.

Apple

175+ countries. App Store & iTunes credits in local currency.

iTunes

175+ countries. Legacy Apple ID balance for media purchases.

Amazon

20+ regional Amazon storefronts. US, UK, DE, FR, IT, ES, JP, IN, BR, CA, AU, MX, and more.

Airbnb

Global. USD-denominated gift credit that recipients can apply to any stay.

How regional catalog selection works

When you submit a recipient with a country, the API selects the correct regional catalog for that country and brand. A brand: "amazon" + country: "DE" produces an Amazon.de balance; the same brand with country: "JP" produces an Amazon.co.jp balance. You do not have to manage region codes yourself; we do it server-side. The full list of supported (brand, country) pairs is published in the OpenAPI spec and updated whenever we add a new region.

Edge cases we handle for you

  • Country not in the brand’s catalog? We surface a clear 422 with a hint to the closest supported region
  • Currency mismatch? We convert at mid-market FX at the moment of order creation
  • Recipient email invalid? We fail-fast on validation, not 6 hours later after the brand rejects the code
  • Recipient wants a different brand? They can self-serve swap via a hosted picker, on your branded domain
Trust & security

Compliance, security, and audit

Enterprise-grade defaults. B2B gift card distribution has real regulatory weight — every B2B account goes through KYB, every API key is scoped, and every event is logged. Here is exactly what is in scope.

KYC for B2B buyers

Standard KYB on every API account: legal entity, beneficial owners, signed MSA, sanctions screening. Required by all major brand partners before we can turn the API on for your account.

IP allow-listing

Optionally restrict API access to a list of your outbound IPs. Available on Pro and Enterprise. Most fintech and healthcare customers enable it on day one.

Scoped API keys + RBAC

Issue per-environment keys (live, sandbox), per-service keys (read-only vs order-creating), and per-team keys. Revoke from the dashboard; keys expire automatically after 90 days of inactivity.

Audit log + immutable trail

Every order, refund, and admin action is logged with actor, IP, and timestamp. Logs are exportable as JSON or CSV for your SOC 2 auditor. Retention: 24 months minimum.

SOC 2 Type II roadmap

Type I in production today; Type II observation period underway. GDPR-compliant data handling, EU data residency available for EU-only customers. PCI scope limited to the order-payment flow.

Uptime + status page

99.95% API uptime target over the trailing 12 months, with a public status page. Webhook retries are automatic and idempotent — your system receives every event exactly once.

Most procurement and security teams can complete their review of Rewordin in under two weeks, using a standard SIG-lite questionnaire plus our public trust portal. We share our latest penetration-test summary, SOC 2 progress notes, sub-processor list, and DPA on request under NDA. For SSO, HRIS, and SCIM integrations, we ship SAML 2.0 and OIDC out of the box and SCIM 2.0 for user provisioning. Every event the API emits is also available in the real-time analytics dashboard — order-level reconciliation, per-recipient status, brand-level mix, and cost-center rollups.

Integration options

Four ways to integrate

The same API, four different on-ramps. Pick the one that matches your team’s stack and timeline.

REST API

OpenAPI 3.1 spec, Postman collection, predictable JSON. The fastest path to production.

Official SDKs

JavaScript/Node, Python, and Go (beta). Idiomatic, type-safe, and pinned to the same OpenAPI.

Webhooks

Signed events for every state change. HMAC-SHA256, exponential backoff, full retry log.

No-code dashboard

Same API, just a form. CSV upload of recipients, click Send. Zapier-style triggers from your CRM.

For non-developers or one-off projects, the dashboard no-code form calls the same API under the hood — you upload a CSV of recipients, click Send, and the same webhooks fire. For SaaS, HR-tech, and loyalty platforms, the REST API + webhooks is the right path. For most teams, the bulk of the integration work is mapping your internal event to our recipient schema; the actual API call is one HTTP request. The procurement buyer’s guide walks through a typical rollout timeline in detail.

FAQ

Frequently asked questions

The questions B2B buyers, developers, and procurement teams ask most. If yours is not here, our API team replies within 4 business hours.

What brands are available through the bulk gift card API?

Nine high-demand brands: Steam, Razer Gold, PlayStation (PSN), Nintendo (eShop), Xbox, Apple, iTunes, Amazon, and Airbnb. The full 5,000+ brand catalog is also reachable via the same API — those 9 are the highest-volume, highest-margin brands we recommend for B2B use cases.

How do volume discounts work — do I need to negotiate each tier?

No. Discount tiers are automatic. As your trailing-30-day order volume grows, your per-card price drops to the next tier without renegotiation, contract amendment, or sales call. You can see your current tier and the next threshold in the dashboard at any time. For Enterprise customers running multi-quarter rollouts, we also offer locked forward rates and contracted volume pricing — talk to your account manager.

Can I send gift cards to recipients in different countries with one API call?

Yes. A single POST to /v1/orders accepts an array of recipients, each with its own country, brand, amount, and currency. Rewordin picks the right regional catalog for each recipient, applies the correct local tax treatment, and converts from your base currency if needed. There is no separate “international endpoint” — it is one API call for one recipient in Tokyo and one in São Paulo. See how global delivery works in detail.

What does the API integration look like — do you have SDKs?

The integration is a single REST endpoint: POST /v1/orders with a JSON body containing your recipients, brands, and amounts. We return a 200 with the order ID, per-recipient delivery status, and a tracking URL. We ship an OpenAPI 3.1 spec, a Postman collection, and official SDKs for JavaScript/Node, Python, and Go (Go is in beta). For non-developers, the dashboard offers a no-code CSV upload that calls the same API under the hood.

How quickly are gift cards delivered after an API call?

Digital gift cards are delivered to the recipient in under 60 seconds from a successful API call. The delivery itself is async — you receive a 200 with the order ID, and a webhook event confirms each individual delivery (order.created, order.delivered, or order.failed). For batch orders with thousands of recipients, median delivery time is 47 seconds per recipient and the batch completes in roughly 2-3 minutes total.

What is the difference between the bulk API and a one-off Web Buy order?

The bulk API is designed for programmatic, repeated, high-volume use: it includes idempotency keys, webhooks, batch orders, sandbox and live environments, an OpenAPI spec, and automatic volume discount tiers. The Web Buy flow is a one-off purchase flow in the dashboard for ad-hoc orders (“buy a $50 Steam code right now for a single recipient”) — it is not a developer surface and it does not qualify for volume discounts. If you are sending more than a handful of gift cards per month, the bulk API is the right product. For evaluating which platform to build on, our platform-selection framework lays out the criteria procurement should weigh.

Talk to our API team

Tell us your monthly volume, the brands you care about, and your integration timeline. We will send a sandbox key and a 30-minute walkthrough of the dashboard, the API, and the webhook flow. When you are ready, our pricing page shows how the per-card cost drops with each volume tier.

Explore All Features