
Backend-safe, copy-paste examples for collecting public social media data with
SocQ. The examples cover the shared task workflow and the current Instagram,
TikTok, YouTube, and Facebook endpoints.
- Create an API key.
- Copy
.env.example to .env.
- Set
SOCQ_API_KEY.
- Run a cURL, Node.js, or Python example.
- Store the returned
task_id, then poll GET /v1/tasks/{task_id} until the
task succeeds or fails.
cp .env.example .env
export SOCQ_API_KEY="your-api-key"
Never put a SocQ API key in browser code, mobile apps, public repositories,
screenshots, fixtures, or logs.
Every current submit endpoint has a focused repository with cURL, Node.js, and
Python examples, endpoint-specific behavior, production guidance, responsible
use notes, and synthetic fixtures.
The machine-readable inventory in
catalog/endpoints.json maps all 51 public endpoint
contracts to their focused repositories.
submit public-data task
|
v
store task_id
|
v
poll task status <---- callback is a notification, not a result payload
|
v
read data.results.items
|
v
follow data.results.next_cursor when data.results.has_more is true
Task states are queued, running, succeeded, and failed. Callback
delivery is best-effort, so production systems should keep polling as a
fallback.
catalog/ Public endpoint manifest and focused-repository metadata
curl/ Copy-paste HTTP requests
node/ Runnable Node.js examples
python/ Runnable Python examples
shared/ Reusable task clients
fixtures/ Synthetic response shapes used by checks and documentation
docs/ Production integration guidance
scripts/ Local and CI validation
SocQ is built for public social data workflows. It is not an official API of
Instagram, TikTok, YouTube, or Facebook and does not provide access to private
account data.
The MIT license covers the example code in this repository. It does not grant
rights to SocQ's hosted service, third-party platform data, trademarks, or
private product source code.