TikTok Shop is TikTok’s e-commerce marketplace, where sellers list products and fulfill orders placed through in-feed videos, LIVE sessions, the product showcase and the Shop tab. The TikTok Shop Partner Open API gives access to a seller’s shop data, including orders, product catalog, stock, settlement statements, returns, packages, promotions, and LIVE analytics.

Configuring TikTok Shop as a Source

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

1. Add account access

You’ll need to authorize Nekt to access your TikTok Shop data. You don’t need to register anything in the TikTok Shop Partner Center — Nekt already has an approved app there, and you simply grant it access to your shop. Click on the Authorization button. You’ll be redirected to TikTok Shop, where you need to be signed in to the Seller Center account that owns the shop you want to sync. There you’ll:

Confirm the shop the authorization applies to, choose the access duration (we recommend Unlimited, so the connection doesn’t stop working on a fixed date) and enter a contact email, then click Confirm installation.
Review the permissions Nekt is requesting — product, order, logistics, finance, and analytics information — accept the acknowledgement and click Authorize.

You’ll be redirected back to Nekt with the connection filled in automatically. If you ever need to reconnect the shop, use the Refresh button next to the field. The following configurations are also available:

Start Date: The earliest date from which records will be synced. If not provided, all available historical data will be extracted.

The following advanced settings are also available:

Shop cipher: The encrypted identifier of a single shop. Leave it empty to sync every shop the authorization covers — the connector resolves the shops automatically.
Shop ID: The shop identifier reported alongside the records. Only used when a shop cipher is set manually.
Lookback Days: (Default: 7) How many days before the last synced day the LIVE analytics streams re-read on each run, so metrics TikTok Shop restates after the fact (late payments, returns, refunds) are captured.

Don’t have access to the TikTok Shop account yourself? Use the Share link option at the top of this step to send the authorization to whoever manages the shop — they complete it without needing a Nekt account.

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.
- Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
- Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in 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 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.
Determine when to execute an 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 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.

Stream	Slug	Description
Shops	`shops`	The shops the connected authorization gives access to.
Orders	`orders`	Orders placed in the shop, with their status timeline and fulfillment data.
Products	`products`	Products listed in the shop, with their SKUs, prices, and stock.
Product Inventory	`product_inventory`	Available and committed stock per SKU and warehouse.
Statements	`statements`	Settlement statements (payouts transferred to the seller).
Statement Transactions	`statement_transactions`	Individual transactions that make up each settlement statement.
Withdrawals	`withdrawals`	Withdrawals and transfers made from the TikTok Shop balance.
Returns	`returns`	Return and refund requests opened against the shop’s orders.
Cancellations	`cancellations`	Order cancellation requests raised by buyers, sellers or the platform.
Packages	`packages`	Packages created to fulfill the shop’s orders.
Promotion Activities	`promotion_activities`	Promotion activities configured in the shop.
Coupons	`coupons`	Coupons created by the shop.
Warehouses	`warehouses`	Warehouses registered by the shop for pickup and returns.
LIVE Sessions	`live_sessions`	LIVE sessions that generated sales for the shop, with performance metrics.
LIVE Session Minutes	`live_session_minutes`	Minute-by-minute breakdown of each finished session.
LIVE Session Products	`live_session_products`	Performance of each product featured in a session.
LIVE Daily Performance	`live_daily_performance`	The shop’s LIVE sales aggregated per day.

Fields by stream

Below you’ll find all available data streams from TikTok Shop and their corresponding fields:

Shops

The shops the connected authorization gives access to. Useful to map shop_id values to shop names and regions.

Field	Type	Description
`id`	String	Unique identifier of the shop
`name`	String	Display name of the shop
`region`	String	Market the shop sells in (e.g. BR, US, ID)
`seller_type`	String	Whether the seller is local to the region or cross-border
`cipher`	String	Encrypted shop identifier used by shop-scoped endpoints
`code`	String	Short shop code used by TikTok Shop

Orders

Orders placed in the shop, with their status timeline, buyer information, fulfillment data and full payment breakdown. Synced incrementally by update_time.

