Reacherapp Reacher Data API
53
AI ReadinessFoundational (C-)53/100
Official vendor OpenAPI document · agent-readyMarketingMarketing AutomationapiKey347 EndpointsREST
For Agents
Rank TikTok Shop affiliate creators by GMV, find new creators with natural-language search, approve sample requests, reply to creator DMs, and run outreach and email automations for a Reacher-connected shop.
Use for: Find the top 20 creators by GMV for my shop over the last 30 days, I need to approve the qualifying sample suggestions from this week, Search for fitness creators with over 50000 followers who have an email on file, Reply to the creator who asked about commission rates
Not supported: Does not create TikTok Shop products, process customer orders, or publish videos to TikTok. Use for managing and measuring a TikTok Shop affiliate creator program only.
The Reacher Data API exposes a TikTok Shop brand's affiliate creator program: the creators promoting its products, the videos and live streams they post, the GMV each one drives, and the outreach that recruits them. Beyond reporting, it runs the program day to day, approving AI-suggested sample shipments, replying to creators in existing TikTok DM threads, creating outreach and email automations, and managing GMV Max campaigns, usage rights, and CRM tags. Natural-language creator search, P&L and finance reconciliation, and shop health metrics round out the surface, with every call addressed to one or more shops through the x-shop-id header.
Install Jentic One Beta
Connect the Reacher Data API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Reacher Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freacherapp.com%2Freacherapp" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freacherapp.com%2Freacherapp" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Reacher Data API.
Rank affiliate creators by lifetime GMV with POST /creators/list, or by GMV inside a date window with POST /creators/performance
Build a creator video leaderboard for a campaign window with total_video_gmv and total_units_sold per creator
Search the TikTok creator universe in plain language with POST /ai-search/creators, filtered by followers, engagement rate, GMV, and has_email
Approve or dismiss AI-suggested sample requests, up to 50 suggestion_ids per call, with an X-Dry-Run header to validate first
Reply to a creator inside an existing TikTok DM conversation with text, an image, or a product card
Create an email automation targeting a mailing list, creator search filters, or a CRM stage, with a daily send cap
Pull P&L summaries, finance statements, and payment reconciliation for the shop
Use Cases
Patterns agents use Reacher Data API for, with concrete tasks.
★ Affiliate program assistant through Jentic
A brand's agent can run the weekly affiliate routine: pull top creators, review the AI sample suggestions, and answer creator DMs. Through Jentic it searches by intent, receives the matching Reacher operation with its input schema, and calls it with the x-api-key and x-shop-id headers injected by your self-hosted Jentic One instance. Write operations such as sample approval accept X-Dry-Run, so the agent can validate a batch before it ships real samples.
Call GET /samples/suggestions, then POST /samples/suggestions/approve with all_qualifying true and the X-Dry-Run header set to true, and report which suggestions would be approved and which were skipped
Creator performance reporting
Affiliate managers need to know which creators actually sell. POST /creators/performance ranks creators by GMV earned inside a date range, defaulting to the last 30 days, while POST /creators/list reports lifetime GMV with filters such as min_followers, min_videos, and tags. POST /videos/leaderboard aggregates attributed video GMV per creator for a campaign window, optionally limited to product_ids.
POST /creators/performance with start_date '2026-10-01', end_date '2026-10-31', sort_by 'gmv', sort_dir 'desc', and page_size 20, then list each creator handle with its GMV
Creator discovery
Recruiting new affiliates starts with finding creators who fit the product. POST /ai-search/creators takes a natural-language query and filters such as min_followers, min_engagement_rate, categories, and has_email, and searches the creator table for the shop's region. Lookalike, transcript, and video search modes find creators similar to an existing top performer or who have mentioned a topic.
POST /ai-search/creators with query 'home fitness equipment reviews', min_followers 50000, and has_email true, then return the top ten creators
Creator outreach and messaging
Once creators are found, outreach runs through automations and DMs. POST /automations/email requires automation_name, email_account_id, subject, body, and selection_mode, where selection_mode targets a mailing list, search filters, or a CRM stage. For creators already in conversation, the reply operations send text, an image, or a product card into the existing TikTok thread; TikTok does not allow cold-opening a DM.
Call GET /email-accounts to choose an email_account_id, then POST /automations/email with automation_name 'Q4 recruit', subject, body, and selection_mode 'crm_stage' with the target stage
Key Endpoints
347 endpoints — the reacher data api exposes a tiktok shop brand's affiliate creator program: the creators promoting its products, the videos and live streams they post, the gmv each one drives, and the outreach that recruits them.
METHOD
PATH
DESCRIPTION
GET
/shops
List shops the key can access
POST
/creators/performance
Rank creators by GMV in a date range
POST
/videos/leaderboard
Creator video leaderboard
POST
/ai-search/creators
Natural-language creator search
POST
/samples/suggestions/approve
Approve AI sample suggestions
POST
/creator-messages/conversations/{creator_handle}/reply
Reply to a creator DM
POST
/automations/email
Create an email automation
GET
/account/limits
Resolved plan limits per shop
GET
/shops
List shops the key can access
POST
/creators/performance
Rank creators by GMV in a date range
POST
/videos/leaderboard
Creator video leaderboard
POST
/ai-search/creators
Natural-language creator search
POST
/samples/suggestions/approve
Approve AI sample suggestions
POST
/creator-messages/conversations/{creator_handle}/reply
Reply to a creator DM
POST
/automations/email
Create an email automation
GET
/account/limits
Resolved plan limits per shop
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
R
Reacher Data API
- Foundational (C-)53/100
66
Foundational Compliance58
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience43
Agent Usability50
Security88
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
66
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
89%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
58
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
83%
Example Validity
Percentage of examples that conform to their schemas.
48%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
32%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
53%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
88
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
88%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Reacher by hand means sending both the x-api-key and x-shop-id headers, switching between single-shop and multi-shop calls, and adding Idempotency-Key and X-Dry-Run headers on writes. Through Jentic you install once, import the Reacher Data API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Reacher carries the shop in a header rather than the URL path, so rules bound which operations your agent may call, not which shop. Where a target sits in the path, such as the creator handle on DM replies or the campaign id on GMV Max metrics, a rule can narrow the agent to that one creator or campaign. You choose the operations it may call, so ones that ship samples or send messages are not included unless you add them.
Credential isolation
Your Reacher API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'top creators by GMV' or 'approve sample suggestions', and Jentic returns the matching Reacher operation with its input schema so the agent picks the right one without paging through hundreds of operations.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Reacher Data API through Jentic.
What authentication does the Reacher Data API use?
Per its OpenAPI spec, the Reacher Data API uses two header values together: your API key in `x-api-key` (keys start with rk_live_) and the shop to query in `x-shop-id`. The shop header accepts one shop id, a comma-separated list, or 'all', but detail endpoints need a single shop. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Is there a Reacher MCP server?
You don't need an MCP server to give your agent the Reacher Data API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls it. With this many operations, on-demand discovery matters: the agent loads only the operation it is about to call instead of every tool definition.
Can I limit what my agent is allowed to do with the Reacher Data API?
Yes. A reporting agent could get a rule that allows only POST /creators/performance, POST /videos/leaderboard, and GET /shops, so it can rank creators but cannot approve samples, send DMs, or start automations. Every call it makes is logged.
Can I test a write operation without it taking effect?
Yes, on the operations that declare it. Sample approval, DM replies, and email automation creation accept an X-Dry-Run header that validates and echoes the request without acting, and they take an Idempotency-Key header so a retried call is not applied twice. Approving sample suggestions without a dry run ships real samples.
What is the difference between creators list and creators performance?
POST /creators/list reports each creator's lifetime GMV for the shop, with filters such as min_shop_gmv, min_followers, and tags. POST /creators/performance ranks creators by GMV earned within a date range, defaulting to the last 30 days, and matches the dashboard's Top Creators section.
What are the rate limits for the Reacher Data API?
The OpenAPI spec mentions a separate write rate limit but does not state the numbers. GET /account/limits returns the plan limits in force for each shop for CRM, automations, and email automations, which helps size a batch. Check https://docs.reacherapp.com for current request limits.
How do I rank my top creators through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Reacher Data API from the API Directory, and store your API key and shop id. Your agent searches for 'top creators by GMV', receives POST /creators/performance with its input schema, and calls it with your date range. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED