Skip to main content
Thinkific is a platform to create, sell and deliver online courses. This connector reads your site’s data through the Thinkific Admin API: courses with their chapters and lessons, course reviews, enrollments with progress and completion, users and their custom profile fields, instructors, groups with their members and analysts, orders, products with their price options, bundles, categories, promotions and coupons.
The connector only reads data. It never creates, changes or deletes courses, users, enrollments or orders in Thinkific.

Before you start

  • Your Thinkific plan must include the API. Thinkific only gives API access to sites on the Grow plan (Pro + Growth) or higher. On other plans every request is refused as if the credentials were wrong.
  • You need the site owner (or an admin who can manage API access). The connector signs in with an API Access Token created in the site settings.
  • Courses built with the new course builder are not in the API. Thinkific leaves them out of its REST API (courses, chapters, lessons, categories and products). Enrollments in those courses do appear in the enrollments table.
  • Some tables depend on your Thinkific plan. When a feature is not included in your plan (groups, for example), Thinkific refuses to share it. Those tables are skipped and marked as failed in the run, and the other tables keep syncing. Upgrade the plan, or deselect those tables.

Configuring Thinkific as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Thinkific option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

Choose how the connector signs in. API Access Token is the method Thinkific recommends. To create an API Access Token:
  1. Sign in to your Thinkific site.
  2. Go to Settings and open the Code & analytics tab.
  3. Scroll to API Access Tokens and click Add API access token.
  4. Give it a name (for example, “Nekt”) and an expiration date, and click Save.
  5. Copy the token. Thinkific shows it only once.
See Thinkific’s guide to API Access Tokens.
The token stops working on the expiration date you chose. When it expires the sync fails: create a new token in Thinkific and update it in the source. The token gives access to all the data of your site, so keep it safe.
If your site already uses the legacy API key, you can use it instead: it is under Settings > Code & analytics > API, together with your site’s subdomain. Thinkific plans to retire this method, and resetting the key to see it again breaks any other integration that uses it. The following configurations are available:
  • Authentication Method: API Access Token (recommended) or API Key and subdomain (legacy).
  • API Access Token: the token you created, when you chose API Access Token.
  • API Key: the legacy API key of your site, when you chose the legacy method.
  • Subdomain: the first part of your site’s thinkific.com address (yourschool for yourschool.thinkific.com), when you chose the legacy method. Not your custom domain.
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: enrollments can be synced as Incremental: each sync brings only the enrollments that changed since the previous one (and, once a week, all of them again). Every other table is synced as Full table: each sync brings the current state of the data, so records deleted in Thinkific also leave your catalog.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here. Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description. Every table also has an additional_fields column: any field Thinkific returns that is not mapped to its own column, as a JSON object.

Fields by stream

Fields marked String (JSON) hold a JSON value; use your SQL engine’s JSON functions to read them.

Courses and learning

The courses of the site. Courses built with Thinkific’s new course builder are not available in the API. Read in full on every sync.Table: courses · Primary key: id · Sync: Full table
The chapters of each course, read with one request per course. Read in full on every sync.Table: chapters · Primary key: id · Sync: Full table
The lessons, quizzes, surveys and other contents of each chapter, read with one request per chapter. Read in full on every sync.Table: contents · Primary key: id · Sync: Full table
The reviews of each course, approved or not, read per course. Read in full on every sync.Table: course_reviews · Primary key: id · Sync: Full table
Which user is enrolled in which course, with progress, completion and expiry. The first sync reads every enrollment; later syncs read the enrollments updated since the previous sync (with one day of margin) up to the moment the sync started, and once a week all of them again, so values that change when a date passes (such as expired) are refreshed. An enrollment updated while a sync runs is picked up by the next sync. If the weekly full refresh cannot be completed, that sync still loads the recent changes and the next one tries the full refresh again.Table: enrollments · Primary key: id · Sync: Incremental (by updated_at)

People

