/v1/me is the buyer's own view of their commerce data. Every endpoint here is authorized by a customer session secret, and the identity in that credential decides whose data is returned.
There is no customer_id argument anywhere in this namespace. A customer_id in the query string, or nested anywhere in the request body, is rejected with ME_CUSTOMER_ID_FORBIDDEN rather than ignored. A resource that exists but belongs to another buyer returns 404, not 403, so the namespace does not confirm that someone else's order ID is real.
Use this when you build your own account UI. Flint keeps enforcing access on the server, so a bug in your front end cannot show one buyer another buyer's order.
What the buyer can do#
| Job | Endpoints |
|---|---|
| Profile and email | GET/PATCH /v1/me, email change request and confirm |
| Email preferences | Get and update the optional email categories the buyer's address receives |
| Orders | Orders, order activity, receipt resend |
| Money | Payments, refunds |
| Gift cards | Save with possession proof, list, get balance, list anonymous history, remove saved access |
| Delivery | Fulfillments, shipments, packages |
| Invoices | List, get, PDF, and a checkout session to pay one |
| Subscriptions | List, get, pause, resume, cancel, reactivate, change payment method, start and get a payment retry |
| Saved payment methods | List, get, add, remove, set default |
| Addresses | List, create, get, update, delete, set default |
| Returns | Eligibility check, create, get, cancel, POST /v1/me/return-resolutions/{return_resolution_id}/checkout-session |
| Account closure | Request deletion, list requests, get one request's status |
A narrowed projection, not an alias#
These are not the merchant endpoints with a filter applied. Reads are trimmed to what a buyer should see, and writes are limited to what a buyer should be able to do to their own account.
Returns are the clearest case: a Return read through a customer session carries a narrower supported_actions and completion_blockers than the same Return read with a merchant key, because a buyer cannot receive, inspect, or approve their own Return. See self-serve Returns.
expand is not available here. Subscription reads include subscription_plan without it: the plan's current summary, or null for a subscription created without a plan.
Writes that move money#
Paying an invoice and paying a Return resolution both go through a checkout session rather than a direct charge. The buyer's own account never carries payment authority, and Flint's hosted payment surface handles the card. This is the same for a merchant-hosted account as for Flint's.
Gift card access follows possession#
Saved gift cards use the full customer session to identify the buyer's collection, and a current gift card code or private recipient link to prove access. Saving does not confer exclusive ownership or checkout spending authority. Several buyers can save one card, and each sees its balance and anonymous history. The full code, other holders' identities, and merchant provenance stay private. Replacing a code invalidates saved access until fresh proof is provided.