Field	Type	Description
`id`	String	TikTok Shop order identifier
`shop_id`	String	Shop the order belongs to
`status`	String	Order status (UNPAID, ON_HOLD, AWAITING_SHIPMENT, PARTIALLY_SHIPPING, AWAITING_COLLECTION, IN_TRANSIT, DELIVERED, COMPLETED, CANCELLED)
`order_type`	String	Order type, such as a regular order or a pre-order
`commerce_platform`	String	Platform where the order was placed
`create_time`	Integer	When the order was placed (Unix timestamp)
`update_time`	Integer	Last change to the order, used as the incremental replication key (Unix timestamp)
`paid_time`	Integer	When the order was paid (Unix timestamp)
`rts_time`	Integer	When the seller marked the order ready to ship (Unix timestamp)
`collection_time`	Integer	When the carrier collected the package (Unix timestamp)
`delivery_time`	Integer	When the package was delivered (Unix timestamp)
`cancel_time`	Integer	When the order was cancelled (Unix timestamp)
`rts_sla_time`, `tts_sla_time`, `delivery_sla_time`	Integer	Platform deadlines for shipping, collection and delivery (Unix timestamp)
`shipping_due_time`, `collection_due_time`, `delivery_due_time`	Integer	Due dates for each fulfillment step (Unix timestamp)
`cancel_order_sla_time`	Integer	When the platform automatically cancels the order (Unix timestamp)
`pick_up_cut_off_time`, `fast_dispatch_sla_time`, `recommended_shipping_time`, `release_date`	Integer	Other fulfillment related times (Unix timestamps)
`user_id`	String	TikTok user identifier of the buyer
`buyer_email`	String	Email address of the buyer
`buyer_nickname`, `buyer_avatar`	String	Public TikTok profile of the buyer
`buyer_message`	String	Note left by the buyer at checkout
`seller_note`	String	Internal note added by the seller
`cpf`, `cpf_name`	String	Buyer tax identifier used to issue an invoice (Brazil)
`fulfillment_type`	String	FULFILLMENT_BY_SELLER, FULFILLMENT_BY_TIKTOK or FULFILLMENT_BY_DILAYANI_TOKOPEDIA
`delivery_type`	String	HOME_DELIVERY or COLLECTION_POINT
`shipping_type`	String	TIKTOK, SELLER or TIKTOK_DIGITAL
`shipping_provider`, `shipping_provider_id`	String	Carrier handling the order
`tracking_number`	String	Carrier tracking number
`delivery_option_id`, `delivery_option_name`	String	Delivery option chosen by the buyer
`warehouse_id`	String	Warehouse serving the order
`fast_delivery_program`, `fulfillment_priority_level`	String	Additional fulfillment program tags
`cancellation_initiator`	String	SELLER, BUYER or SYSTEM
`cancel_reason`	String	Reason the order was cancelled
`is_buyer_request_cancel`	Boolean	Whether the buyer asked to cancel
`is_on_hold_order`, `has_updated_recipient_address`, `authentication_required`	Boolean	Flags regarding specific order states
`is_replacement_order`, `is_exchange_order`	Boolean	Flags regarding order replacements and exchanges
`replaced_order_id`, `exchange_source_order_id`	String	Identifiers for replaced and exchanged orders
`is_sample_order`, `is_refundable_sample`, `is_subscription_order`	Boolean	Flags specifying specialized order types
`split_or_combine_tag`, `auto_combine_group_id`	String	Details for split or combined fulfillment orders
`need_upload_invoice`	Boolean	Whether uploading an invoice is required
`consultation_id`	String	Internal consultation identifier
`payment_method_name`	String	Payment method used by the buyer
`is_cod`	Boolean	Whether the buyer pays cash on delivery
`payment`	JSON	JSON object with the full payment breakdown: `currency`, `sub_total`, `shipping_fee`, `seller_discount`, `platform_discount`, `tax`, `total_amount` and the market-specific fees
`line_items`	JSON	Products, quantities, prices, discounts and taxes of the order
`packages`	JSON	Packages the order was split into
`recipient_address`	JSON	Delivery address (not available while the order is UNPAID or ON_HOLD)
`handling_duration`	JSON	Handling time agreed for the order
`order_rights`	JSON	Order tags from the programs the seller subscribes to

