Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help-loyalife.xoxoday.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Why Idempotency Matters

Network timeouts and ambiguous responses are unavoidable. Without idempotency, retrying a failed request can result in the same transaction being processed twice — awarding duplicate loyalty points. Loyalife’s transaction APIs support client-controlled idempotency via the _xoxo_api_client_idempotency field.

​
How It Works

{
  "_xoxo_api_client_idempotency": "order-invoice-2026-00123",
  "transaction_id": "TXN-2026-00123",
  "amount": 500,
  ...
}
  • Generate once per logical submission — use an ID tied to the business event (e.g. purchase order ID, invoice ID, or a UUID you generate once for each intended processing attempt).
  • Reuse on retries — if the first submission times out or returns an ambiguous response, retry with the same _xoxo_api_client_idempotency. The platform will recognise the duplicate and not process it twice.
  • Generate a new ID for new submissions — only generate a new _xoxo_api_client_idempotency when you genuinely intend a new business transaction.

​
transaction_id vs _xoxo_api_client_idempotency

FieldEnforced as unique by LBMS?Purpose
transaction_idNoYour business identifier for the row — used for your own reconciliation.
_xoxo_api_client_idempotencyProgram-dependentSafe retry key — prevents double-processing on retries.
LBMS does not enforce global uniqueness on transaction_id. If your processes require uniqueness, enforce it on your side. Confirm with your Xoxoday implementation contact whether _xoxo_api_client_idempotency is mapped to a unique column in your program configuration.

​
Integration Checklist

1

Generate an idempotency key

Create a stable, unique key per logical business request — e.g. the purchase order ID.
2

Submit the transaction

Include _xoxo_api_client_idempotency in the request body.
3

On timeout or ambiguous response, retry

Reuse the same _xoxo_api_client_idempotency. Do not generate a new one.
4

On confirmed success or failure, move on

Use Poll Batch Status to confirm the outcome of a V2 batch submission.