Home / API

API access designed around your own MaProxy data layer

Customers authenticate to your site, spend from your own wallet system, and receive MaProxy order records while supplier API calls stay on the server.

Customer-facing model

What the portal exposes

MaProxy account authentication for each customer
MaProxy wallet balance stored in your own data store
MaProxy order history scoped to the signed-in user
MaProxy-side fulfillment status after supplier handoff

Server-side model

What stays hidden

Supplier API key and supplier base URI details
Supplier master-account balance and payment methods
Unrelated supplier orders and IP inventory from other customers
Supplier auth / whitelist objects that do not belong to the signed-in MaProxy user

Order lifecycle

The billing and ownership boundary now sits at the MaProxy layer.

1. Customer signs up on your MaProxy site
2. Customer wallet balance is stored in your own database
3. Customer creates a MaProxy order
4. MaProxy wallet is charged first
5. Server sends the supplier order using your supplier API key
6. MaProxy stores the mapping between local order and supplier order
7. Customer sees only MaProxy order data in the portal

Recommended endpoint groups

Expose your own stable MaProxy API and keep the supplier API behind it.

Accounts: sign in, profile, MaProxy wallet balance
Checkout: quote a product, create a MaProxy order, inspect order state
Orders: list only the current customer's MaProxy orders
Fulfillment: show mapped IP or credential data only for the current customer order
Billing: expose MaProxy wallet ledger rows instead of supplier account funding details