Multi Upload Tool API
66
AI ReadinessAI-Aware (B)66/100
Official vendor OpenAPI document · agent-readySocial MediaSocial PublishingapiKey58 EndpointsREST
For Agents
Publish or schedule video, photo, and text posts to TikTok, YouTube, Instagram, LinkedIn, X, and other connected accounts, run approval flows, and read per-account analytics.
Use for: Post this video to TikTok and YouTube at 6pm tomorrow, List all connected Instagram accounts, Check whether my scheduled LinkedIn post was published, Retry every failed upload from today
Not supported: Does not edit video, generate captions, run paid ads, or read platform inbox messages. Use for publishing, scheduling, approving, and tracking social posts across connected accounts only.
The Multi Upload Tool API publishes a video, photo, or text post once to one or many connected social accounts on TikTok, YouTube, Instagram, Facebook, LinkedIn, Pinterest, Bluesky, Threads, and X, immediately or on a schedule. Posts can be validated in a dry run, held as drafts or pending approval, approved or sent back for changes, rescheduled, and retried when they fail. The API also covers connected-account management, per-account daily publishing limits, analytics with on-demand sync, media pools, webhooks with delivery replay, team members and invites, white-label connection links, short links, and custom domains.
Install Jentic One Beta
Connect the Multi Upload Tool API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Multi Upload Tool 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%2Fmulti-upload-tool.com%2Fmulti-upload-tool" | 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%2Fmulti-upload-tool.com%2Fmulti-upload-tool" | 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 Multi Upload Tool API.
Publish a video, photo, or text post to one connected account or to many accounts in one bulk call
Schedule a post with schedule_date and reschedule or retry it later
Dry-run a post against each platform's rules before publishing
Hold posts as drafts or pending approval, then approve them or request changes
Check each connected account's daily publishing limits and platform capabilities
Read analytics across all connected accounts or for one account, and trigger an immediate sync
Subscribe webhooks to events such as upload.completed and upload.failed, and replay a delivery
Use Cases
Patterns agents use Multi Upload Tool API for, with concrete tasks.
★ AI social agent cross-posting a video
An AI agent asked to 'post this clip everywhere tomorrow morning' needs one call path instead of nine platform SDKs. Through Jentic the agent searches for 'publish a video to several social accounts', loads the Multi Upload Tool bulk upload operation with its input schema, and sends the accounts list, the video URL, a description, and a schedule_date, with the x-api-key token injected at call time. It then checks each upload's status to confirm the job was scheduled.
Call POST /upload/validate with accounts and a video URL, then POST /upload/bulk with the same accounts, a description, and schedule_date set to 2026-11-10T09:00:00Z
Client approval before publishing
An agency drafts posts for a client and needs sign-off before anything goes live. Posts created with status pending_approval are only published once approved, through the approve route or a client review link created for a set of uploadIds. A reviewer can instead request changes with a comment, which keeps the post unpublished.
Create a review link with POST /upload/review-links for three pending uploadIds, then call POST /upload/{id}/approve on each one the client accepts
Recovering failed uploads
Platform tokens expire and uploads fail. A monitor subscribed to upload.failed and connected_account.expired webhook events learns about failures as they happen, can list uploads filtered by status and platform, and can retry all failed uploads for an account or platform in one call once the account is reconnected.
Call GET /upload with status=failed and platform=instagram, then POST /upload/retry-failed with platform set to instagram
Weekly cross-account analytics report
A creator wants one report across every channel. The analytics overview aggregates every connected account and can be filtered by tags, while the per-account analytics route returns one account's figures, and a sync route refreshes an account immediately instead of waiting for the nightly pass.
Call POST /analytics/{connectedAccountId}/sync for each account, then GET /analytics/overview and summarise the week by platform
Key Endpoints
58 endpoints — the multi upload tool api publishes a video, photo, or text post once to one or many connected social accounts on tiktok, youtube, instagram, facebook, linkedin, pinterest, bluesky, threads, and x, immediately or on a schedule.
METHOD
PATH
DESCRIPTION
POST
/upload
Publish to one account
POST
/upload/bulk
Publish to many accounts
POST
/upload/validate
Validate a post as a dry run
GET
/upload/{id}
Get an upload
POST
/upload/{id}/approve
Approve a post
GET
/accounts
List connected accounts
GET
/analytics/overview
Analytics across connected accounts
POST
/webhooks
Create a webhook
POST
/upload
Publish to one account
POST
/upload/bulk
Publish to many accounts
POST
/upload/validate
Validate a post as a dry run
GET
/upload/{id}
Get an upload
POST
/upload/{id}/approve
Approve a post
GET
/accounts
List connected accounts
GET
/analytics/overview
Analytics across connected accounts
POST
/webhooks
Create a webhook
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.
M
Multi Upload Tool API
- AI-Aware (B)66/100
82
Foundational Compliance63
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience93
Agent Usability50
Security82
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
82
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
30%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
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.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
52%
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.
57%
Summary Coverage
Coverage of summaries across operations/tags/info.
93
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
93%
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).
82
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
82%
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 Multi Upload Tool by hand means sending a kmb_ token in x-api-key, handling the X-Team-ID header, presigning large media, and staying inside per-endpoint write limits. Through Jentic you install once, import Multi Upload Tool from the API Directory, store the token once, and your agent calls it.
Permission scoping
The target account for a new post travels in the request body, so rules bound which operations your agent may call, not which social account it posts to. You choose the operations it may call, so destructive ones like disconnecting an account or removing a team member are not included unless you add them.
Credential isolation
Your Multi Upload Tool token 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 'schedule a post to TikTok' or 'retry failed uploads', and Jentic returns the matching Multi Upload Tool operation with its input schema, including fields like accountId and schedule_date, so the agent builds a valid request.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Multi Upload Tool API through Jentic.
What authentication does the Multi Upload Tool API use?
Per its OpenAPI spec, every operation uses an API token sent in the x-api-key header, in the form kmb_ followed by 64 hex characters. Tokens carry scopes such as posts:read, posts:publish, or analytics:read chosen at creation, and an unscoped token can target a team with the X-Team-ID header. Through Jentic the token is held by your own instance and injected at call time.
What are the rate limits for the Multi Upload Tool API?
The OpenAPI spec states limits per IP and per endpoint group, returning 429 when exceeded: 50 requests per 15 minutes for POST /upload, and 20 requests per 15 minutes for POST /upload/bulk and destructive operations. Reads are typically 100 requests per 5 to 15 minutes, and one IP may present at most 10 distinct API tokens per hour.
How do I publish a video larger than 100 MB with the Multi Upload Tool API?
A file part sent to POST /upload must stay under 100 MB because of an edge limit. For larger media, call POST /upload/presign to get upload URLs, put the bytes into storage, then pass the returned bucketUrl or accessUrl in the video, photo, or file field of the upload request.
How do I schedule a post across several accounts through Jentic?
Search Jentic for 'publish a video to several social accounts', load the POST /upload/bulk operation, and execute it with the accounts list, the media, and a schedule_date. Check results with GET /upload/{id}. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Multi Upload Tool API?
Yes. Write a rule that allows only POST /upload/validate, GET /upload, and GET /accounts, and the agent can check drafts and read status but cannot publish, disconnect an account, or remove team members. You can pair that with a token holding posts:write but not posts:publish, so anything it creates is held for approval, and every call is logged.
Which platforms does the Multi Upload Tool API publish to?
The spec's Platform enum lists TikTok, YouTube, Instagram, Facebook, LinkedIn, Pinterest, Bluesky, Threads, and X. GET /platforms/capabilities returns what each platform supports, and text-only posts are accepted on Facebook, LinkedIn, Bluesky, and Threads.
GET STARTED