Official vendor OpenAPI document · agent-readySocial MediaSocial PublishingapiKey38 EndpointsREST
For Agents
Create and schedule one post across X, LinkedIn, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky, Mastodon, and Telegram, attach media, and track its publishing status. Also reads LinkedIn, Mastodon, and Bluesky analytics and manages webhooks.
Use for: Schedule this announcement on LinkedIn and Bluesky for 9am tomorrow, I need to post the same update to X, Threads, and Mastodon now, Check whether my scheduled Instagram post was published, List all failed posts from last week
Not supported: Does not handle paid social advertising, social listening across public accounts, or direct messages. Use for scheduling and publishing posts to your own connected accounts and reading their analytics only.
The Publora API schedules and publishes social media posts to X/Twitter, LinkedIn, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky, Mastodon, and Telegram from one request. A post names the connected platforms, its content, an optional scheduledTime, per-platform settings, a first comment, and up to 10 media URLs, and you can track its status and publishing logs afterwards. It also reads LinkedIn post, account, and follower analytics plus Mastodon and Bluesky statistics, works LinkedIn reactions, comments, and reshares, and sends webhooks when posts are scheduled, published, or fail.
Install Jentic One Beta
Connect the Publora API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Publora 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%2Fpublora.com%2Fpublora" | 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%2Fpublora.com%2Fpublora" | 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 Publora API.
Create a post for several connected platforms at once, as a draft or scheduled for an ISO 8601 scheduledTime
Make post creation retry-safe with an Idempotency-Key header
Attach images and video by public URL, or upload through a pre-signed URL and finalize the file, plus custom Instagram Reel covers and YouTube thumbnails
Check a post's status and its publishing logs, and list posts filtered by status, platform, and date range
Read LinkedIn post, account, follower, and profile analytics, and Mastodon and Bluesky post and profile statistics
Add LinkedIn reactions such as LIKE or PRAISE, comment on posts, and reshare an existing post
Subscribe webhooks to post.scheduled, post.published, post.failed, and post.demoted events
Use Cases
Patterns agents use Publora API for, with concrete tasks.
★ Agent-scheduled cross-platform posting
An AI agent drafting social content can check the live per-platform limits, list the connected accounts, and create one Publora post that targets LinkedIn, X, and Bluesky with a scheduledTime. Sending an Idempotency-Key with the request means a retried call after a timeout does not publish the post twice, and the publishing logs show exactly what happened on each platform.
Get platform connections, then create a post with content 'We just shipped v2' for the linkedin and bluesky connection IDs, scheduledTime 2026-11-13T09:00:00Z, and a UUID Idempotency-Key
LinkedIn engagement and analytics
Creators and small teams track how LinkedIn posts perform and respond to them in the same workflow. Publora reads post statistics by postedId, aggregated account statistics over a dateRange, follower statistics, and a profile summary, and it can add a reaction, post a comment, or reshare a post with commentary, so an agent can report and engage without opening LinkedIn.
Get LinkedIn post statistics for a postedId and platformId, then add a reaction with reactionType PRAISE to that post
Publishing failure alerts
Scheduled posts can fail when a token expires or media is rejected. A webhook subscribed to post.failed and post.published lets an integration react the moment a post lands or breaks, and the post logs operation returns the per-platform publishing log for diagnosis, while the test-connection operation checks whether a platform account is still healthy.
Create a webhook named failures with url https://hooks.example.com/publora and events post.failed and post.published
Key Endpoints
38 endpoints — the publora api schedules and publishes social media posts to x/twitter, linkedin, instagram, threads, tiktok, youtube, facebook, bluesky, mastodon, and telegram from one request.
METHOD
PATH
DESCRIPTION
POST
/create-post
Create and schedule a post
GET
/get-post/{postGroupId}
Get post details and status
PUT
/update-post/{postGroupId}
Edit a draft or scheduled post
GET
/list-posts
List posts with filters
GET
/platform-connections
List connected social accounts
GET
/platform-limits
Get live per-platform posting limits
POST
/get-upload-url
Get a pre-signed media upload URL
POST
/linkedin-post-statistics
Get LinkedIn post analytics
POST
/create-post
Create and schedule a post
GET
/get-post/{postGroupId}
Get post details and status
PUT
/update-post/{postGroupId}
Edit a draft or scheduled post
GET
/list-posts
List posts with filters
GET
/platform-connections
List connected social accounts
GET
/platform-limits
Get live per-platform posting limits
POST
/get-upload-url
Get a pre-signed media upload URL
POST
/linkedin-post-statistics
Get LinkedIn post analytics
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.
P
Publora API
- AI-Aware (B)65/100
85
Foundational Compliance76
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability50
Security82
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
85
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
96%
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).
42%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
76
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
34%
Example Density
How richly the API is illustrated with examples.
99%
Example Validity
Percentage of examples that conform to their schemas.
72%
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.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
42%
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.
35%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
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 Publora by hand means attaching its x-publora-key header, looking up platform connection IDs, and adding Idempotency-Key headers so retries do not double-post. Through Jentic you install once, import Publora from the API Directory, store the key once, and your agent calls it.
Permission scoping
Publora puts the post group id in the URL path (/get-post/{postGroupId}, /update-post/{postGroupId}), so a rule can pin your agent to one post for edits, while the target platforms ride in the request body. You choose the operations it may call, so destructive ones like post deletion or webhook secret regeneration are not included unless you add them.
Credential isolation
Your Publora 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 'schedule a social media post' or 'get LinkedIn post analytics', and Jentic returns the matching Publora operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Publora API through Jentic.
What authentication does the Publora API use?
The Publora API authenticates with an API key in the x-publora-key header, per its OpenAPI spec, using a key from Settings > API Keys in the format sk_timestamp.hexstring. Workspace calls can also pass an x-publora-user-id header to act for a managed user. Through Jentic the key is stored once and injected at call time, so it never appears in your agent's prompt or logs.
Which platforms can I post to with the Publora API?
The spec lists X/Twitter, LinkedIn, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky, Mastodon, and Telegram. POST /create-post takes an array of platform connection IDs in the format platform-platformId, which you get from GET /platform-connections.
What are the rate limits for the Publora API?
The spec documents one limit: media URL ingestion allows 60 URLs per fixed one-hour window and returns 429 past it, with the pre-signed upload flow as the alternative. It does not state a general request limit, so check https://publora.com for current plan limits.
How do I schedule a post with the Publora API through Jentic?
Search Jentic for 'schedule a social media post', which returns POST /create-post with its input schema, then send content, the platforms array, and a scheduledTime in UTC. Omit scheduledTime to save a draft. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I avoid duplicate posts when a request is retried?
Yes. POST /create-post, PUT /update-post/{postGroupId}, and POST /attach-media/{postGroupId} accept an optional Idempotency-Key header. Send the same unique value on a retry and Publora returns the original result instead of creating a second post.
Is there a Publora MCP server?
You don't need an MCP server to give your agent the Publora API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, finding the posting and analytics operations by intent instead of loading all of them into context.
Can I limit what my agent is allowed to do with the Publora API?
Yes. Write a rule that allows only POST /create-post, GET /get-post/{postGroupId}, and GET /platform-connections, so the agent can draft, schedule, and check posts but cannot delete posts, comment or react on LinkedIn, or manage workspace users, and every call it makes is logged.
GET STARTED