Error Handling
Methods
- Account/Auth/
- Account/SSH/Key/
- Billing/Invoice/
- Billing/Payment/
- Cloud/Backup/
- Cloud/Config/
- Cloud/IP/Pool/
- Cloud/Image/
- Cloud/Server/
- Cloud/Template/
- Monitoring/Bandwidth/
- Monitoring/Load/
- Monitoring/Services/
- Network/DNS/Domain/
- Network/DNS/Record/
- Network/DNS/Reverse/
- Network/DNS/Zone/
- Network/Firewall/
- Network/Firewall/Ruleset/
- Network/IP/
- Network/LoadBalancer/
- Network/Pool/
- Network/Private/
- Network/Region/
- Network/Zone/
- Notifications/
- Order/AddOn/
- Product/
- Server/
- Server/VirtualDomain/
- Storage/Block/Cluster/
- Storage/Block/Volume/
- Support/Alert/
- Utilities/Info/
- VIP/
- VPN/
API Documentation (API Version v1)
Billing/Invoice/
DESCRIPTION
An invoice is a record of specific charges owed by the customer for a set of services. A bill is a point of communication with a customer. When Liquid Web bills a customer, it gathers any outstanding invoices, generates any new invoices if needed and sends them to the customer.
There are three ways an invoice could be generated:
-
Any time a service is added or removed from an account an invoice is generated.
-
During the normal billing time for an account, an invoice is generated for the upcoming month.
-
For certain services where it is impossible to know how much to charge until we know the usage for the service, we charge for the previous month's usage. If an account has charges for any of those services (backups, bandwidth overages, etc), an additional invoice will be generated for those services only.
**** NOTE ****
Bills related methods have been moved to billing->bill
In order to help clear up confusion, we have made an effort to separate bills and invoices. Originally, to try and make things simpler, we attempted to make bills and invoices appear more like one thing. This, unfortunately, did not work as well as intended. In making things more transparent, the API methods involving Bills and Invoices have been refined. In order to maintain backwards compatibility, the version 1 (v1) methods will continue to refer to bills rather than invoices. Moving forward, including the bleed version, the methods will be referring solely to invoices. This means that a list method called as v1 will return different data than the bleed version.
Exceptions to this rule: Any method that only existed as a bleed method prior to the separation of bills and invoices. These methods have been completely moved to billing->bill and are no longer available under billing->invoice.
details
URL:
https://api.liquidweb.com/v1/Billing/Invoice/details
Description:
Parameters:
Parameter | Type | Notes |
---|---|---|
id | A positive integer value (i.e. 1 and up). | * Required |
Returns:
Field | Type | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
accnt | A valid account number, up to 6 digits in length. The account number a given bill is associated with. | |||||||||||||||||||||||||||||||||||||
bill_date | A valid date in YYYY-MM-DD format. The date a given bill was created. | |||||||||||||||||||||||||||||||||||||
due | A monetary value, such as -$.05, 0.05, or -5.00 The amount remaining due on a given bill. | |||||||||||||||||||||||||||||||||||||
end_date | A valid date in YYYY-MM-DD format. The end date of a date range for a given bill covering all invoices associated with the bill. | |||||||||||||||||||||||||||||||||||||
id | A valid id number (a positive integer). The unique id of a given bill. | |||||||||||||||||||||||||||||||||||||
lineitem_groups | An array of associative arrays containing | |||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||
payments | An array of associative arrays containing An array containing a list of payments associated with a bill. Each element of the array is an associative array containing the following fields: | |||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||
start_date | A valid date in YYYY-MM-DD format. The start date of a date range for a given bill covering all invoices associated with the bill. | |||||||||||||||||||||||||||||||||||||
status | A single word, consisting of only letters, digits, hyphens, and underscores. The status of a given bill (new, authorized, voided, refuneded, etc). | |||||||||||||||||||||||||||||||||||||
total | A monetary value, such as -$.05, 0.05, or -5.00 The total amount a bill is for after summing all the invoices on it. | |||||||||||||||||||||||||||||||||||||
type | A single word, consisting of only letters and digits. Defines the payment method being used when a bill was created (ie, check or credit card). |
Possible Errors:
Refer to the Error Handling documentation for the list of exception types
list
URL:
https://api.liquidweb.com/v1/Billing/Invoice/list
Description:
v1
Deprecated. This method has been moved to billing->bill->list
Returns a list of all the bills for the logged in account. Bills are created at your regular billing date, but are also created for one-off items like creating or cloning a server.
bleed
Returns a list of all the invoices for the logged in account.
Parameters:
Parameter | Type | Notes |
---|---|---|
page_num | A positive integer value (i.e. 1 and up). | * Optional
|
page_size | A positive integer value (i.e. 1 and up). | * Optional
|
Returns:
Field | Type | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
item_count | A non-negative integer value (i.e. 0 and up). | ||||||||||||||||||||||||||||||||
item_total | A non-negative integer value (i.e. 0 and up). | ||||||||||||||||||||||||||||||||
items | An array of associative arrays containing | ||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||
page_num | A positive integer value (i.e. 1 and up). | ||||||||||||||||||||||||||||||||
page_size | A positive integer value (i.e. 1 and up). | ||||||||||||||||||||||||||||||||
page_total | A positive integer value (i.e. 1 and up). |
Possible Errors:
Refer to the Error Handling documentation for the list of exception types