Skip to main content

External REST API: Full Read/Write Access to Loyalty Data

Casa Loyalty now ships a full external REST API — 36 operations across 26 endpoints — bringing Casa to full parity with Smile.io and Rivo for partner and merchant integrations.

Written by Sam

Casa Loyalty now has a full external REST API, so partner platforms and merchant systems can read and write loyalty data programmatically instead of only through the admin dashboard and storefront widget. This brings Casa to full parity with Smile.io and Rivo's loyalty APIs.

Coverage: 36 operations across 26 endpoints

The API spans every core area of the loyalty program:

  • Customers

  • Points

  • Orders

  • Rewards

  • Redemptions

  • Referrals

  • VIP tiers

  • Activities

  • Program settings

  • Translations

Read and write, not just read

This isn't a read-only reporting layer — the API supports the same actions your team can take from the admin:

  • Create and update customers

  • Adjust points, either a single customer or in batch (up to 20 at once)

  • Process external orders for points — useful for POS or non-Shopify sales channels

  • Redeem rewards

  • Create, complete, or block referrals

  • Force a customer into a specific VIP tier

  • Manage rewards and translations

Granular permissions

Access is secured with resource:action scoped API-key permissions — for example customers:write or rewards:read — so a key can be limited to exactly what an integration needs. Existing generic API keys continue to work unchanged, so nothing breaks for current integrations.

Safety and admin parity

Every write goes through the same protections and side effects as actions taken in the admin:

  • FIFO-safe points accounting — batch and per-customer adjustments respect the same accounting rules as the dashboard.

  • Soft-deleted-customer protection — the API won't let you write against a customer record that's been soft-deleted.

  • Full admin-parity side effects — API actions trigger the same Klaviyo/platform events, customer emails, and VIP re-evaluation that the equivalent admin action would.

Pagination

All list endpoints use cursor-based pagination via since_id, so integrations can page through large customer, order, or activity datasets reliably without offset drift.

Where to find it

Full endpoint reference, request/response examples, and authentication details are in the developer docs: https://app.casaloyalty.io/docs/

Did this answer your question?