OxifyOxify
Developer Reference

App proxy endpoints

Theme-side endpoints proxied through Shopify with the customer's session.

This article is a draft and may be incomplete or change before publishing.

Oxify exposes endpoints at /apps/iacart/* proxied through Shopify to the app server.

Why use them

Useful for theme-side fetches that need the customer's session — for example, building a custom storefront block that reads the customer's eligible reward tiers, or wiring a custom analytics ping that includes the cart contents.

What "proxied" means

The browser hits a URL on your storefront domain. Shopify forwards it to the Oxify backend with a signed verification header. Oxify trusts the header, knows it came from a real customer's session, and returns the data.

Endpoint patterns

The most common patterns:

  • /apps/iacart/cart-state — Current cart with reward eligibility.
  • /apps/iacart/funnels — Active post-purchase funnels for testing.
  • /apps/iacart/track — Custom event dispatch.

Authentication

The signed proxy header is automatic — your storefront-side fetch doesn't need to include credentials.

On this page