DropReply CLI — Publish Replies from Your Terminal

Installation

One command to get started

Install the CLI globally with npm, then authenticate with your API key.

$ npm install -g @dropreply/cli

Terminal

# Set your API key
$ export DROPREPLY_API_KEY=drpl_live_your_api_key

# Publish a reply on Reddit
$ dropreply reply \
    --platform reddit \
    --url "https://reddit.com/r/webdev/comments/abc123/..." \
    --content "Great question! I've been using Next.js for this exact use case..."

Reply Submitted
ID:        rpl_7f3a9b2c
Status:    queued

# Check the reply status
$ dropreply status rpl_7f3a9b2c

ID:        rpl_7f3a9b2c
Status:    published
Platform:  reddit

Commands

Everything you need in the CLI

Manage your entire reply workflow from the command line.

dropreply reply

Publish a new reply. Specify platform (reddit or twitter), target URL, and content. Returns a reply ID for tracking.

dropreply status

Check the status of a reply by ID. See if it's queued, publishing, published, or failed with error details.

dropreply replies

List your recent replies with status, platform, and timestamps. Supports filtering by platform and status.

dropreply accounts

Check available managed accounts by platform. See how many Reddit and Twitter accounts are ready.

dropreply usage

View your current usage stats for the billing period. Replies used, remaining quota, and plan details.

dropreply upvote

Submit an upvote/like job. Specify platform and target URL to boost visibility on Reddit or X.

Use Cases

Works everywhere scripts run

Integrate reply publishing into any workflow that supports shell commands.

CI/CD Pipelines

Publish replies as part of your deployment pipeline. Announce releases, respond to feedback, or share updates automatically after each deploy.

Cron Jobs

Schedule reply publishing with cron. Run at specific times for maximum engagement, or set up periodic health checks on your published replies.

Shell Scripts

Compose complex workflows in bash. Chain reply creation with content generation, or batch process replies from a CSV file.

Monitoring

Script health checks for your published replies. Alert on failures, track success rates, and ensure your content stays live.

Local Development

Test reply publishing during development. Use test API keys to validate content and format before going live.

Automation Hooks

Trigger replies from webhooks, GitHub Actions, Zapier CLI, or any automation tool that can execute shell commands.

Example

Batch replies from a script

Combine CLI commands with shell scripting for powerful automation.

publish-replies.sh

#!/bin/bash
# Publish replies to multiple Reddit threads

URLS=(
  "https://reddit.com/r/SaaS/comments/abc123/best-tools-for-outreach"
  "https://reddit.com/r/startups/comments/def456/how-do-you-handle-marketing"
  "https://reddit.com/r/webdev/comments/ghi789/what-apis-are-you-using"
)

for url in "${URLS[@]}"; do
  REPLY_ID=$(dropreply reply \
    --platform reddit \
    --url "$url" \
    --content "We built an API for this exact use case..." \
    --json | jq -r '.id')

  echo "Queued: $REPLY_ID for $url"
done

# Check usage after batch
dropreply usage

Publish Replies from Your Terminal