Original Runa API vs Fluz API Adapter
Base URL
- Original Runa API: https://playground.runa.io
- Fluz API Adapter:
- Staging: https://api-adapter.staging.fluzapp.com/runa
- Production: https://api-adapter.fluzapp.com/runa
Authentication
Runa Base URL- Uses API Key Authentication with the header
X-Api-Key
Fluz API Adapter
- Uses Basic Authentication with the
Authorizationheader (same as all vendor integrations).
API Endpoint Comparison
Request Examples
Create Order
Original Runa Request:
Fluz API Adapter Request:
products.value has to change, because it is resolved against the Fluz catalog. Correlate an order using the id from the response.
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
- Best for testing and low-volume flows, since the call stays open for the length of the purchase
- 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, since your call returns immediately regardless of how long the purchase takes
An order is readable once its purchase has completed. Reading a reference ID before then returns an error rather than a pending status, so treat an error on a freshly created order as still processing and read again shortly. Order status values are Fluz’s:
PENDING, IN_PROGRESS, COMPLETED, FAILED, CANCELED. See Connector behaviour for status values, error responses, limits, and request constraints.