Warm TikTok & Instagram accounts with Claude Code

Q: How many terms should I buy?

6–9 for a focused niche is typical; use `generate_warming_terms` and remove anything a real viewer would not type. More terms means more sessions, not longer ones.

Q: What happened to deep warming?

`wants_deep_warming` is discontinued; new orders are rejected with `DEEP_WARMING_DEPRECATED`. Use `wants_advanced_warming`.

Warming from Claude Code means asking TokPortal's manager to spend real, recorded sessions on the account — open the profile, search a niche term, watch and engage with results, leave a comment — one session per term, verified by TokPortal before the manager is paid. The agent generates the terms with generate_warming_terms, attaches them at creation (wants_advanced_warming + advanced_warming_terms) or later (configure_bundle_warming_terms), and re-warms delivered accounts with rewarm_account; list_account_warming_sessions returns the proof. Nothing comparable exists in an official API, which has no notion of an account's behavioral history.

Connect TokPortal to Claude Code

Claude Code is a terminal agent: Anthropic's terminal coding agent; MCP servers are added with claude mcp add and used in any session.

Remote (OAuth, recommended):

claude mcp add --transport http tokportal https://app.tokportal.com/api/ext/mcp

Then run /mcp inside Claude Code and authenticate in the browser. Local stdio alternative with an API key:

claude mcp add tokportal -e TOKPORTAL_API_KEY=sk_... -- npx -y tokportal-mcp

Prefer a packaged install? The TokPortal plugin ships the MCP server plus slash commands:

claude plugin marketplace add tokportal/claude-plugin
claude plugin install tokportal@tokportal

Snippet status: verified against Claude Code's documentation (source).

Dedicated guide: Claude Code + TokPortal.

Once connected, sanity-check the setup with a read-only call: "What is my TokPortal credit balance?" should trigger tokportal_get_credit_balance. GET requests and dry-run writes do not spend credits.

Try the workflow without spending

For this trial, use the remote MCP endpoint https://app.tokportal.com/api/ext/mcp, local tokportal-mcp 1.15.1 or later, or the REST API. Upgrade and restart an older local server first. Version 1.15.0 does not forward the dry-run header; do not use its write tools for a simulation. If you cannot verify the installed local version, use the remote endpoint or REST.

Use the sandbox for the first attempt. MCP write tools accept dry_run: true as a top-level argument, beside body; REST writes accept the X-TokPortal-Dry-Run: true header. Keep your usual authentication and scopes. Each simulated write validates the request and returns credits_would_charge with credits_charged: 0. Nothing is created or published.

Simulated IDs start with 00000000-0000-4000-8000-. Use them only in later dry-run writes. GET requests read real data, so skip publish-readiness checks and polling for synthetic IDs. Simulations have no cross-call memory and upload URLs are placeholders: do not upload files to them.

To run for real, review the returned price and confirm before the first live write. Bundle creation charges credits immediately; publishing hands the order to a manager. Repeat creation without dry-run mode and use the new real IDs for configuration and publishing. A synthetic ID cannot be reused in a live request.

How it works

Advanced Niche Warming is billed per target (search term), 5 credits each at the standard rate, bought 3 to 30 at a time in multiples of 3 — never per day. Each target becomes a screen-recorded session: the manager opens the account, searches the term, watches videos from the results, likes/saves and comments. TokPortal verifies every recording (an AI pass plus checks) before paying the manager, and exposes the outcome as a warming session with per-term status, so your agent can read the report rather than trust a promise. Webhooks warming.session_started, warming.term_verified and warming.session_completed fire along the way.

From Claude Code there are three entry points. At creation: create_bundle with wants_advanced_warming: true and either the terms (advanced_warming_terms) or just a count (advanced_warming_terms_count) to be filled later. Later on a bundle: configure_bundle_warming_terms sets exactly the purchased number of terms once (one-shot) and, if the manager already holds the order, warming starts immediately. On a delivered account: rewarm_account with 3–30 search_terms starts a fresh cycle — useful before a campaign or after a pause. generate_warming_terms (text, platform, count) writes terms in the same language as the description, which is what you want for a Spanish account in Mexico or an English one in the US.

Good terms are what a real viewer of that niche would type: "air fryer recipes", "gym tok", "skincare routine oily skin" — not brand names, not hashtags. Warming does not guarantee reach; it gives the account a coherent behavioral profile before you post, and a verifiable record you can show a client.

Run it from Claude Code

Start a Claude Code session in the project folder and paste the prompt below. Every tokportal_* call is shown before it runs; approve read-only tools freely and review write tools (create_*, configure_*, publish_*) before accepting.

Tool sequence

tokportal_get_credit_costs — Live per-target price and any allowance.
tokportal_generate_warming_terms — text (niche description), platform, count (multiple of 3) → suggested terms.
tokportal_create_bundle — wants_advanced_warming: true with advanced_warming_terms or advanced_warming_terms_count.
tokportal_configure_bundle_warming_terms — Set the terms later on a count-only purchase (exactly the purchased number, one-shot).
tokportal_rewarm_account — New warming cycle on a delivered account: search_terms (3–30).
tokportal_list_account_warming_sessions — Sessions per account with per-term verification status.
tokportal_get_warming_session — Detail of one session (terms, verification, timestamps).
tokportal_create_webhook_endpoint — warming.session_started, warming.term_verified, warming.session_completed.

Prompt to paste

