Connecting your TikTok Shop through Cruva

Cruva runs the affiliate side of a TikTok Shop: the creators who promote your products, the free samples they ask for, the messages you send them and the outreach and automations that find them. When you connect your Cruva account, Cook can read all of it in chat, through the Cook API and through the Cook MCP server. Anything that would change something in Cruva, or reach a creator, waits on an approval card until a person in your workspace approves it.

Before you start

• You need a Cruva account with the Standard API plan or higher. Cruva’s REST API is not part of its plans below Standard, and Cruva refuses the key without it.
• You need permission to manage integrations in the Cook workspace.

Getting your API key and shop id

1. In Cruva, open API settings and create an API key. It starts with cruva_. Copy it; Cruva shows it once.
2. Open My Shops, find the shop you want Cook to read and press View Info. Copy its shop id.

The key decides what Cook can reach. If you limit the key to some routes or some shops in Cruva, Cook can read only those.

Connecting Cruva

1. In Cook, open Integrations and find Cruva.
2. Paste the API key and the shop id, and press Connect.
3. Cook checks the key with Cruva before it saves it. If Cruva refuses it, Cook shows Cruva’s reason, for example a key without API access on its plan.

Cook keeps the key with your workspace’s connection. It is never shown again, never put in chat and never returned by the Cook API.

What Cook can read

Ask in chat, for example “who were my top creators this month” or “which sample requests are waiting”. Cook reads, from your Cruva shop:

• Shops: the shops your key reaches, and which one Cook uses.
• Stats: GMV, orders, affiliate GMV, videos and samples for a date range. Without dates, Cook reads this month to today.
• Affiliates: your creators, with what each one sold in a date range, or their lifetime numbers from Cruva’s affiliate CRM.
• Videos: affiliate videos about your products, with views and GMV.
• Samples: creators’ sample requests, with their status (for example To Review or Ready to Ship).
• Inbox and messages: your creator conversations and the messages in one.
• Outreach logs: what Cruva’s outreach sent to creators.
• Automations: your Cruva automations and whether each is on.
• Ads campaigns: your TikTok ad campaigns with spend and results.

What waits for an approval card

These four actions never happen straight away. Cook files an approval card that shows exactly what will change, and nothing reaches Cruva until a person approves it:

• Approve sample requests: one or more requests, or every request from one creator that is waiting in To Review.
• Reject sample requests: the same way.
• Send a message to a creator: the card shows the message word for word.
• Turn an automation on or off.

Cook carries out an approved card once. If Cruva refuses it, the card says why.

The Cook API and the Cook MCP server

The same reads and proposals are on the Cook API and in the Cook MCP server, so your own agent can use them with your Cook API key.

What	API operation	MCP tool
Shops	cruva.shops	cruva_shops
Stats	cruva.stats	cruva_stats
Affiliates	cruva.affiliates	cruva_affiliates
Videos	cruva.videos	cruva_videos
Sample requests	cruva.samples	cruva_samples
Inbox	cruva.inbox	cruva_inbox
Messages in a conversation	cruva.messages	cruva_messages
Outreach logs	cruva.outreachLogs	cruva_outreach_logs
Automations	cruva.automations	cruva_automations
Ads campaigns	cruva.adsCampaigns	cruva_ads_campaigns
Approve sample requests (approval card)	cruva.approveSamples	cruva_approve_samples
Reject sample requests (approval card)	cruva.rejectSamples	cruva_reject_samples
Message a creator (approval card)	cruva.sendDm	cruva_send_dm
Turn an automation on or off (approval card)	cruva.toggleAutomation	cruva_toggle_automation

The four approval-card operations return the card’s id. A key limited to cruva:read can call the reads; the proposals need cruva:write.

Rate limits

Cruva allows 10 requests a second for each key and shop. If Cruva answers that the key is over that limit, Cook says so; ask again a moment later. The Cook API has its own limits for each Cook key, listed on the API reference.

Removing Cruva

Open Integrations in Cook, open Cruva and disconnect it. Cook deletes the key it kept. To stop the key everywhere, also delete it in Cruva’s API settings.

Getting help

Write to [email protected] with your workspace name. The support page lists what else helps us answer quickly.