A practical checklist for reseller API orders

Keep your API key private

The reseller API uses the key associated with your account. Treat it like a password: do not place it in public pages, screenshots or shared browser code. Calls from your own application should be made from a secure server.

Read the API documentation for the endpoint, available actions and request fields. The API and website use the same account balance.

Validate before submitting

Fetch the current service list and check the service ID, supported quantity range and required link. Submit a positive whole quantity. Names can change, so use the service ID rather than matching names in your application.

Check balance and expected charge before sending an add request. A real order can spend money; a test should never be assumed free.

Record the result and avoid duplicates

Store the returned order ID immediately. Use that ID for later status checks, refill requests or cancellation where supported. If an upstream request has an uncertain outcome, do not blindly resend it: review the account order history first.

An accepted cancellation request is not necessarily a completed refund. Read the final order status and balance rather than assuming success from a single request.

Prepare for service changes

Refresh the catalog periodically, handle unavailable services and keep your users informed about delivery conditions. Do not expose supplier credentials or promise delivery guarantees beyond the selected service listing.