Common workflows.

Practical request patterns for QR resolution, follow or unfollow, manual adjustments, and transaction reconciliation.

Sep 16, 2026

Use these requests to resolve links, save cards, correct points, and reconcile transactions.

Resolve a QR code or shared link

Use the member discover resolver when a member scans a QR code or opens a shared loyalty link.

POST /api/agent/v1/member/discover/resolve HTTP/1.1
Host: your-domain.com
Accept: application/json
Content-Type: application/json
X-Agent-Key: rl_member_A1b2C3d4E5f6G7h8I9j0K1l2M3n4O5p6Q7r8

{
  "url": "https://your-domain.com/en-us/card/3598a5db-f008-477c-ac4d-5365c662ad62"
}

Supported inputs:

card URLs
follow URLs
stamp-card URLs
voucher URLs
raw UUIDs
unique identifiers

If the resource is not live or discoverable, the API returns 404.

Save a card to "My Cards"

POST /api/agent/v1/member/discover/follow HTTP/1.1
Host: your-domain.com
Accept: application/json
Content-Type: application/json
X-Agent-Key: rl_member_A1b2C3d4E5f6G7h8I9j0K1l2M3n4O5p6Q7r8

{
  "card_id": "3598a5db-f008-477c-ac4d-5365c662ad62"
}

This operation is idempotent. Repeating the same follow request does not create duplicates.

Unfollow:

POST /api/agent/v1/member/discover/unfollow HTTP/1.1
Host: your-domain.com
Accept: application/json
Content-Type: application/json
X-Agent-Key: rl_member_A1b2C3d4E5f6G7h8I9j0K1l2M3n4O5p6Q7r8

{
  "card_id": "3598a5db-f008-477c-ac4d-5365c662ad62"
}

Manual points adjustment

When a support agent or partner system needs to grant points outside a real purchase, use the purchase endpoint with points and a reconciliation note.

POST /api/agent/v1/partner/transactions/purchase HTTP/1.1
Host: your-domain.com
Accept: application/json
Content-Type: application/json
X-Agent-Key: rl_agent_A1b2C3d4E5f6G7h8I9j0K1l2M3n4O5p6Q7r8S9t0

{
  "card_id": "3598a5db-f008-477c-ac4d-5365c662ad62",
  "member_identifier": "[email protected]",
  "points": 250,
  "note": "Support adjustment case #7843"
}

Reserve this for a one-off correction, and attach a note. This example has no source_reference: repeating it awards points again. After a timeout, reconcile the transaction before another attempt. For queued corrections, use the retry-safe purchase fields.

Reconcile transactions by date range

Use the partner transaction list with from and to in Y-m-d format.

GET /api/agent/v1/partner/transactions?from=2026-03-01&to=2026-03-08&[email protected]&per_page=100 HTTP/1.1
Host: your-domain.com
Accept: application/json
X-Agent-Key: rl_agent_A1b2C3d4E5f6G7h8I9j0K1l2M3n4O5p6Q7r8S9t0

Use this for:

end-of-day reconciliation
customer-support investigations
replay safety checks before retrying a purchase
external finance exports

Typical error branch

Missing input on resolve:

{
  "error": true,
  "code": "MISSING_INPUT",
  "message": "Provide a \"url\" or \"identifier\" parameter.",
  "retry_strategy": "fix_request"
}

Canonical names only

These workflows use the canonical request and response fields from the main reference pages.