Thinkific API Glossary

    Plan Availability
    Legacy Plans
    Platform

Thinkific uses a number of terms that may not be familiar to a new developer. This article aggregates that lexicon in a single place. 

List of Terms

A

  • Admin API - Thinkific's REST API used for making requests as if a creator in a Thinkific account
  • API Access Token - API Authentication method that can be used by Customers to build custom integrations on a Growth or higher Thinkific account. (App Developers should use OAuth
  • Apps Extending Themes (AETs) - An app that uses our API to install a Theme Extension into a Thinkific account (example
  • App Installation Flow - Apps must follow our expected installation flow for them to be listed on the Thinkific App Store
  • App Submission Process - The process by which a third party app is submitted to Thinkific, undergoes testing, and is listed on the Thinkific App Store

E

  • Embedded App - An embedded app has customized what a Thinkific creator see in the app's settings area (under /manage/apps/{slug}) to create a seamless app experience for them

G

L

  • Liquid API - Theme Extensions use our Liquid API to build configurable sections that Thinkific creators can use on their Site Pages

O

P

  • Partner Portal - Thinkific's Partner Portal is a website where you can create and administer your public and private apps. This is where you'll find your client and secret keys.
  • Private App - Third party apps authenticated using OAuth 2.0 intended for use by a handful of accounts
  • Public App - Third party apps authenticated using OAuth 2.0 intended for listing on the Thinkific App Store

S

T

  • Teaching API (Legacy) - Thinkific's REST API used for making requests as if a student in a Thinkific account
  • Thinkific App Store - Thinkific's app marketplace where Thinkific creators can search for first and third party applications to add functionality to their Thinkific account.
  • Thinkific Creator - A catch-all term for owners of Thinkific accounts

* NOTE: Thinkific API Key integration will be sunset at some point in the future. We thus recommend creating a Private App instead of an API Key integration (or possibly a Public App). 

Was this article helpful?
0 out of 1 found this helpful