Evaluate this workflow in the TokPortal sandbox only.
Use the remote MCP endpoint https://app.tokportal.com/api/ext/mcp or local tokportal-mcp 1.15.1 or later for write tools.
Verify the installed local version before using its write tools. Version 1.15.0 is unsafe for simulations.
If the local version is older or unknown, use the remote endpoint or authenticated REST
requests with X-TokPortal-Dry-Run: true instead.
For every non-GET MCP tool call, set dry_run: true as a top-level boolean beside body.
For every REST write in a workflow, send the X-TokPortal-Dry-Run: true header.
Use normal read tools for existing real objects. Do not GET or poll synthetic IDs,
and do not upload files to simulated upload URLs. Simulated objects have no cross-call memory.
Show credits_would_charge and verify credits_charged is 0 for each simulated write.
Do not execute any live write. Ask for my explicit GO before the first real write,
including bundle creation, which charges immediately. After GO, repeat creation
without dry_run and use the new real IDs; never reuse synthetic IDs in live requests.

Use the TokPortal MCP tools. For account ACCOUNT_ID (TikTok), call generate_warming_terms with
text "budget K-beauty and skincare for oily skin", platform tiktok, count 6. Show me the terms,
let me edit them, then simulate rewarm_account with the final list and report credits_would_charge.
Do not look for a new session: a dry run creates none.

Paste the prompt in a Claude Code session; Claude Code shows each tokportal_* call and asks for approval on write tools. /mcp shows connection state.

REST equivalent (write requests below are simulations; GET requests read existing real data)

# Generate 6 terms
curl -X POST -H "X-TokPortal-Dry-Run: true" https://app.tokportal.com/api/ext/warming/generate-terms \
  -H "X-API-Key: sk_..." -H "Content-Type: application/json" \
  -d '{"text":"skincare for oily skin, budget K-beauty","platform":"tiktok","count":6}'

# Re-warm a delivered account
curl -X POST -H "X-TokPortal-Dry-Run: true" https://app.tokportal.com/api/ext/accounts/ACCOUNT_ID/rewarm \
  -H "X-API-Key: sk_..." -H "Content-Type: application/json" -H "Idempotency-Key: $(uuidgen)" \
  -d '{"search_terms":["oily skin routine","niacinamide serum","kbeauty haul","sunscreen for acne","double cleansing","drugstore skincare"]}'

# Read the proof
curl https://app.tokportal.com/api/ext/accounts/ACCOUNT_ID/warming-sessions -H "X-API-Key: sk_..."

Key parameters

Parameter	Values	Notes
`wants_advanced_warming`	boolean	Mandatory alongside the terms or the count — never inferred. Sending targets without it is refused with ADVANCED_WARMING_FLAG_REQUIRED, not charged and dropped. TikTok and Instagram only.
`advanced_warming_terms`	3–30 strings, 2–50 chars, count multiple of 3	Or advanced_warming_terms_count to configure later — one or the other, and a count that disagrees with the list fails with ADVANCED_WARMING_COUNT_MISMATCH. Send distinct terms: anything dropped as a duplicate or for its length fails the call with ADVANCED_WARMING_TERMS_REJECTED rather than shrinking what you buy.
`advanced_warming_terms_count`	3–30, multiple of 3	Unconfigured purchases auto-cancel and refund after 14 days.
`search_terms (rewarm_account)`	3–30, multiple of 3	One recorded, verified session per term.
`generate_warming_terms.text`	≤1000 chars	Terms come back in the same language.

Full schemas: OpenAPI reference · openapi.json.

Example configurations

Warmed Instagram account

{"bundle_type":"account_only","platform":"instagram","country":"FR","wants_advanced_warming":true,
 "advanced_warming_terms":["recette healthy","batch cooking","déjeuner rapide"]}

Count now, terms later

{"bundle_type":"account_and_videos","platform":"tiktok","country":"US","videos_quantity":9,
 "wants_advanced_warming":true,"advanced_warming_terms_count":9}

Rewarm before a campaign

{"search_terms":["running shoes review","marathon training","couch to 5k"]}

Credits

5 credits per target at the standard rate, minimum 3 targets (15 credits), maximum 30 per purchase; billed per target, never per day. Contract allowances may lower it — read get_credit_costs. See Credits & Pricing and Advanced Niche Warming.

Why not the official API

Official platform APIs expose no way to build an account's viewing history: there is no endpoint to search, watch or engage as the account. Warming only exists because a human holds the device. TokPortal makes that human step orderable, priced per term and verifiable through recorded sessions.

As of August 2026 the first-party routes look like this. TikTok's Content Posting API (Direct Post) requires each account owner to authorize your app with the video.publish scope, limits every user access token to 6 requests per minute, keeps all posts from unaudited apps in private viewing mode until TikTok audits the app, and enforces an unpublished daily post cap per user (spam_risk_too_many_posts) that integrators commonly report at roughly 15–25 posts per account per day. Meta's Instagram Content Publishing API allows 100 API-published posts per professional account in a 24-hour moving window and only for accounts you own and connect via OAuth. Neither creates accounts, warms them, or reports third-party bans. TokPortal is human-operated infrastructure: accounts created and run by managers in the target country, one X-API-Key for all of them, dated slots (max 3 per day per bundle) instead of per-account tokens.

Sources: TikTok Content Posting API – Direct Post, TikTok Content Posting API – Get started, Instagram Platform – Content Publishing.

Warm TikTok & Instagram accounts with Claude Code

Connect TokPortal to Claude Code

Try the workflow without spending

How it works

Run it from Claude Code

Key parameters

Example configurations

Credits

Why not the official API

FAQ

How do I know warming actually happened?

How many terms should I buy?

Can I warm an account that TokPortal did not create?

What happened to deep warming?

Also works with

Other jobs with Claude Code