Overview - CLI Usage
Agentic CLI workflows — social posts, integrations, analytics, media upload, and directory launch commands.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
What is in this section
Operational reference for the openquok CLI grouped by command verb. Social pages cover posts:*, integrations:*, analytics:*, and upload helpers that feed posts:create.
Directory pages cover directory:* for product profiles, variants, and listing readiness.
For install and auth, start at Get Started. For copy-paste recipes per network or launch site, see CLI Examples.
Social scheduling and channels
Note
Directory launch commands prepare your product on My Products for sites such as PeerPush and Uneed. They use directory:* verbs, not posts:create. You submit on the directory site with the browser extension.
Tip
Your main product profile is the default product record. A directory variant is optional per-site copy. Use directory:profiles:list --main-only when you need the main id before directory:variants:ensure.
Directory launch
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.