Skip to main content
This document provides specific details for using the Fluz Gift Card Vendor API Connector with Runa as the vendor.

Original Runa API vs Fluz API Adapter

Base URL

Authentication

Runa Base URL
  • Uses API Key Authentication with the header X-Api-Key

Fluz API Adapter

  • Uses Basic Authentication with the Authorization header (same as all vendor integrations).

API Endpoint Comparison

Request Examples

Create Order

Original Runa Request:

Fluz API Adapter Request:

Background Processing for Runa Orders

All purchase operations through the Runa integration are processed as background operations. The Fluz API Adapter provides two response modes for Runa:

Synchronous vs Asynchronous Processing Modes

  • Synchronous Mode:
    • Add header X-Execution-Mode: sync to wait for the background operation to complete
    • The API call will wait until the background purchase operation completes
    • Full operation results are returned in the response
    • Good for testing scenarios but may experience timeouts for complex purchases
  • Asynchronous Mode (Default):
    • Returns immediately with an operation reference ID
    • The purchase continues processing in the background
    • Check the status later by querying the order endpoint with the reference ID
    • Recommended for production to avoid timeouts
Both modes rely on background processing, but they differ in how the API responds to the client.

Idempotency Support

Both the original Runa API and Fluz’s implementation support idempotency keys to prevent duplicate operations:

Example Usage with cURL

Example 1: Get a Specific Order

Example 2: Get All Orders

Example 3: Get Balance for All Currencies

Example 4: Get Balance for USD Currency

Example 5: Create Order with Runa (Asynchronous Mode - Default)

Example 6: Create Order with Runa (Synchronous Mode)