Schedule posts with Postiz
Use the Postiz social-media scheduler to plan and publish Mouve posts and threads.
Postiz is an open-source social-media scheduler. Mouve ships a Postiz provider so you can plan Mouve posts on the same calendar as your other channels.
Availability
The Mouve provider is developed alongside this API and is not in a public Postiz release. It ships as a Mouve-maintained Postiz image built from upstream plus the provider; Mouve runs that image against its own account first. A contribution to upstream Postiz is planned but nothing here depends on it landing.
What it supports
| Capability | Notes |
|---|---|
| Text posts | The Postiz composer caps Mouve at 2,000 characters |
| Threads | Postiz "comments" become Mouve replies to the scheduled post |
| Audience | Scheduled posts publish as everyone — the only audience that yields a public permalink |
| Images | Not yet. See Images below |
| Video | Not supported, and refused before anything is published |
After publishing, Postiz links the live post's permalink
(https://mouve.it/<username>/post/<id>). Mouve computes that URL and returns
it on create — the provider never assembles one itself, so a later username
change cannot leave Postiz holding a dead link.
How the connection works
Connecting Mouve as a Postiz channel is a standard
OAuth 2.1 authorization requesting two scopes:
profile.read (to show which account is connected) and posts.write (to
publish). Media uploads ride posts.write — no extra scope. If you untick one
on the consent screen, the connection fails immediately rather than half-working
until the first publish.
You can disconnect the channel at any time from your Mouve settings, which revokes access immediately.
Images
Mouve's media endpoint is not part of this release, so a scheduled post with an image cannot publish yet. The provider fails it with
This Mouve API does not accept images yet — POST /public/v1/media is not available on it. Schedule the post without images to publish the text, or add the image from the Mouve app.
and publishes nothing — your text does not go out silently missing its picture. Remove the image and the post publishes normally.
When the endpoint ships, images will work with no change on the Postiz side: up to 5 per post (1 per reply), attached by URL. Watch the changelog.
Behavior worth knowing
- Retries are safe. The provider sends an
Idempotency-Keyderived from the Postiz post id — the same key on every attempt at the same scheduled post. A retried publish returns the original post instead of creating a second one. - Threads and time. Access tokens live one hour; keep the cumulative delay across a thread's replies under ~50 minutes so the whole thread publishes on one token. Every reply attaches to the original post, not to the reply before it — Mouve threads are one level deep.
- Moderation applies to API posts exactly as to posts made in the app — a published post can be removed after the fact, after which its permalink returns 404.
- Private profiles: a scheduled
everyonepost from a private profile is rejected with422 AUDIENCE_UNAVAILABLErather than published invisibly. Postiz surfaces Mouve's own explanation on the queue item. - Rate limits and outages are retried with backoff; a permission problem
(
403) is reported without disconnecting the channel. Only an expired or revoked token (401) makes Postiz re-authenticate.
Building your own integration instead?
Everything the Postiz provider uses is the plain public API:
GET /public/v1/me and POST /public/v1/posts. The
quickstart covers the same flow in three curl commands.