Add scheduling faster
Give your app a social calendar without building a new queue and timer for each social network.
Let users plan posts without making your team build 10 schedulers. Send the content, publish time, and time zone. Mallary handles the queue and each platform API.
Mallary gives your app one schedule while it handles the hard work behind the scenes.
Give your app a social calendar without building a new queue and timer for each social network.
Send a date, time, and time zone. Mallary saves the publish time in UTC and keeps the original time zone.
Get one job for each platform. See what is waiting, what went live, and what needs your help.
Use an exact UTC time when your app already did the math. Or send the time your user picked and their time zone. Mallary will turn it into the right queue time.
"scheduled_at": "2026-08-01T18:00:00Z"
"scheduled_at": "2026-08-01T14:00",
"scheduled_timezone": "America/New_York"
fetch('https://mallary.ai/api/v1/post', {
method: 'POST',
headers: {
'Authorization': 'Bearer YOUR_API_KEY',
'Content-Type': 'application/json'
},
body: JSON.stringify({
platforms: ['facebook', 'instagram', 'linkedin'],
message: 'Our new feature goes live today.',
media: [{
url: 'https://files.mallary.ai/launch.mp4'
}],
scheduled_at: '2026-08-01T14:00',
scheduled_timezone: 'America/New_York'
})
})
Your app sends the plan. Mallary waits, runs each platform job, and reports the result.
Pick one or more connected platforms. Add your message, media, and any platform options.
Send one exact timestamp, or send a local time with an IANA time zone such as America/New_York.
Check each job, list grouped posts, or use webhooks. Delete a pending grouped post before publishing starts.
Use a UTC or offset timestamp when your app already knows the exact moment.
Use a local wall-clock time and an IANA time zone when the audience cares about local time.
Schedule one post across many platforms and keep all platform jobs in one group.
Change captions, titles, post types, and other supported options for each destination.
Delete a grouped post while it is still waiting and publishing has not started.
React when a post is scheduled, published, partly published, or failed.
Short answers about publish times, time zones, jobs, and plans.
A social media scheduling API lets your app set a future time for a social post. The API saves the post, waits for that time, and then sends it to each chosen social platform.
Send your normal POST /api/v1/post request and add scheduled_at. You can send an exact timestamp with a time zone offset, or pair a local time with scheduled_timezone.
You can send a local date and time with an IANA time zone such as America/New_York. Mallary turns it into UTC for the queue and returns the original scheduled_timezone when you read the grouped post.
Yes. Add any supported connected platforms to the platforms array. Mallary creates one job for each platform and keeps them together as one grouped post.
Yes. Call DELETE /api/v1/posts/{id} while the grouped post is still pending and publishing has not started.
Check GET /api/v1/jobs/{id}, list grouped posts, or listen for webhooks. Finished jobs include a platform post ID and public URL when the platform provides them.
Scheduling is included with Starter, Pro, and Business plans. Paid plans can be tried free for 14 days.
Connect the accounts, copy your API key, and schedule your first multi-platform post.