Every channel on one rundown.
Plan, approve and publish to YouTube, Instagram, TikTok, X and Facebook from one calendar, or cue posts from your own content pipeline through the REST API.
Behind the scenes, part 2
Live Q&A reminder
Launch teaser
Launch day reel
Carousel: the details
Unboxing in 30 seconds
How it's made
Thread: what's new
It's live
Event: open studio
Launch recap
Plan once, adapt per platform.
Write a post once. Amaposta knows which platforms show a title, where hashtags go and how each one counts characters, so every channel gets a version that fits. When one channel needs its own words, write an override for just that channel.
The post you write
- Title
- How we roast a batch in 12 minutes
- Description
- From green beans to first crack in 12 minutes. We filmed one batch start to finish, including the part where it almost burns.
- Hashtags
- coffee behindthescenes
- Video
- batch-142.mp4 0:58
-
YouTube Title and description
How we roast a batch in 12 minutes
From green beans to first crack in 12 minutes. We filmed one batch start to finish, including the part where it almost burns.
Tags coffee behindthescenes
-
Instagram Caption only
From green beans to first crack in 12 minutes. We filmed one batch start to finish, including the part where it almost burns. #coffee #behindthescenes
Instagram has no title field, so the title stays out of the caption.
-
X Written for X 101/280
Batch 142 is out: green beans to first crack in 12 minutes, start to finish. #coffee #behindthescenes
Counted the way X counts: links as 23, emoji as 2, hashtags included.
Checks before 9:00, not after.
Every rule Amaposta knows about a platform is checked while you write: file types and sizes, video length, aspect ratio, character counts, missing titles and channels that need attention. A post with errors can't be scheduled, so you fix it at your desk instead of reading a failure email at 9:01.
Each message says what to change, and the same checks run on posts that arrive through the API.
Before you schedule
3 errors, 1 warning
-
Instagram accepts JPEG files; this one is PNG.
Media
-
Post is 312/280 characters on X including hashtags. Shorten it by 32 or write a version just for X.
Text
-
YouTube needs a title.
Title
-
TikTok's connection expires soon. Reconnect to avoid a missed post.
Channel
Fix the errors to schedule this post.
Review inbox
2 waiting-
Launch day reel
API key Content pipeline
In review Tue 09:00 -
Behind the scenes, part 3
Generated by your pipeline
In review Wed 17:30 -
Thread: launch questions
Written by an editor
Changes requested Link the pricing page in the last post.
A review inbox for people and pipelines.
Turn on approvals for a project and posts wait in the review inbox until an admin approves them. Approving keeps the scheduled time; asking for changes sends the author your note.
API keys follow the same rule. A key without the posts:publish scope can create and schedule posts, but they land in review first. That makes it safe to let an AI pipeline write drafts while a person keeps the final say.
Connections that don't quietly die.
Tokens refresh in the background before they lapse. When a platform needs someone to sign in again, you hear about it seven days ahead, not after a missed post. Failures come in plain English with a Retry button.
-
Connected
YouTube
Access tokens last 1 hour and renew automatically.
-
Connected
Instagram
Tokens last 60 days and renew automatically while the channel is in use.
-
Expires in 6 days
TikTok
Access tokens last 24 hours; refresh tokens last a year.
-
Connected
X
Access tokens last 2 hours and renew automatically.
-
Reconnect needed
Facebook
Page tokens don't expire unless the person who connected loses access.
Delivery failed
FailedYour endpoint returned 503 Service Unavailable.
Amaposta will retry with backoff.
Client reconnect links
When the account belongs to a client, send them a link. They sign in with the platform itself and the channel is back, without an Amaposta account and without sharing a password.
Built for your own pipeline.
Everything in the calendar is available over a REST API. Upload media or pass a URL, create a post with per-channel overrides and let the queue pick the next free slot. Retries are safe with an Idempotency-Key, and signed webhooks tell your systems when a post goes live or fails.
Create a video post and add it to the queue
curl "$AMAPOSTA_URL/api/v1/projects/$PROJECT_ID/posts" \
-H "Authorization: Bearer $AMAPOSTA_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: batch-142" \
-d '{
"kind": "video",
"title": "How we roast a batch in 12 minutes",
"description": "We filmed one batch start to finish.",
"hashtags": ["coffee", "behindthescenes"],
"media_url": "https://cdn.example.com/batch-142.mp4",
"schedule": { "mode": "queue" }
}'Webhook events
-
post.createdA post was created (dashboard or API) -
post.scheduledA post was scheduled -
post.approvedA post was approved -
post.publishedA post went live on a channel -
post.failedA post failed to publish on a channel -
channel.connectedA channel was connected or reconnected -
channel.disconnectedA channel lost its connection -
media.readyAn upload finished processing -
media.failedAn upload couldn't be processed
Start free, grow by channel.
Sandbox channels are free on every plan, so you can try the whole flow before connecting a real account.
-
Starter
For trying Amaposta and personal brands.
1 project, 3 channels, 30 scheduled posts a month, Visual calendar, Upload API, Sandbox channels
$0
-
Pro
For creators and small teams publishing every day.
5 projects, 15 channels, 3 team members, Unlimited posts, Approval workflow, Outbound webhooks, Client reconnect links
$24 a month, billed yearly
-
Agency
For agencies running many brands for clients.
Unlimited projects, 60 channels, 15 team members, Everything in Pro, Priority support
$82 a month, billed yearly
Put your next post on air.
Connect a sandbox channel, schedule a post and watch it go out. It takes about two minutes, and nothing leaves Amaposta until you connect a real account.