Chargebee provides HTTP based API which follows the essence of REST*.
The HTTP protocol's rules are followed thereby enabling simple HTTP client tools like "curl" to be used.
The following client libraries provide a "easy to use" wrapper around the raw HTTP based API.
If you require support for additional languages, please raise a ticket on our support page.
Sample Snippets
Use the language bar at the top to view code examples in your chosen language.
Want us to generate ready-to-test snippets?
Login to Chargebee and open the API docs from there and you'll find ready-to-test sample codes based on your Chargebee test site's api key and data.
Don't have an account with Chargebee yet? Signup now!.
Sample Apps
Explore our suite of sample applications, complete with tutorials to guide your integration with Chargebee.
Documentation
For in-depth explanations and definitions of all Chargebee components, consult our documentation.
Resources
Chargebee follows the REST model of exposing resources as urls. For example, subscriptions are exposed as
https://{site}.chargebee.com/api/v1/subscriptions
The Java client library provide a corresponding class representation of the resource. For example, subscriptions are represented by
com.chargebee.models.Subscription
Request
The client library exposes all operations specific to that resource as static methods in the corresponding resource class and they return a operation specific Request object. The "Request" objects expose a
fluent API using which you could set the
input parameters for the operation. After filling in the request parameters, invoke the request method to send the request. There is an additional overloaded request method that takes in environment configuration that is applied only for that request.
Response
The response is in JSON format.
Currently Chargebee does not support any other response format.
The com.chargebee.Result class wraps the response sent by the server. It has methods
that allow you to fetch the specific resource from the result.
The com.chargebee.ListResult class is used to wrap list responses.
Note: Sometimes, while working with Chargebee APIs, you may see undocumented attributes returned in the response. Such attributes should be ignored.
Sample Codes
import java.io.IOException;
import com.chargebee.*;
import com.chargebee.models.*;
import com.chargebee.models.enums.*;
public class Sample{
public static void main(String args[]) throws IOException{
/*
creates a subscription with customer information and billing details.
*/
Environment.configure("{site}","{site_api_key}");
Result result = Subscription.create()
.planId("no_trial")
.customerFirstName("John")
.customerLastName("Doe")
.customerEmail("john@user.com")
.billingAddressFirstName("John")
.billingAddressLastName("Doe")
.billingAddressLine1("PO Box 9999")
.billingAddressCity("Walnut")
.billingAddressState("California")
.billingAddressZip("91789")
.billingAddressCountry("US")
.customerAutoCollection(AutoCollection.OFF)
.request();
Subscription subscription = result.subscription();
Customer customer = result.customer();
Card card = result.card();
Invoice invoice = result.invoice();
System.out.println(result);
}
}
copy full code
/*
creates a subscription with customer information and billing details.
*/
Environment.configure("{site}","{site_api_key}");
Result result = Subscription.create()
.planId("no_trial")
.customerFirstName("John")
.customerLastName("Doe")
.customerEmail("john@user.com")
.billingAddressFirstName("John")
.billingAddressLastName("Doe")
.billingAddressLine1("PO Box 9999")
.billingAddressCity("Walnut")
.billingAddressState("California")
.billingAddressZip("91789")
.billingAddressCountry("US")
.customerAutoCollection(AutoCollection.OFF)
.request();
Subscription subscription = result.subscription();
Customer customer = result.customer();
Card card = result.card();
Invoice invoice = result.invoice();
copy snippet
/*
creates a subscription with customer information and billing details.
*/
Environment.configure("{site}","{site_api_key}");
Result result = Subscription.create()
.planId("no_trial")
.customerFirstName("John")
.customerLastName("Doe")
.customerEmail("john@user.com")
.billingAddressFirstName("John")
.billingAddressLastName("Doe")
.billingAddressLine1("PO Box 9999")
.billingAddressCity("Walnut")
.billingAddressState("California")
.billingAddressZip("91789")
.billingAddressCountry("US")
.customerAutoCollection(AutoCollection.OFF)
.request();
Subscription subscription = result.subscription();
Customer customer = result.customer();
Card card = result.card();
Invoice invoice = result.invoice();
Checkout our java client
repository
hosted at github. The jar is available under the /dist directory.
Source Code
The source code for the client library is available as a public repository
at github. The
code is provided with MIT license.
So in case you need any modifications please feel free to do so. If you
think it would be useful for other users please do let us know.
Newer versions of client library are released whenever there are new additions to the API. The version
numbering format is major-version.minor-version(s). All
minor releases are backward compatible. Please check the
change notes
for more details.
The latest version details for API V1 are:
Version: 1.1.80
Released On: 2019-08-27
OpenAPI Specification
As part of our commitment to enhance the developer experience, we're thrilled to introduce the Chargebee OpenAPI specification. It's the first step in a series of planned improvements.
The Chargebee OpenAPI specification is a version of our API spec that is fully compliant with the OpenAPI Specification v3.0.1. Stay tuned for more updates!
Code samples
The sample code snippets provided for the endpoints in this documentation are ready-to-test. Once you log in and select a test site using the dropdown that appears at the top, the code samples in this documentation automatically include your API key and site data.
API testing
Chargebee provides the Time Machine feature to help you test your integration. Once you've set up your billing configuration on the test site, you can simulate events on a hypothetical time frame to ensure everything works as expected. Ensure that you rigorously test your configuration before going live.