Overview - CLI Usage
Agentic CLI workflows for managing posts, integrations, analytics, and media uploads.
1 min read
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
What is in this section
Operational recipes for the openquok CLI grouped by command verb. For one-off setup (install, auth) start at Get Started; for end-to-end social platform recipes see CLI Examples.
Managing Posts
List, create, find slots, delete, and reconnect missing posts
Integrations
Discover connected channels, settings schemas, and dynamic tools
Global Plugs
Catalog, list, upsert, activate, and delete channel-level engagement rules
Analytics
Platform-level and per-post analytics over a 7 / 30 / 90 day window
Media Upload
Upload local files (`upload`) or mirror a public URL (`upload-from-url`); both return the ids you pass to posts:create
Conventions used in these pages
- All commands print machine-readable JSON, so every example can be piped through jq.
- Sample IDs in command examples use kebab-case angle-bracket placeholders — <integration-id>, <post-id>, <post-group-id>, <media-group-id>, <customer-group-id>. Substitute real ids from openquok integrations:listopenquok posts:list, or the response of openquok upload before running. When an example needs two distinct ids of the same kind, the suffix form is used: <integration-id-1>, <integration-id-2> (or descriptive variants like <threads-integration-id-1>).
- ISO-8601 timestamps with an explicit Z (UTC) or offset are required — the backend rejects timezone-less strings.
- Authentication is shared across every command (stored credentials, then OPENQUOK_API_KEY). Cover this once on CLI authentication.