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.