- API Reference
- ProxyMarket API
- Webhooks
A customer paid, deliver their proxy or VPN
ProxyMarket calls this the moment a customer's payment clears. Check X-Signature, find your product by external_plan_id, create the customer's access, and answer one of three ways:
- provisioned (best): put the proxy login, or
vpn_config_file, in the answer. The customer sees it at once. - pending: you need more time. Then send it with Deliver the proxy login or VPN config within 5 minutes.
- error: you cannot deliver, with a
message. ProxyMarket refunds the customer automatically and takes back your earning.
Save order_id: later calls about this order use it. The payload is the same for proxy, VPN and VLESS orders.
/provisionHeader parameters
Which event this call is.
order.provisionRequest body application/json · required
ProxyMarket order ID. Keep it: credentials, expiry and the other webhooks use it.
The external_id you synced. It tells you which port, modem or VPN pool to use.
ProxyMarket customer ID, for your own records. The customer never sees it.
How many were ordered (usually 1).
How long the customer paid for, in days, or hours when duration_unit is hours.
days, hoursData limit in GB. null means unlimited.
Name of the plan.
What the customer paid.
When the payment cleared (UTC).
Authentication
Check X-Signature before anything else; answer 401 when it does not match. See the guide for code.
Responses
Your answer. status is provisioned, pending or error; with provisioned, include the proxy login (all four fields) or vpn_config_file.
provisioned, pending, errorFull client file for VPN and VLESS orders.
When access ends on your side.
With status error, why you cannot deliver.
X-Signature did not match. ProxyMarket did not send this, or the body was changed.