Products

Products listed in the shop, with their SKUs, prices and stock. Synced incrementally by update_time.

Field	Type	Description
`id`	String	TikTok Shop product identifier
`shop_id`	String	Shop the product belongs to
`title`	String	Product title shown to buyers
`status`	String	Listing status (DRAFT, PENDING, FAILED, ACTIVATE, SELLER_DEACTIVATED, PLATFORM_DEACTIVATED, FREEZE, DELETED)
`create_time`	Integer	When the product was created
`update_time`	Integer	Last change to the product, used as the incremental replication key
`is_not_for_sale`	Boolean	Whether the product is flagged as not available for sale
`has_draft`	Boolean	Whether the product has unpublished draft changes
`listing_quality_tier`	String	Quality tier TikTok Shop assigns to the listing content
`skus`	JSON	SKUs with seller SKU, price, stock per warehouse, status and fees
`sales_regions`	JSON	Regions where the product is sold
`recommended_categories`	JSON	Categories TikTok Shop recommends for the product
`integrated_platform_statuses`	JSON	Status on natively integrated platforms, such as Tokopedia
`audit`	JSON	Audit status of the product and the reasons behind it
`product_families`	JSON	Product families the product belongs to
`scheduled_sale`	JSON	Scheduled sale configuration
`product_sync_fail_reasons`	JSON	Why syncing the global product to this listing failed

Product Inventory

Available and committed stock per SKU and warehouse. Synced incrementally by product_update_time.

Field	Type	Description
`product_id`	String	TikTok Shop product identifier
`product_update_time`	Integer	Unix timestamp of the last change to the product this stock belongs to, used as the incremental replication key
`shop_id`	String	Shop the product belongs to
`skus`	JSON	JSON array with the stock of each SKU, broken down by warehouse and by campaign, creator and in-shop allocation

Statements

Settlement statements, that is, the payouts TikTok Shop transfers to the seller. Synced incrementally by statement_time.

Field	Type	Description
`id`	String	Settlement statement identifier
`shop_id`	String	Shop the statement belongs to
`statement_time`	Integer	When the statement was generated, used as the incremental replication key
`payment_time`	Integer	When the payout was transferred to the seller
`payment_status`	String	Whether the payout already reached the seller’s bank account
`payment_id`	String	Identifier of the payout transfer
`currency`	String	Currency of every amount in the statement
`settlement_amount`	String	Net amount settled to the seller
`revenue_amount`	String	Gross revenue included in the statement
`net_sales_amount`	String	Revenue after seller-funded discounts
`fee_amount`	String	Total platform fees deducted
`shipping_cost_amount`	String	Total shipping costs
`adjustment_amount`	String	Total adjustments applied by TikTok Shop policy

Statement Transactions

The individual transactions that make up each settlement statement, which is where order-level revenue, fees and shipping costs can be reconciled. Synced incrementally by statement_time.

Field	Type	Description
`id`	String	Transaction identifier
`statement_id`	String	Settlement statement the transaction belongs to
`statement_time`	Integer	Unix timestamp of when the parent statement was generated, used as the incremental replication key
`shop_id`	String	Shop the transaction belongs to
`type`	String	Transaction type, such as an order settlement or an adjustment
`order_id`	String	Order the transaction settles
`order_create_time`	Integer	When the settled order was placed
`currency`	String	Currency of every amount in the transaction
`settlement_amount`	String	Net amount settled for the transaction
`revenue_amount`	String	Revenue recognized in the transaction
`shipping_cost_amount`	String	Shipping cost charged to the seller
`fee_tax_amount`	String	Taxes charged on the platform fees
`adjustment_amount`, `adjustment_id`, `adjustment_order_id`	String	Adjustment details
`reserve_id`, `reserve_amount`, `reserve_status`	String	Funds withheld under the reserve policy
`estimated_release_time`	Integer	When withheld funds are estimated to be released
`associated_order_id`	String	Order associated with a reserve or adjustment entry
`revenue_breakdown`	JSON	Detailed revenue components
`shipping_cost_breakdown`	JSON	Detailed shipping cost components
`fee_tax_breakdown`	JSON	Detailed fee tax components
`supplementary_component`	JSON	Additional settlement components