Every user of the site: students, admins and affiliates. Read in full on every sync.Table: users · Primary key: id · Sync: Full table
The custom profile fields of each user (for example country or phone), one row per user and field. Read in full on every sync.Table: user_custom_profile_fields · Primary key: user_id, id · Sync: Full table
The custom fields of the site’s sign-up form. Read in full on every sync.Table: custom_profile_field_definitions · Primary key: id · Sync: Full table
The instructor profiles shown on courses. Read in full on every sync.Table: instructors · Primary key: id · Sync: Full table
Groups of students, for example the employees of a client company. May depend on your Thinkific plan. Read in full on every sync.Table: groups · Primary key: id · Sync: Full table
The users who can see each group’s reports, read with one request per group. Read in full on every sync.Table: group_analysts · Primary key: group_id, user_id · Sync: Full table
The users that belong to each group, read per group. Before reading the groups, the connector checks that Thinkific applies the group filter; if it does not, this table fails instead of listing every user in every group. Read in full on every sync.Table: group_members · Primary key: group_id, user_id · Sync: Full table

Sales

The order history of the site. Read in full on every sync.Table: orders · Primary key: id · Sync: Full table
The products of each order, one row per order and product. Read in full on every sync.Table: order_items · Primary key: order_id, item_index · Sync: Full table
What the site sells: courses, bundles and communities. Read in full on every sync.Table: products · Primary key: id · Sync: Full table
The price options of each product (one-time, subscription, payment plan, free). Read in full on every sync.Table: product_prices · Primary key: id · Sync: Full table
Bundles of courses, read with one request per bundle product. Read in full on every sync.Table: bundles · Primary key: id · Sync: Full table
The courses of each bundle, one row per bundle and course. Read in full on every sync.Table: bundle_courses · Primary key: bundle_id, course_id · Sync: Full table
The categories of the site (called collections in the Thinkific API). Read in full on every sync.Table: collections · Primary key: id · Sync: Full table
The products of each category, one row per category and product. Read in full on every sync.Table: collection_products · Primary key: collection_id, product_id · Sync: Full table
Discount rules. Coupons are the usable codes of a promotion. Read in full on every sync.Table: promotions · Primary key: id · Sync: Full table
The coupon codes of each promotion, read per promotion. Read in full on every sync.Table: coupons · Primary key: id · Sync: Full table

Implementation notes

  • Full reads. Except for enrollments, Thinkific’s API has no filter by update date, so those tables are read in full on every sync. A table is only replaced once it was read completely: when Thinkific fails or answers inconsistently in the middle of a table, that table keeps the data of the previous sync and the run says which table failed.
  • Changes during a sync. Thinkific returns its lists page by page, so a record created or deleted while a list is being read can shift the others between pages. To avoid missing records, the connector reads every list that has more than one page at least twice and combines the reads, reading again while a read still finds records the earlier ones missed. Records that appear because they were created or updated during the sync do not count as missed. If a list keeps changing in a way the reads cannot settle, that table fails instead of loading with gaps, and the next sync tries again.
  • Empty answers. If a table that had records in the previous sync suddenly comes back empty, the sync stops that table instead of emptying it. If the data really was removed in Thinkific, run a Full sync of the source to accept the empty table.
  • Tables Thinkific refuses or does not offer. When Thinkific answers that a feature is not included in your plan, the tables of that feature are skipped and marked as failed, and the sync log names them. The same happens, with a “not found” message, when Thinkific does not offer one of the lists for your site. If no selected table can be read, or the credentials are invalid or expired, the run fails.
  • Renamed columns. Two API fields have names that are reserved words in SQL: a category’s default is loaded as is_default, and a price option’s interval and interval_count as billing_interval and billing_interval_count.
  • Amounts. Order amounts come in the site’s currency; Thinkific calls the unit “dollars” (amount_dollars) and also sends the value in cents (amount_cents).
  • Rate limits. Thinkific allows 120 requests per minute per site, shared with your other integrations. The connector sends one request at a time, spaced to use at most about two thirds of that limit so your other integrations keep working, and waits and retries when Thinkific asks it to slow down. Tables read per course, chapter, promotion or group take one request per record, so sites with many courses and chapters take longer to sync.