Commerce

Chargify API Integration

Codat’s new Chargify integration enables you to securely connect to, retrieve, and view your customers' recurring sales and subscription transactions

Chargify.com

Fast track your Chargify integration with our purpose-built products

Lending API

Get insight into financial health for smarter, more efficient lending.

Learn more

FAQs

What is Chargify?

Chargify is a subscription management and recurring billing platform, allowing businesses that offer subscription-based or recurring billing to manage their process via a single platform.

Why use Codat's Chargify integration?

Chargify is one of the leading subscription billing platforms for B2B SaaS companies. Codat’s Chargify integrations enable you to pull subscriptions and recurring billing data. This data can be used to power a wide variety of use cases, such as revenue-based lending, and financial management dashboards.

How do I get started using the Chargify integration?

Take a look at our docs to see how you can get started using Codat’s Chargify integration today.

Explore similar integrations

Market research

Find out more about the commerce data opportunity

Download our guide to connecting with eCommerce and Payments software to better understand Codat’s coverage and why commerce data is so valuable

Download report

Codat's guide to connecting with eCommerce and Payments software

Documentation

Visit our docs to learn about our Chargify integration

View docs

Roadmap

See what we’re building next and have your say

Visit roadmap

Cookie	Duration	Description
cookielawinfo-checkbox-analytics	1 year	This cookies is set by GDPR Cookie Consent WordPress Plugin. The cookie is used to remember the user consent for the cookies under the category "Analytics".
cookielawinfo-checkbox-necessary	1 year	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
viewed_cookie_policy	1 year	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.

Cookie	Duration	Description
lpv887333	30 minutes	No description
visitor_id887333	10 years	No description
visitor_id887333-hash	10 years	No description

Cookie	Duration	Description
_ga	2 years	This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
_gat_gtag_UA_89798244_1	1 minute	Google Analytics cookies are used to collect information about how Visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of Visitors to the site, where Visitors have come to the site from, and the pages they visited.
_gid	1 day	This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
_hjAbsoluteSessionInProgress	30 minutes	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
_hjFirstSeen	30 minutes	This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
_hjid	1 year	This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
_hjIncludedInPageviewSample	2 minutes	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.
_hjTLDTest	session	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
_lfa	2 years	This cookie is set by the provider Leadfeeder. This cookie is used for identifying the IP address of devices visiting the website. The cookie collects information such as IP addresses, time spent on website and page requests for the visits.This collected information is used for retargeting of multiple users routing from the same IP address.
pardot	past	The cookie is set when the visitor is logged in as a Pardot user.
vuid	2 years	This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.

Fast track your Chargify integration with our purpose-built products

Lending API

FAQs

What is Chargify?

Why use Codat's Chargify integration?

How do I get started using the Chargify integration?

Explore similar integrations

Chargebee

Recurly

Zettle by PayPal

Amazon Seller Central

Find out more about the commerce data opportunity

Documentation

Roadmap

Want to get started?