Get purchases for your organization
Retrieve all purchase records for your organization with powerful filtering options.
What is a purchase? A purchase represents a transaction where a trader bought an evaluation plan or funded account from your organization. Each purchase is linked to one or more trading accounts.
What you get:
- Purchase details (date, price, currency, status)
- The trading plan that was purchased
- All trading accounts created from this purchase
- Custom metadata you’ve added (any JSON data)
Filtering & Search:
| Parameter | Description | Example |
|---|---|---|
status | Filter by purchase status | ?status=paid |
metadata | Filter by metadata key:value | ?metadata=promoCode:SUMMER25 |
search | Search in metadata (text) | ?search=stripe_pi_123 |
startDate | Purchases from this date | ?startDate=2025-01-01 |
endDate | Purchases until this date | ?endDate=2025-01-31 |
Pagination:
Results are paginated. Use limit and offset to navigate through large datasets.
Example queries:
# Get all paid purchases
GET /organization/purchases?status=paid
# Get purchases with a specific promo code from January 2025
GET /organization/purchases?metadata=promoCode:SUMMER25&startDate=2025-01-01&endDate=2025-01-31
# Search for a specific transaction
GET /organization/purchases?search=stripe_pi_3ABC123
# Page 2 with 25 results per page
GET /organization/purchases?limit=25&offset=25
Use cases:
- Generate revenue reports
- Track refunds and chargebacks
- Find purchases by a specific trader
- Audit purchase history for compliance
Authorizations
JWT Bearer token for user session auth. Format: "Bearer {token}". Used by User and Organization endpoints.
Query Parameters
Filter by purchase status (pending, paid, refunded, cancelled)
pending, paid, refunded, cancelled Filter by metadata key:value (e.g., "refunded:true", "campaign:affiliate")
Search in metadata notes (partial match)
Only include purchases from this date onwards
Only include purchases up to this date
Results per page (default: 50, max: 100)
1 <= x <= 100Skip this many results (for pagination)
x >= 0Cursor for pagination. Pass the nextCursor value from the previous response to get the next page. When using cursor, do not send offset — it will be ignored.
How it works: The cursor is an opaque string that points to the last item you received. The server uses it to efficiently fetch the next set of results without scanning previous pages.
Backwards compatible: If you don't send a cursor, offset/limit pagination works as before.
Sort results. Format: field:direction where direction is asc or desc.
Allowed fields: created_at, purchase_date, price_paid, status
Default: created_at:desc
Examples: created_at:asc, current_balance:desc
Related topics
Get trading accounts for your organizationGet your organization profileGet traders for your organizationGet trading plans for your organizationGet team members for your organization