Postiz is a bundled OAuth2 provider in authsome. Postiz social posting and scheduling APIs.Documentation Index
Fetch the complete documentation index at: https://authsome.agentr.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
At a glance
| Provider name | postiz |
| Display name | Postiz |
| Auth type | OAuth2 |
| Default flow | device_code, headless |
| PKCE supported | Yes |
| Device code supported | Yes |
| DCR supported | No |
| Default scopes | (none) |
| Proxy host | api.postiz.com |
Env var (access_token) | POSTIZ_ACCESS_TOKEN |
| Provider docs | Link |
Prerequisites
Postiz uses the device authorization grant. No callback URL is registered. You enter a short code on a separate device after runningauthsome login.
Log in
Multiple accounts
Pass--connection <name> on login and on every read command to keep two or more accounts on the same provider side by side. See Multiple connections per provider for the full pattern.
Use the token
Run the agent under the proxy. The library tab is for embedding authsome inside a larger Python orchestrator.POSTIZ_ACCESS_TOKEN=authsome-proxy-managed in the child’s environment and injects the real token into outbound requests to api.postiz.com. The child process never sees the actual value. Refresh tokens are never exported.
Override the bundled definition
What’s next
Headless setup
Postiz is the only bundled provider that defaults to the device code flow.
Run agents with the proxy
Inject the access token into outbound requests without exposing it.