Product purchase flow
This guide describes how to purchase products through the Glofox API using a cart-based flow.
When a user purchases a membership, they use a single RESTful endpoint, as described in Payment collector. Product purchases follow a structured multi-step flow: list products, create a cart, then check out.
API flow overview
The flow uses standard HTTP methods and resource-based URLs. It consists of three sequential steps, each with its own endpoint:
- Get products—Retrieve available products for a specific location.
- Create cart—Initialize a cart with selected products and payment method; the response includes a price breakdown.
- Checkout cart—Finalize the cart, trigger payment, and generate an invoice.
API flow details
| Step | Method | Endpoint | API reference |
|---|---|---|---|
| Get products | GET |
/v3.0/locations/{location_id}/products |
Get products |
| Create cart | POST |
/v3.0/carts |
Create cart |
| Checkout cart | POST |
/v3.0/carts/{cart_id}/checkout |
Checkout cart |
The diagram below illustrates the sequential steps in the product purchase flow.
Cart ownership and checkout authorization
A cart is always tied to the authenticated user who created it. Only that user can check out that cart.
Authentication for these calls uses the x-glofox-impersonated-member-id request header to identify the member the operation is for. That prevents one user from checking out another user’s cart.
Glofox API endpoints already support this header. It's used in other flows such as Book and in cart pre-checkout for membership price breakdown, as described in Payment collector.
Restrictions
- No mixed purchases: You can't combine product and membership in a single cart transaction. For example, buying a product and a membership together isn't supported.
- Consistent payment processing: These cart endpoints use the same payment processing stack as the existing purchase flows elsewhere in the API.
Final notes
Follow the cart-based sequence and the authentication rules so that checkout stays consistent and secure. For request and response shapes, use the OpenAPI specification in the Swagger section of this portal, or contact Glofox API support if you need help.