Withdrawals

Withdrawals and transfers made from the TikTok Shop balance. Synced incrementally by create_time.

Field	Type	Description
`id`	String	Withdrawal identifier
`shop_id`	String	Shop the withdrawal belongs to
`type`	String	Withdrawal type, such as a settlement transfer or a manual withdrawal
`amount`	String	Amount withdrawn
`currency`	String	Currency of the withdrawal
`status`	String	Current status of the withdrawal
`create_time`	Integer	When the withdrawal was created, used as the incremental replication key

Returns

Return and refund requests opened against the shop’s orders. Synced incrementally by update_time.

Field	Type	Description
`return_id`	String	Return request identifier
`shop_id`	String	Shop the return belongs to
`order_id`	String	Order the return was opened against
`return_type`	String	Type of the request (refund, return and refund, replacement)
`return_status`	String	Current status of the request
`arbitration_status`	String	Status of the platform arbitration, when escalated
`role`	String	Who initiated the return
`return_reason`, `return_reason_text`	String	Reason for the return
`create_time`	Integer	When the request was opened
`update_time`	Integer	Last change to the request, used as the incremental replication key
`shipment_type`	String	How the buyer sends the items back
`handover_method`	String	Handover method chosen by the buyer
`return_tracking_number`	String	Tracking number of the return shipment
`return_provider_name`, `return_provider_id`	String	Carrier handling the return
`return_shipping_document_type`	String	Type of return shipping document
`return_method`	String	Method used to return the items
`can_buyer_keep_item`	Boolean	Whether the buyer may keep the item and still be refunded
`is_quick_refund`	Boolean	Whether the buyer was refunded before the items were received
`seller_proposed_return_type`	String	Return type the seller proposed instead
`buyer_rejected_partial_refund`	Boolean	Whether the buyer rejected the proposed partial refund
`is_combined_return`	Boolean	Whether the return was combined with others
`combined_return_id`	String	Identifier if the return was combined
`pre_return_id`, `next_return_id`	String	Related return requests
`return_line_items`	JSON	Items covered by the return, with refund amounts
`refund_amount`	JSON	Refund breakdown of the request
`discount_amount`	JSON	Discounts reverted by the return
`shipping_fee_amount`	JSON	Shipping fees involved in the return
`partial_refund`	JSON	Partial refund proposed for the return
`return_warehouse_address`	JSON	Address the items must be returned to
`seller_next_action_response`	JSON	Actions the seller must take and their deadlines

Cancellations

Order cancellation requests raised by buyers, sellers or the platform. Synced incrementally by update_time.

Field	Type	Description
`cancel_id`	String	Cancellation request identifier
`shop_id`	String	Shop the cancellation belongs to
`order_id`	String	Order the cancellation refers to
`cancel_type`	String	Type of the cancellation request
`cancel_status`	String	Current status of the request
`role`	String	Who initiated the cancellation
`cancel_reason`, `cancel_reason_text`	String	Reason for the cancellation
`should_replenish_stock`	Boolean	Whether the cancelled items return to available stock
`create_time`	Integer	When the cancellation was requested
`update_time`	Integer	Last change to the cancellation, used as the incremental replication key
`cancel_line_items`	JSON	Items covered by the cancellation, with refund amounts
`refund_amount`	JSON	Refund breakdown of the cancellation
`seller_next_action_response`	JSON	Actions the seller must take and their deadlines

Packages

Packages created to fulfill the shop’s orders. Synced incrementally by update_time.

Field	Type	Description
`id`	String	Package identifier
`shop_id`	String	Shop the package belongs to
`status`	String	Current status of the package
`create_time`	Integer	When the package was created
`update_time`	Integer	Last change to the package, used as the incremental replication key
`tracking_number`	String	Carrier tracking number
`shipping_provider_name`, `shipping_provider_id`	String	Carrier handling the package
`orders`	JSON	JSON array with the orders and SKUs contained in the package
`order_line_item_ids`	JSON	JSON array with the order line items contained in the package

