Build with the AlwaysCompleted API

Connect AlwaysCompleted to your server-side workflow to retrieve services, place orders and follow their progress. This guide takes you from your first read-only request to the checks that matter when creating orders. Keep the API reference open for the complete parameter lists and response examples.

Get ready to connect

1. Create an account and use your account’s API key in your server-side configuration.
2. Read the service catalogue and the terms of the services you plan to offer. Requirements, available options and order limits depend on the selected service.
3. Send requests from your own backend over HTTPS. Keep normal TLS certificate verification enabled.
4. Store the API key securely on your server. Keep it out of public pages, browser JavaScript, screenshots and shared code examples.

Make your first read-only request

The documented endpoint accepts POST requests and returns JSON. The official request example uses URL-encoded form parameters. Every action includes your API key and an action name.

POST https://alwayscompleted.com/api/v2

key=YOUR_API_KEY&action=services

Replace the placeholder only in your server-side configuration. The services action reads the catalogue; it does not create an order. Use its response to identify service IDs and inspect the available fields before building your order form.

Use current service and account information

The service list documents each service’s name, type, category, rate, minimum and maximum quantity, plus refill and cancellation indicators. Match the chosen service ID to its current description and requirements. Use the returned data when preparing an order instead of copying illustrative IDs or prices from documentation examples.

Use action=balance to read your account balance and its currency. Treat example amounts in the reference as sample data. Your application should display the actual response and handle errors before continuing.

Create orders deliberately

To create an order, send action=add with the selected service ID and the fields required for that service type. A Default order uses link and quantity; other types have different parameters. Check the matching section of the reference before submitting.

When creation succeeds, save the returned order ID alongside your own order record. If a request times out or its response is unclear, check the outcome before submitting it again. Blindly repeating an add request risks an unintended duplicate. Never use order creation as an automatic connection test.

Track orders and supported follow-up requests

Use action=status with order for one order, or orders with comma-separated IDs for a batch of up to 100. The documented response includes status, charge, start_count, remains and currency. Inspect each result: a batch can contain an error for an individual ID.

Refill and cancellation are requests subject to availability and the selected service’s conditions. Use action=refill to request a refill, action=refill_status to follow it and action=cancel to request cancellation. The documented batch variants accept up to 100 IDs. Submitting a request does not guarantee that a refill or cancellation will be approved.

Continue your integration

Use the full API reference for exact action parameters and examples. If you are building a customer-facing service workflow, see AlwaysCompleted for resellers. Review the Terms & Policy alongside each service’s description before accepting customer orders.