Sign In
Get a Demo

Chartbeat API
Terms of Service

Last updated: April 20, 2026

These API Terms of Service (the “API Terms”) govern access to and use of the application programming interfaces, related software, tools, documentation, data, materials, methods, and content provided by or on behalf of Chartbeat, Inc. and its affiliates, including Tubular Labs, Lineup Systems and FatTail (referred to collectively as “Chartbeat”) (each an “API,” and together, the “APIs”). These API Terms supplement and are incorporated into the applicable Chartbeat master terms, subscription terms, terms of service, or services agreement in respect of the particular Chartbeat entity and the customer identified in an applicable work order, order form or customer profile (“Customer,” and together with Chartbeat, the “Parties”) (the “Master Terms”). Capitalized terms used but not defined in these API Terms have the meanings given in the Master Terms.

By accessing or using any API, Customer agrees to these API Terms and the Master Terms. If Customer does not agree, Customer may not access or use any API.

  1. License and Scope. Subject to these API Terms and the Master Terms, Chartbeat grants to Customer a limited, revocable, non‑exclusive, non‑transferable license, without the right to sublicense, to access and use the APIs solely to build and operate Customer’s internal applications and systems for Customer’s internal business purposes. Customer may permit its affiliates and third‑party service providers to access and use the APIs solely on Customer’s behalf and for Customer’s benefit in accordance with these API Terms, provided that Customer remains responsible for their compliance.
  2. Credentials and Access. Chartbeat will issue one or more API credentials (for example, keys or tokens) to Customer. Customer must keep credentials secure and confidential, use them only server‑side, and prevent unauthorized access or disclosure. Credentials are personal to Customer and must not be shared outside Customer’s organization except as expressly permitted in Section 1. Customer must promptly notify Chartbeat of any suspected compromise and rotate credentials if instructed. Chartbeat may monitor API usage and may throttle, suspend, or revoke access for suspected abuse, security risk, or violation of these API Terms or the Master Terms.
  3. Acceptable Use and Restrictions. Customer must not, directly or indirectly, and must not authorize any third party to, do any of the following:  (i) build a product or service that replicates or competes with core Chartbeat or Tubular offerings; (ii) provide any time‑sharing, service bureau, outsourcing, or other access to the APIs or outputs for the benefit of third parties; (iii) circumvent or exceed published or communicated rate limits, quotas, concurrency controls, or usage thresholds; (iv) interfere with or disrupt the APIs or other users’ applications or data; reverse engineer, decompile, disassemble, or otherwise attempt to derive source code or underlying ideas or algorithms of any Chartbeat technology except to the extent such restriction is prohibited by applicable law; (v) copy, modify, distribute, or create derivative works of the APIs; (vi) remove or obscure proprietary notices; (vii) use the APIs with spyware, malware, or any malicious code; use the APIs to promote or distribute counterfeit goods, embargoed or illegal items, hate material, or unlicensed regulated products; or (viii) present data obtained from the APIs in a manner that suggests such data originates from any third‑party website or service rather than Chartbeat. 
  4. Third‑Party Content; Takedown. APIs may provide access to content owned by third parties (“Third‑Party Content”). Customer is solely responsible for complying with any applicable owner‑imposed requirements or restrictions on Third‑Party Content. If any owner requests removal of its Third‑Party Content from any Customer application or website using the APIs, Customer must remove it within twenty‑four (24) hours after receipt of the request. 
  5. Data Use; Redistribution; Caching and Deletion. Except as expressly permitted by Chartbeat in writing, Customer may use data, metrics, insights, analytics, or other outputs obtained via the APIs (“API Data”) only for internal business purposes and must not sell, rent, lease, sublicense, redistribute, or otherwise provide API Data to any third party. Customer is solely responsible for its API integrations and for obtaining and maintaining all necessary rights, consents, and approvals to use the APIs and any Third Party Content. If Chartbeat authorizes any public display or disclosure of API Data, Customer must provide conspicuous attribution as “Data provided by Tubular Labs” for Tubular‑sourced API Data or as Chartbeat designates for Chartbeat‑sourced API Data, and in digital media include a live link to the applicable Chartbeat website. Customer must refresh any API Data that it caches at least every twenty‑four hours. For any YouTube‑sourced data made available via the APIs, Customer must refresh such data at least every thirty (30) calendar days or delete such data after thirty (30) days if Customer does not refresh it, to conform to YouTube’s API requirements. Upon expiration or termination of Customer’s API access, Customer must delete all API Data within thirty (30) days and provide written confirmation of deletion to Chartbeat upon request.
  6. API Data Use Compliance.  Customer is solely responsible for its API integrations and for obtaining and maintaining all necessary rights, consents, and approvals to use the APIs and any Third‑Party Content.  In addition, Customer acknowledges that API Data may include content or data originating from third‑party platforms, publishers, or content distributors whose terms and policies (for example, developer, data, or API terms) may restrict or prohibit use of their content or data with artificial intelligence or machine learning technologies.  Customer is solely responsible for ensuring that its, and its service providers’, use of API Data complies with all such third‑party terms and policies.  Without limiting the foregoing, Customer must not use, and must not permit any third party to use, any API Data to train, fine‑tune, or otherwise improve any general‑purpose or specialized artificial intelligence or machine learning systems, models, or algorithms, or to create embeddings or derived datasets for such purposes, unless Customer has obtained Chartbeat’s prior written consent and all necessary rights, consents, and permissions from the applicable rightsholders and platforms, and Customer’s use fully complies with their then‑current terms.  For clarity, routine analytical processing of API Data within Customer’s systems to generate ephemeral insights for internal business purposes is permitted, provided that no API Data or derivative thereof is ingested into or used to update the weights or parameters of any artificial intelligence or machine learning model, and provided that Customer maintains reasonable technical and organizational controls to prevent upload of API Data to third‑party generative AI services absent the foregoing consents.  If Chartbeat or any third‑party platform notifies Customer that a particular use is non‑compliant, Customer will immediately cease the use, delete the affected data and any outputs or models derived from such use, and certify deletion upon request.  Customer will flow down the obligations in this paragraph in writing to any third‑party service providers engaged to process API Data on Customer’s behalf and remains responsible for their compliance.  Customer is responsible for complying with all applicable data protection, consumer protection, export control, and other laws and regulations in connection with Customer’s API usage.
  7. Customer Privacy Policy.  If Customer uses the APIs to process any end‑user data on any Customer website or application, Customer will publicly post a privacy policy describing its data collection, use, storage, and disclosure practices, including any disclosures required by applicable laws and platform policies (for example, disclosures that third parties may serve content or advertisements, collect information, and place or recognize cookies).  
  8. Security; Incidents. Customer must implement and maintain appropriate administrative, physical, and technical safeguards to protect API credentials, the APIs, and API Data. Customer must promptly report in writing any actual or suspected unauthorized access to or use, disclosure, alteration, or destruction of API Data or the APIs associated with Customer’s use, cooperate with Chartbeat to remediate any security deficiency, and immediately disconnect any intrusion. Customer and its users will not make any public statements regarding any such security incidents without Chartbeat’s prior written consent.
  9. Rate Limits, Quotas, and Quality Controls. Customer must comply with all published or communicated rate limits, quotas, concurrency controls, and quality‑of‑service constraints for the APIs. Current rate limits can be found here. Chartbeat may publish response headers indicating remaining request capacity. Chartbeat may throttle or suspend access to preserve service quality or investigate suspected misuse. Chartbeat may update product‑specific rate limits from time to time, which rate limits shall be incorporated into these API Terms.
  10. Fees and Commercial Use. Access to Chartbeat APIs is subject to fees as set forth in the Master Terms and any applicable order form or amendment, unless Chartbeat has expressly agreed in writing to provide such access at no additional charge.  Without limiting the foregoing, “commercial applications” or high‑rate usage, including applications where the primary purpose is to derive revenue, where Customer charges its users a fee for products or services that include integration using the Chartbeat API, where Customer sells services to Chartbeat users and uses the Chartbeat API to import such users’ content into Customer’s service, or where Customer operates a destination site that uses Chartbeat content or videos to drive traffic and generate advertising revenue, are always subject to applicable fees. Access to the Tubular APIs is fee‑based and priced according to expected usage, with limitations on requests per minute and daily quotas. Fees, invoicing, and payment terms are set forth in the Master Terms and any applicable order form. 
  11. Changes; Deprecation; Support. Chartbeat may modify, discontinue, or deprecate any API, feature, or attribute at any time. To the extent practicable, Chartbeat will endeavor to provide commercially reasonable advance notice of changes that materially and adversely affect backward compatibility, except where immediate changes are required for legal, regulatory, or security reasons. Chartbeat may publish changelogs and migration guidance where available. Unless otherwise specified in an order form, APIs are provided without service‑level commitments; any applicable service level agreement is governed by the Master Terms and product‑specific attachments. 
  12. Ownership; Feedback. Chartbeat and its licensors retain all right, title, and interest in and to the APIs, API Data (excluding Customer Data, if any, contributed by Customer into a Chartbeat product in accordance with the Master Terms), and all related intellectual property. No rights are granted by implication. If Customer provides any suggestions, ideas, or other feedback regarding the APIs (“Feedback”), Chartbeat may use and incorporate such Feedback without restriction and without any obligation to Customer.
  13. Indemnification. Customer will defend Chartbeat, its affiliates, and their respective officers, directors, employees, agents, licensors, and data providers from and against any third‑party claims, and will indemnify them for any resulting damages, liabilities, costs, and expenses (including reasonable attorneys’ fees), arising out of or related to Customer’s or its affiliates’ or contractors’ use of the APIs or API Data in violation of these API Terms, the Master Terms, or applicable law; Customer’s applications or content; or any alleged violation of third‑party rights by Customer’s applications or content. 
  14. Disclaimers. EXCEPT AS EXPRESSLY PROVIDED IN THE MASTER TERMS, THE APIS, API DATA, ANY THIRD‑PARTY CONTENT, AND ANY RELATED SOFTWARE OR MATERIALS ARE PROVIDED “AS IS” AND “AS AVAILABLE” WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON‑INFRINGEMENT, AVAILABILITY, ACCURACY, SECURITY, INTEGRATION, AND QUIET ENJOYMENT. CHARTBEAT DOES NOT WARRANT THAT THE APIS WILL BE ERROR‑FREE OR UNINTERRUPTED, THAT ANY RESULTS WILL BE ACHIEVED, OR THAT THIRD‑PARTY CONTENT WILL BE TRUTHFUL, ACCURATE, RELIABLE, OR COMPLETE. 
  15. Limitation of Liability. TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT WILL CHARTBEAT OR ITS LICENSORS, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, AFFILIATES, OR DATA PROVIDERS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE, EXEMPLARY, OR CONSEQUENTIAL DAMAGES, OR FOR ANY LOSS OF BUSINESS, REVENUES, PROFITS, GOODWILL, OR DATA, OR FOR THE COST OF SUBSTITUTE GOODS OR SERVICES, ARISING OUT OF OR RELATING TO THESE API TERMS OR THE APIS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT WILL CHARTBEAT’S AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO API ACCESS EXCEED THE FEES PAID BY CUSTOMER TO CHARTBEAT FOR ACCESS TO THE APIS IN THE TWELVE‑MONTH PERIOD PRECEDING THE EVENT GIVING RISE TO LIABILITY. THESE LIMITATIONS APPLY REGARDLESS OF THE FORM OF ACTION AND EVEN IF A REMEDY FAILS OF ITS ESSENTIAL PURPOSE. 
  16. Suspension and Termination. Chartbeat may suspend or terminate Customer’s API access immediately upon notice if Chartbeat believes Customer has violated these API Terms, poses a security risk, or fails to pay applicable fees when due. Either Party may terminate the API Terms for material breach not cured within thirty days after written notice. Upon termination or expiration, Customer must cease all use of the APIs and delete API Data in accordance with Section 6, and Sections that by their nature should survive will survive. 
  17. Confidentiality. Any non‑public information disclosed by Chartbeat to Customer in connection with the APIs, including credentials, documentation marked confidential, and non‑public technical or business information, constitutes Chartbeat’s Confidential Information under the Master Terms. Customer must protect and limit use and disclosure of such Confidential Information in accordance with the Master Terms.
  18. Publicity; Branding. Customer must not use Chartbeat’s or Tubular’s names, logos, or marks without prior written authorization and in compliance with Chartbeat’s branding guidelines. Any authorized public disclosures of API Data must include required attribution and disclaimers as instructed by Chartbeat. 
  19. Compliance; Audit. Customer will implement measures to ensure compliance with these API Terms and, upon reasonable notice, will provide information reasonably requested by Chartbeat to verify compliance. Chartbeat may monitor API usage for compliance and quality assurance. 
  20. Export and Government Rights. Customer will comply with applicable export and sanctions laws and will not export, re‑export, or use the APIs or API Data in violation of such laws. If Customer is an agency or instrumentality of the U.S. Government, the APIs are “commercial items” provided with only the rights set forth in these API Terms.
  21. Dispute Resolution; Governing Law; Order of Precedence. Dispute resolution, governing law, jurisdiction, and venue are governed by the Master Terms. In the event of any conflict between these API Terms and the Master Terms, these API Terms control with respect to the subject matter hereof and the Master Terms control otherwise. In the event of any conflict between these API Terms and an order form, the order form controls with respect to fees, quantities, and commercial terms specifically identified therein. 
  22. Changes to API Terms. Chartbeat may update these API Terms from time to time. The then‑current version will govern each use of the APIs. Continued use after the effective date of an update constitutes acceptance of the updated terms.