Promotion Activities

Promotion activities configured in the shop, such as flash sales and direct discounts.

Field	Type	Description
`id`	String	Promotion activity identifier
`shop_id`	String	Shop the activity belongs to
`title`	String	Title of the promotion activity
`activity_type`	String	Type of promotion (FLASHSALE, DIRECT_DISCOUNT, SHIPPING_DISCOUNT, BUY_MORE_SAVE_MORE, GIFT_WITH_PURCHASE)
`duration_type`	String	Whether the activity runs for a fixed period or is open ended
`status`	String	Current status of the activity
`product_level`	String	Whether the promotion applies at product or variation level
`begin_time`, `end_time`	Integer	When the promotion starts and ends
`create_time`, `update_time`	Integer	When the promotion was created and last changed
`discount`	JSON	Discount rules of the activity
`participation_limit`	JSON	Limits on how many times a buyer can use the promotion
`activity_commands`	JSON	Operations currently allowed on the activity

Coupons

Coupons created by the shop.

Field	Type	Description
`id`	String	Coupon identifier
`shop_id`	String	Shop the coupon belongs to
`title`	String	Title of the coupon
`display_type`	String	Where the coupon is shown to buyers
`status`	String	Current status of the coupon
`promo_code`	String	Code buyers enter to redeem the coupon
`target_buyer_segment`	String	Buyer segment the coupon targets
`product_scope`	String	Range of products the coupon applies to
`creation_source`	String	System where the coupon was created
`create_time`, `update_time`	Integer	When the coupon was created and last changed
`claim_duration`	JSON	Period during which buyers can claim the coupon
`redemption_duration`	JSON	Period during which a claimed coupon can be redeemed
`usage_limits`	JSON	Claim and redemption limits
`discount`	JSON	Discount granted by the coupon
`threshold`	JSON	Minimum purchase required to use the coupon

Warehouses

Warehouses registered by the shop for pickup and returns.

Field	Type	Description
`id`	String	Warehouse identifier
`shop_id`	String	Shop the warehouse belongs to
`name`	String	Name of the warehouse
`entity_id`	String	Legal entity the warehouse belongs to
`effect_status`	Boolean	Whether the warehouse is currently in effect
`type`	String	Warehouse purpose, such as sales or return warehouse
`sub_type`	String	More specific warehouse classification
`is_default`	Boolean	Whether this is the default warehouse for its type
`address`	JSON	JSON object with the full warehouse address, including geolocation

LIVE Sessions

LIVE sessions that generated sales for the shop, with their performance metrics. Synced incrementally by start_time (with lookback).

Field	Type	Description
`id`	String	TikTok Shop identifier of the LIVE session
`shop_id`	String	Shop the session belongs to
`account_type`	String	Type of TikTok account that hosted the LIVE (OFFICIAL_ACCOUNTS, MARKETING_ACCOUNTS, AFFILIATE_ACCOUNTS)
`title`	String	Title of the LIVE session
`username`	String	TikTok username of the host of the LIVE
`start_time`	Integer	Unix timestamp (UTC) of when the LIVE started, used as the incremental replication key
`end_time`	Integer	Unix timestamp (UTC) of when the LIVE ended
`currency`	String	ISO 4217 code of the currency
`gmv`	String	Gross merchandise value of the orders placed directly from the LIVE
`gmv_24h`	String	Gross merchandise value within 24h
`avg_price`	String	Average price
`products_added`	Integer	Number of products added
`different_products_sold`	Integer	Number of different products sold
`created_sku_orders`	Integer	Created SKU orders
`sku_orders`	Integer	SKU orders
`items_sold`	Integer	Items sold
`customers`	Integer	Customers
`click_to_order_rate`	String	Click to order rate
`acu`	Integer	Average concurrent users
`pcu`	Integer	Peak concurrent users
`viewers`	Integer	Viewers
`views`	Integer	Views
`avg_viewing_duration`	Integer	Average viewing duration
`comments`	Integer	Comments
`shares`	Integer	Shares
`likes`	Integer	Likes
`new_followers`	Integer	New followers
`product_impressions`	Integer	Product impressions
`product_clicks`	Integer	Product clicks
`click_through_rate`	String	Click through rate

