> ## Documentation Index > Fetch the complete documentation index at: https://docs.nekt.com/llms.txt > Use this file to discover all available pages before exploring further. # TikTok Organic as a data source > Bring data from TikTok Organic (Login Kit / Open API) to Nekt. TikTok Organic refers to non-paid content on TikTok—creator profiles and videos. The connector uses the **TikTok Open API** (Login Kit) to extract the authenticated user's profile and their published videos so you can analyze organic content in your Lakehouse. ## Configuring TikTok Organic as a Source In the [Sources](https://app.nekt.ai/sources) tab, click on the "Add source" button located on the top right of your screen. Then, select the TikTok Organic option from the list of connectors. Click **Next** and you'll be prompted to add your access. ### 1. Add account access You need to authorize Nekt to access your TikTok account via **OAuth 2.0**. Complete the TikTok authorization flow so that the connector can use your OAuth credentials to obtain and refresh access tokens. 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**: you can choose between INCREMENTAL and FULL\_TABLE. All streams use full table sync by default. 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](https://docs.nekt.com/get-started/core-concepts/triggers), 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 define some additional settings: * 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](https://docs.nekt.com/get-started/core-concepts/resource-control). * Determine when to execute an **Additional [Full Sync](https://docs.nekt.com/get-started/core-concepts/types-of-sync#additional-full-sync)**. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. Once you are ready, click **Next** to finalize the setup. ### 5. Check your new source You can view your new source on the [Sources](https://app.nekt.ai/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](https://app.nekt.ai/catalog), you need at least one successful source run. # Streams and Fields Below you'll find all available data streams from TikTok Organic (Open API) and their corresponding fields. Single record with the authenticated user's basic profile (Open API user info). **Key Fields:** | Field | Type | Description | | :------------------ | :------ | :------------------------------- | | `open_id` | String | The user's open ID (primary key) | | `union_id` | String | The user's union ID | | `avatar_url` | String | User's avatar URL | | `display_name` | String | User's display name | | `bio_description` | String | User's bio description | | `profile_deep_link` | String | User's profile deep link | | `is_verified` | Boolean | Whether the user is verified | | `follower_count` | Integer | Number of followers | | `following_count` | Integer | Number of following | | `likes_count` | Integer | Number of likes received | | `video_count` | Integer | Number of videos posted | | `username` | String | User's username | List of videos published by the authenticated user (paginated). **Key Fields:** | Field | Type | Description | | :------------------ | :------ | :---------------------------------- | | `id` | String | The video's unique ID (primary key) | | `create_time` | Integer | Video creation unix timestamp | | `cover_image_url` | String | Video cover image URL | | `share_url` | String | Video share URL | | `video_description` | String | Video description | | `duration` | Integer | Video duration in seconds | | `height` | Integer | Video dimension height in pixels | | `width` | Integer | Video dimension width in pixels | | `title` | String | Video title | | `embed_html` | String | Embed code | | `embed_link` | String | Embed link | | `like_count` | Integer | Number of likes | | `comment_count` | Integer | Number of comments | | `share_count` | Integer | Number of shares | | `view_count` | Integer | Number of views | # Data Model The following diagram illustrates the relationship between the two streams. **user\_info** is the authenticated user's profile; **videos** is the list of videos published by that user. ```mermaid theme={null} erDiagram user_info ||--o{ videos : "open_id (owner)" user_info { string open_id PK string display_name string username int follower_count int video_count } videos { string id PK int create_time string video_description int like_count int view_count } ``` # Implementation Notes * **Authentication**: The connector uses **OAuth credentials** to obtain and refresh access tokens automatically. * **API base**: Requests are sent to the TikTok Open API by default. Endpoints used include `/v2/user/info/` (user\_info) and `/v2/video/list/` (videos). * **Pagination**: **videos** uses cursor-based pagination (cursor, max\_count). **user\_info** returns a single record. * **Stream selection**: You can select **user\_info**, **videos**, or both. Select only what you need to reduce extraction time and catalog size. ## Skills for agents TikTok Organic connector documentation as plain markdown, for use in AI agent contexts.