You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+57-57Lines changed: 57 additions & 57 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,16 +3,16 @@
3
3
4
4
## Introduction
5
5
6
-
Maxio Advanced Billing (formerly Chargify) provides an HTTP-based API that conforms to the principles of REST.
7
-
One of the many reasons to use Advanced Billing is the immense feature set and surrounding community [client libraries](page:development-tools/client-libraries).
6
+
Maxio Advanced Billing (formerly Chargify) provides an HTTP-based API that conforms to the principles of REST.
7
+
One of the many reasons to use Advanced Billing is the immense feature set and surrounding community [client libraries](page:development-tools/client-libraries).
8
8
The Maxio API returns JSON responses as the primary and recommended format, but XML is also provided as a backwards compatible option for Merchants who require it.
9
9
10
10
### Steps to make your first Maxio Advanced Billing API call
11
11
12
-
1.[Sign-up](https://app.chargify.com/signup/maxio-billing-sandbox) or [log-in](https://app.chargify.com/login.html) to your [test site](https://maxio-chargify.zendesk.com/hc/en-us/articles/5405553861773-Testing-Intro) account.
13
-
2.[Setup and configure authentication](https://maxio-chargify.zendesk.com/hc/en-us/articles/5405281550477-API-Keys#api) credentials.
14
-
3. Submit your API request and try it out.
15
-
4. Verify results through response.
12
+
1.[Sign-up](https://app.chargify.com/signup/maxio-billing-sandbox) or [log-in](https://app.chargify.com/login.html) to your [test site](https://maxio-chargify.zendesk.com/hc/en-us/articles/5405553861773-Testing-Intro) account.
13
+
2.[Setup and configure authentication](https://maxio-chargify.zendesk.com/hc/en-us/articles/5405281550477-API-Keys#api) credentials.
14
+
3. Submit your API request and try it out.
15
+
4. Verify results through response.
16
16
5. Test our integrations.
17
17
18
18
We strongly suggest exploring the developer portal, our [integrations](https://www.maxio.com/integrations) and the API guide, as well as the entire set of application-based documentation to aid in your discovery of the product.
@@ -37,11 +37,11 @@ The following section explains how to use the advancedbilling library in a new p
37
37
38
38
To use the package in your application, you can install the package from [pkg.go.dev](https://pkg.go.dev/) using the following command:
39
39
40
-
```bash
41
-
$ go get github.com/maxio-com/ab-golang-sdk@v0.1.0
40
+
```bash
41
+
$ go get github.com/maxio-com/ab-golang-sdk@v3.0.0
42
42
```
43
43
44
-
You can also view the package at: https://pkg.go.dev/github.com/maxio-com/ab-golang-sdk@v0.1.0
44
+
You can also view the package at: https://pkg.go.dev/github.com/maxio-com/ab-golang-sdk@v3.0.0
45
45
46
46
## Initialize the API Client
47
47
@@ -60,21 +60,21 @@ The following parameters are configurable for the API Client:
// That said, regeneration of the invoice may be forced with the params `force: true`, which will void an advance invoice if one exists and generate a new one. If no advance invoice exists, a new one will be generated.
30
30
// We recommend using either the create or preview endpoints for proforma invoices to preview this advance invoice before using this endpoint to generate it.
"422": {TemplatedMessage: "HTTP Response Not OK. Status code: {$statusCode}. Response: '{$response.body}'.", Unmarshaller: errors.NewErrorListResponse},
"422": {TemplatedMessage: "HTTP Response Not OK. Status code: {$statusCode}. Response: '{$response.body}'.", Unmarshaller: errors.NewErrorListResponse},
// ReadAdvanceInvoice takes context, subscriptionId as parameters and
63
63
// returns an models.ApiResponse with models.Invoice data and
64
64
// an error if there was an issue with the request or response.
65
65
// Once an advance invoice has been generated for a subscription's upcoming renewal, it can be viewed through this endpoint. There can only be one advance invoice per subscription per billing cycle.
// VoidAdvanceInvoice takes context, subscriptionId, body as parameters and
@@ -94,31 +94,31 @@ func (a *AdvanceInvoiceController) ReadAdvanceInvoice(
94
94
// Void a subscription's existing advance invoice. Once voided, it can later be regenerated if desired.
95
95
// A `reason` is required in order to void, and the invoice must have an open status. Voiding will cause any prepayments and credits that were applied to the invoice to be returned to the subscription. For a full overview of the impact of voiding, please [see our help docs]($m/Invoice).
0 commit comments