Original Incomm API vs Fluz API Adapter
Base URL
- Original Incomm API: https://app.giftango.com
- Fluz API Adapter:
- Staging: https://api-adapter.staging.fluzapp.com/incomm
- Production: https://api-adapter.fluzapp.com/incomm
Original Incomm
- Uses Bearer Authentication with the Authorization header - need to generate authorization token first.
/auth/token endpoint with body:
Fluz API Adapter
- Uses Basic Authentication with the
Authorizationheader (same as all vendor integrations).
API Endpoint Comparison
Request Examples
Create Order
Original Incomm Request:
Fluz API Adapter Request:
DeliverEmail must not be true, because Fluz returns the gift card credentials in the order response rather than emailing the recipient, which keeps delivery under your control. PurchaseOrderNumber and CustomerOrderId are kept for compatibility with your existing request shape; correlate an order using the identifiers Fluz returns.
Response timing
Create order is synchronous, always running to completion. The call does not return until the purchase has finished, which can take up to 150 seconds, so set your client’s read timeout above that.Order status values are Fluz’s, not Incomm’s.
OrderStatus returns PENDING, IN_PROGRESS, COMPLETED, FAILED, or CANCELED. See Connector behaviour for status values, error responses, limits, and request constraints.