Customer account

The customer account API at /client-data/* is the surface a customer portal calls. It covers profile, addresses, payment methods, support tickets, messages, push notifications, wishlist, and the dashboard rollup. Every call is scoped to the authenticated customer — there's no way to read or write another customer's data through this API.

Dashboard

dashboard returns a curated rollup: counts of orders, pending tickets, unread messages, wallet balance, recent activity. Use it to populate a customer portal landing page in one round-trip. all returns the full bundle — every collection the customer has data in. Heavier, used on first sign-in or when refreshing local cache.

Profile

Standard profile fields (name, phone, language, timezone, about). The PUT accepts a partial — send only fields you're changing.

Verification

Email and phone verification flows. send issues a code; verify confirms it. Status returns the current verification state for both.

Orders

Paginated. Filter by status, sort by any field, and the response always returns the customer's own orders only — there's no cross-customer view.

Payment methods

Stripe-tokenised cards (and PayPal billing agreements). The POST accepts a Stripe paymentMethodId (created client-side via Stripe Elements); the platform attaches it to the customer's Stripe Customer object and stores a reference. The full card number never touches AppEngine.

// after createPaymentMethod() with Stripe Elements
await fetch('/api/client-data/payment-methods', {
  method: 'POST',
  headers: { orgid: ORG_ID, Authorization: `Bearer ${customerJwt}` },
  body: JSON.stringify({
    paymentMethodId: 'pm_abc',
    setAsDefault: true,
  }),
});

Addresses

autocomplete uses Google Places (configured via the integrations module) for typeahead. The POST upserts — if the body contains an id, that record is updated; otherwise a new address is created.

Tickets

Customer-side ticket creation and lookup. The staff side lives in CRM tickets. Customers can attach files via with-attachments (multipart upload).

Messages and conversations

Direct messages between the customer and staff (or experts). conversations returns distinct threads; messages returns messages within a thread, paginated. Status updates (read, archived) are per-message.

Notifications and push

Notifications are in-app messages. Push tokens are FCM/APNS device tokens registered for mobile push. The platform broadcasts notifications to the right channels via the Sync notification processor.

Wishlist

Per-customer saved-products list. Used by the storefront UI for the heart icon on product cards.

Reservations

Customer-side reservation booking — picks slots, books, modifies, cancels. Same machinery as the staff reservations endpoints, scoped to the customer.

Files

Per-customer file storage. Used for ticket attachments, profile photos, ID uploads. Files live under the customer's namespace in S3 (or the configured object store).

Benefits

Customer-side enrollment in benefit programmes (student discount, military, AAA, employer). Pricing automatically applies the benefit at checkout once approved.

Transactions

Filter by status, payment method, date range. Returns the customer's own transactions only. For wallet and payout-side transactions, see Customer finance and wallet.