Reoogle API Reference
Programmatic access to Reoogle's database of 25,000+ monitored subreddits. Filter by activity, posting safety, mod status, member count, and language — or use /postable to instantly surface communities where you can drop links without them being removed.
Base URL
https://reoogle.com/api/v1
Protocol
HTTPS only
Format
JSON
Auth
Bearer token
Rate limit
60 req / min
What builders are creating
Click any card to see the full guide with code examples.
Auto-Post Content Daily
Build a zero-touch content calendar that posts to the best communities every day — no manual work required.
Link-Drop Traffic Pipeline
Find subreddits where promo posts survive. Schedule links with UTM tracking and watch qualified traffic arrive.
Competitor Mention Intel
Get notified the moment a competitor is discussed on Reddit. Reply before they do and capture the lead.
Mod-Free Sub Alerts
Webhook fires the instant mods go inactive. Your automation posts first, before any competition shows up.
AI Content Campaigns
Generate, review, and approve Reddit posts programmatically via API or Zapier — no dashboard ever needed.
Market Research Engine
Map which of 25k+ subreddits contain your ideal buyers. Filter by category, activity, and language.
Multi-Client Agency Tool
Run full Reddit campaigns for multiple clients under one roof. Separate API keys, isolated data, total control.
Product Launch Blast
Pre-schedule posts to 50+ subreddits before launch day. Time the wave and maximise launch-day visibility.
Engagement Spike Monitor
Track activity trends in your target communities. Catch engagement spikes and post into momentum.
Reddit Inbox as CRM
Pull replies, DMs, and mentions via API. Pipe them into your CRM and convert Reddit conversations to leads.
Viral Post Analytics
Track score, upvote ratio, and comment velocity across all your posts. Double down on what resonates.
Image Campaign Scheduler
Upload product screenshots once via API, reuse across campaigns. Visual posts drive 2× more click-throughs.
Introduction
The Reoogle API is a REST interface that gives you programmatic access to our database of 25,000+ monitored subreddits. Query by moderator activity status, membership size, category, engagement patterns, and posting safety — or use the /postable shortcut to instantly surface communities where links survive.
All endpoints return JSON. All requests must be made over HTTPS. Authentication is via a Bearer token included in the Authorization header. The API follows predictable RESTful conventions — standard HTTP verbs, consistent error envelopes, and cursor-free pagination.
Every subreddit in the database is continuously refreshed. The last_checked and activity_checked_at timestamps on each record tell you exactly how fresh the data is.
New to the API? Jump to Integration Examples to see real-world usage patterns in Node.js, Python, and Next.js before reading the full reference.
Authentication
Every request to a data endpoint must include an API key as a Bearer token in the Authorization header. Generate and manage keys from your Developer dashboard. Keys are prefixed with rog_live_ so they are easy to identify in logs.
Authorization: Bearer rog_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxKey security & storage
The full key is shown only once, immediately after creation — copy it to a secure location such as a password manager or secrets vault. Reoogle stores only a SHA-256 hash of the key; the plaintext cannot be recovered after that initial display. If a key is compromised, revoke it immediately from the dashboard and generate a replacement.
Never expose API keys in client-side JavaScript, public git repositories, or browser requests. Always keep keys in server-side environment variables. If you accidentally commit a key, revoke it immediately.
Verify your key works
The fastest way to confirm a key is valid is to call the /me/usage endpoint. A 200 response means the key is active and you are authenticated. A 401 means the key is missing, malformed, or revoked.
# Verify your key with a minimal request
curl https://reoogle.com/api/v1/me/usage \
-H "Authorization: Bearer rog_live_xxxxxxxxxx"
# Expected 200 response:
# { "key_name": "Production", "limits": { ... }, "recent_requests": [...] }Rate Limiting
Each API key is subject to two independent limits:
Per-minute limit
60 requests / min
Resets every 60-second window
Per-day limit
1,000 requests / day
Resets at 00:00 UTC
Limits are tracked per key, not per account or IP address. Every response includes rate-limit headers so your client can proactively back off before hitting the limit:
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 58
X-RateLimit-Reset: 1750000000 # Unix timestamp when the 60s window resets
X-RateLimit-Daily-Limit: 1000
X-RateLimit-Daily-Remaining: 952When either limit is exceeded, the API returns 429 Too Many Requests and includes a Retry-After header (in seconds) indicating how long to wait. In production, always implement exponential back-off rather than polling at a fixed interval: