If your company is evaluating a gift card API, the question is rarely “which API can send a reward?” Most modern providers can do that. The harder question is which API fits your operating model: catalogue access, supplier coverage, funding, order workflow, recipient experience, reporting, reconciliation, and the level of control your team needs.
Runa, Tillo, and Tremendous all appear in B2B conversations around digital rewards, payouts, and gift card infrastructure. Their public documentation points to different strengths. This comparison looks at the practical differences a buyer, product manager, operations lead, or technical team should review before choosing a partner.
This article is based on public documentation and product pages available at the time of writing. API capabilities, pricing, coverage, and onboarding rules can change, so teams should validate final requirements with each provider before implementation.
Public documentation reviewed:
Quick comparison: Runa, Tillo and Tremendous
Runa
Runa presents itself as infrastructure for global payouts, including gift cards, prepaid cards, and push-to-card options. Its developer documentation highlights RESTful API patterns, API key authentication, production and playground environments, idempotency keys, sync or async execution modes, and order creation through a /order endpoint.
This makes Runa interesting for teams that think in terms of payout infrastructure rather than only gift card catalogue access. If your program includes incentives, payouts, or multiple digital value formats, Runa may fit a broader operating model.
Tillo
Tillo positions its API around gift card access, issuance, and management across a large global brand catalogue. Public pages emphasize digital gift card issuance, product and pricing data, order status, refunds, top-ups, supported markets and currencies, and sandbox onboarding.
This makes Tillo interesting for teams where the gift card catalogue itself is central: brand availability, denominations, delivery methods, local markets, gift card transaction types, and supplier-style operational management.
Tremendous
Tremendous positions its API around rewards, incentives, and payouts, with a strong developer onboarding message. Its documentation highlights sandbox and production URLs, bearer token authentication, POST /orders, campaign and product selection, recipient delivery, and client libraries for common programming languages.
This makes Tremendous interesting for teams that want to launch reward or payout flows quickly, especially where campaigns, recipient delivery, and broad payout methods matter.
Visual decision map
Decision snapshot
How to compare the API documentation
A useful gift card API comparison should go beyond endpoint names. For B2B teams, documentation quality matters because it predicts how hard the implementation and daily operations will be.
Review these areas carefully:
- Authentication and environment setup.
- Sandbox availability and how closely it mirrors production.
- Catalogue or product endpoint structure.
- Order creation and idempotency logic.
- Sync vs async processing and webhook support.
- Delivery methods and recipient experience.
- Refund, cancellation, replacement, and failed delivery handling.
- Reporting fields for finance and reconciliation.
- Rate limits, error codes, and operational status pages.
- How supplier, brand, denomination, country, and currency data is represented.
Authentication and environments
Runa documentation describes API key authentication using an X-Api-Key header and separates production from a playground environment. It also references API versioning and execution modes. That is helpful for teams that need controlled testing before real payouts.
Tillo documentation and help materials refer to sandbox credentials through onboarding. That may be perfectly normal for a B2B provider, but it means buyers should clarify how quickly developers can access test data, issue test orders, and validate brand-level constraints.
Tremendous documentation describes sandbox and production base URLs, bearer token authentication, and a quick developer path. For teams that want engineers to test quickly, that is a useful advantage.
The practical question is not only “is there a sandbox?” It is whether the sandbox includes the product states, failures, currencies, delivery methods, and reporting outputs your team needs to test.
Catalogue and product management
Gift card APIs are only as useful as the product data behind them. A B2B team should understand how each provider represents brands, countries, denominations, currencies, delivery methods, expiry rules, redemption details, and restrictions.
Tillo appears particularly catalogue-oriented in its public materials, with brand details, denomination types, delivery methods, transaction types, and product information described as important parts of the operating workflow.
Runa and Tremendous also provide product or payout selection concepts, but buyers should check whether the catalogue data is detailed enough for their use case: ecommerce display, country filtering, denomination validation, user choice, accounting, and support documentation.
If gift cards are sold or distributed through an ecommerce flow, catalogue data quality becomes especially important. Incorrect denomination rules, missing redemption instructions, or unavailable brands can create checkout problems and support tickets.
Order creation and fulfilment workflow
All three providers support API-based order or reward creation, but the workflow models differ.
Runa documentation references order creation through /order, payment method selection, payout links, product selection, idempotency keys, and sync or async execution. This points to infrastructure-style controls that matter when preventing duplicate orders and handling execution states.
Tillo documentation examples focus on issuing digital codes with fields such as client request ID, brand, face value, delivery method, and fulfilment responsibility. That is relevant for teams managing brand-specific gift card issuance and supplier-like workflows.
Tremendous documentation describes creating orders with funding source, reward value, delivery method, recipient, campaign, and product selection. That is useful for reward programs where recipient delivery and campaign settings are part of the operating model.
The main implementation question is how each provider handles the messy cases: duplicate requests, pending orders, failed delivery, product unavailability, cancellation, refund, replacement, and reconciliation.
Reporting and reconciliation
This is where many gift card API projects become operationally difficult. A demo can show successful reward delivery, but finance needs clean data later.
Before choosing a provider, ask:
- Can we export order-level reports with internal references?
- Can every supplier transaction be matched to an internal order, campaign, customer, or cost center?
- Are failed, cancelled, refunded, and replaced rewards clearly marked?
- Can we track supplier balance, funding source, invoice, or wallet movements?
- Is redemption or remaining balance data available where needed?
- Can reports be pulled by API, dashboard, or scheduled export?
For Glavrio clients, this is often the real decision point. The best API is not only the one that sends a reward. It is the one that supports the reporting and reconciliation model the business needs after the reward is sent.
Which provider fits which use case?
Choose Runa-style infrastructure when:
- Your program is closer to payouts than only gift card issuance.
- You need multiple digital value formats.
- You care about idempotency, execution mode, and payout workflow controls.
- You want a unified payout layer for different reward or incentive use cases.
Choose Tillo-style infrastructure when:
- Gift card catalogue operations are central.
- Brand availability, countries, currencies, denominations, and delivery methods need close management.
- Your team needs strong supplier and product detail workflows.
- You are building gift-card-led experiences and need to validate brand-level constraints.
Choose Tremendous-style infrastructure when:
- You want a reward and payout API with accessible developer onboarding.
- Campaigns, recipients, product choice, and delivery experience are central.
- You need a fast path for incentives, research rewards, employee rewards, or customer payouts.
- Client libraries and public sandbox testing are important to your engineering team.
The hidden work: operating model before API selection
Many companies compare APIs too early. They review endpoints before defining the operational model. That leads to avoidable gaps later.
Before choosing Runa, Tillo, Tremendous, or another provider, define:
- Who owns supplier selection and commercial terms.
- Which countries, currencies, and brands are required.
- Whether recipients should receive a fixed brand, a choice link, or multiple payout options.
- Whether stock is pre-purchased, ordered in real time, or funded from account balance.
- What happens when a reward fails, expires, or needs replacement.
- What data finance needs for monthly reconciliation.
- What reporting is needed for management, customer support, and operations.
- Whether your existing ecommerce, loyalty, HR, CRM, or internal system needs API integration.
This work often determines the right vendor more than the first API call does.
How Glavrio can help
Glavrio helps companies evaluate gift card APIs, reward platforms, supplier workflows, ecommerce flows, reporting, reconciliation, and platform-enabled operations.
For a Runa vs Tillo vs Tremendous evaluation, Glavrio can help:
- Translate business requirements into API and operating requirements.
- Review public and private API documentation.
- Define supplier, catalogue, stock, order, and reporting workflows.
- Compare fulfilment, delivery, refund, and reconciliation models.
- Prepare questions for vendor calls and sandbox testing.
- Support implementation planning around UCP or other partner workflows where relevant.
The goal is not to choose the most popular API. The goal is to choose the setup that your finance, operations, ecommerce, and product teams can actually run.
FAQ: Runa vs Tillo vs Tremendous API
Is Runa, Tillo or Tremendous best for gift card APIs?
There is no universal best option. Runa may fit payout infrastructure use cases, Tillo may fit catalogue-led gift card management, and Tremendous may fit reward and payout programs with fast developer onboarding. The right choice depends on your countries, suppliers, stock model, reporting needs, and integration flow.
What should B2B teams compare first?
Start with catalogue requirements, order workflow, failure handling, reporting, reconciliation, funding, and recipient experience. Endpoint names matter, but operating fit matters more.
Do these APIs replace supplier management?
Not completely. An API can simplify ordering and fulfilment, but teams still need supplier governance, catalogue rules, finance controls, exception handling, and reporting processes.
Can Glavrio help compare gift card API providers?
Yes. Glavrio can help review requirements, compare API documentation, prepare vendor questions, design workflows, and support implementation planning. Contact Glavrio to discuss your gift card API evaluation.