Job board automation from your terminal
Turn repetitive job board work into a command
Replace dashboard checklists and one-off curl commands with first-party commands your team can review, reuse, and run anywhere.
Reviewable automation
Works in CI
Structured results
Make recurring work repeatable
Replace dashboard checklists and one-off curl commands with first-party commands your team can run, review, and reuse.
Find the exact command
Start from a first-party command instead of translating API documentation into another wrapper.
cavuno jobs --help
Make the action explicit
Keep every operation readable in shell history, scripts, and code review.
cavuno jobs publish job_123
Reuse the result
Feed structured output into the rest of your workflow instead of starting the next task by hand.
cavuno jobs get job_123 | jq .status
The right interface for the task
Keep the terminal when explicit steps matter
Use the CLI for reviewable scripts, local files, CI, and operations that should run the same way every time.
Run the whole operation without opening the dashboard
Use one consistent command surface for jobs, companies, content, infrastructure, and the operational checks that keep automation dependable.
Run the board
Create, inspect, update, publish, pause, expire, and delete core records.
Manage infrastructure
Keep domains, taxonomies, and local file uploads in one workflow.
Operate safely
Check limits, follow long-running work, and leave an auditable trail.
cavuno jobs list \--status published \--format json \| jq -r '.data[]| select(.expiresAt != null)| select((.expiresAt | sub("\\.[0-9]+Z$"; "Z") | fromdateiso8601) < now)| .id' \| xargs -n 1 cavuno jobs expire
Turn commands into dependable workflows
Feed structured results into the tools already in your pipeline, keep failures visible, and investigate any run without guessing what happened.
Pipe structured results into the tools you already use
Review bulk changes before they run
Catch command failures and inspect every batch result
Write it once. Run it wherever the work happens.
Start locally, then move the same readable commands into a shell script or CI runner when the workflow is ready to run itself.
npm install -g cavunoexport CAVUNO_API_KEY='cavuno_live_...'cavuno jobs publish job_123{"object": "job","id": "job_123","status": "published"}
Automate your next recurring board task
Install the Cavuno CLI, run the task once, then keep the command for every time it comes back.