LIVE Session Minutes

Minute-by-minute breakdown of each finished session (available only for OFFICIAL and MARKETING accounts). Full table child of live_sessions.

Field	Type	Description
`live_id`	String	TikTok Shop identifier of the parent LIVE session
`shop_id`	String	Shop the session belongs to
`account_type`	String	Type of TikTok account that hosted the LIVE
`metrics`	JSON	Detailed minute-by-minute performance metrics

LIVE Session Products

Performance of each product featured in a session (available only for OFFICIAL and MARKETING accounts). Full table child of live_sessions.

Field	Type	Description
`live_id`	String	TikTok Shop identifier of the parent LIVE session
`shop_id`	String	Shop the session belongs to
`account_type`	String	Type of TikTok account that hosted the LIVE
`product_id`	String	Product identifier
`metrics`	JSON	Detailed product performance metrics

LIVE Daily Performance

The shop’s LIVE sales aggregated per day. Synced incrementally by start_date (with lookback).

Field	Type	Description
`shop_id`	String	Shop the performance metrics belong to
`account_type`	String	Type of TikTok account
`date`	String	Date of the metrics, used as the incremental replication key
`currency`	String	ISO 4217 code of the currency
`metrics`	JSON	Aggregated daily performance metrics

Data Model

The following diagram illustrates the relationships between the core data streams in TikTok Shop.

Implementation Notes

LIVE analytics: The live_* streams read the TikTok Shop Analytics API. They are date-window endpoints (start_date_ge / end_date_lt, in the shop’s timezone), so the sync range is split into 30-day windows and each partition represents a unique combination of shop, account type, and window. Without start_date, the first sync covers the last 365 days.
Restated data: LIVE analytics data is published on a T-1 basis and restated as orders are paid, returned, or refunded. Incremental runs automatically re-read previous days based on the lookback_days setting before the bookmark to capture these changes.
Account Types: live_sessions and live_daily_performance are requested once per account type (OFFICIAL_ACCOUNTS, MARKETING_ACCOUNTS, AFFILIATE_ACCOUNTS) and carry an account_type column. Interaction metrics and the per-session drill-downs (live_session_minutes, live_session_products) only exist for LIVEs hosted by official and marketing accounts.
Multiple shops: A single authorization can cover more than one shop. Every record carries a shop_id column identifying which shop it came from, and the shops stream lists the shops the authorization reaches.
Timestamps: TikTok Shop returns dates as Unix timestamps in seconds (UTC), so fields such as create_time and update_time are integers.
Amounts: Monetary values arrive as strings in the shop’s currency, preserving the exact value returned by TikTok Shop. Ratio fields (like click_through_rate) are kept as strings, as their format varies between endpoints.
Nested data: Fields that contain nested structures — such as the order payment breakdown or the product SKUs — are stored as JSON strings, so they stay stable as TikTok Shop adds new subfields.
Rate limits: TikTok Shop allocates request capacity dynamically per app and shop. When the platform throttles a request, the connector waits and retries automatically, which can make an extraction take longer.

Skills for agents

Download TikTok Shop skills file

TikTok Shop connector documentation as plain markdown, for use in AI agent contexts.

Documentation

Get started

Context

Activate

Workspace

Resources

TikTok Shop as a data source

Configuring TikTok Shop as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Available streams

Fields by stream

Data Model

Implementation Notes

Skills for agents

Download TikTok Shop skills file

​Configuring TikTok Shop as a Source

​1. Add account access

​2. Select streams

​3. Configure data streams

​4. Configure data source

​5. Check your new source

​Streams and Fields

​Available streams

​Fields by stream

​Data Model

​Implementation Notes

​Skills for agents

Download TikTok Shop skills file

Configuring TikTok Shop as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Available streams

Fields by stream

Data Model

Implementation Notes

Skills for agents