Updated 20 October 2026. This policy applies to ADSWAR API integrators and buyers who resell products. Read it together with the API documentation, product conditions and company policies. Use only the services and permissions enabled for your account.
Before accepting orders
- Read the documentation for the API version in use, check permissions and store API keys securely. Never put them in web pages visitors can read.
- Check the product code, model, data format, price, minimum quantity and stock before ordering. Your storefront descriptions should match the features actually sold.
- Check your balance and set alerts for insufficient funds. Do not promise a successful order before checking the actual result.
- Record both your shop's order reference and the code returned by ADSWAR so the same transaction can be tracked.
Statuses that must be distinguished
Receiving an order code, successful payment and complete delivery are separate steps. Read the values defined by the API documentation and count only data sets actually delivered. For partial delivery, show the quantity received and still missing. Do not mark an order complete simply because the HTTP request received a response.
If funds are insufficient, stock is unavailable, required request data is missing or delivery cannot be completed, notify your own system administrator immediately and retain the reason and reference codes for resolution. If processing is ongoing, show the actual status instead of returning empty data or claiming full delivery.
Preventing duplicate orders and charges
A timeout, dropped connection or missing response does not establish that an order failed. Check its status and references before placing a new order. The current documentation explains using Idempotency-Key or client_order_id for supported requests. Follow each endpoint's format and scope; do not assume every request supports the same mechanism.
The integration should lock repeat submissions for the same transaction while awaiting a result and retain the mapping between order references. If you still cannot identify the transaction, contact our team for a check before buying again. Changing the reference to resubmit may cause the system to treat the request as a new order.
Partial delivery and refunds
Use status information from order_status.php and delivery_status as documented, distinguishing waiting, partial delivery, complete delivery, canceled, refunded and awaiting review. For incomplete delivery, record the ordered quantity, quantity received and deducted amount. Keep delivered sets separate from the part under review. Do not reorder the entire quantity without checking the original transaction, as this may cause overbuying and duplicate delivery.
Additional delivery, cancellation or a refund of the difference is assessed against the status and evidence, including the refund policy. We do not promise that every error will trigger an automatic refund or should be retried immediately.
Details shown to your customers
Resellers must accurately describe the products and warranty coverage they sell. Do not add promises of indefinite use, guaranteed advertising approval or claims accepted in every case without such an agreement. Your retail prices and additional conditions do not automatically change the conditions of an ADSWAR order and must not reduce your customers' statutory rights.
How to report an issue we can investigate
Contact ADSWAR with the system order code, your shop reference, product code, quantity, time, amount paid and status message with confidential information removed. If you attach a request or response, hide API keys, passwords, cookies and tokens. Never send keys through public channels.
API use must comply with the terms of service and applicable laws, particularly your rights to access customer information, storage of delivery data and avoiding access to transactions you are not authorized to view. This version takes effect upon publication on 20 October 2026 without reducing rights under existing order conditions.
Last updated: 10/20/2026