Social data, ready for your code.

Collected social posts and Google Trends, through the same TickerTrends backend you already know. Two endpoints. Pay as you use them.

  1. 01Create an account
  2. 02Add credits
  3. 03Make a request
curl --get 'https://social.staging.tickertrends.io/api/public/social-posts' \
  -H 'X-API-Key: YOUR_API_KEY' \
  -H 'Idempotency-Key: social-page-001' \
  --data-urlencode 'term=openai' \
  --data-urlencode 'platforms=tiktok' \
  --data-urlencode 'limit=20'

Keep your API key on your server. Send it with the X-API-Key header.

Social posts

1 credit / post delivered

Retrieve indexed TikTok, X, Instagram, and Reddit posts. Each result includes text, publication time, and the original URL where resolved. Collected captions and creator metadata are included when available.

GET/api/public/social-posts
ParameterDescription
termRequired indexed topic; up to 200 characters. Match its spelling and case.
platformsx, tiktok, instagram, reddit. Comma-separated; all by default.
limit1–100 posts, default 20. Only returned posts are billed.
start / endUTC ISO dates. Inclusive start, exclusive end; last 7 days by default. Maximum 31-day window.
cursorUse next_cursor with the same parameters to retrieve another page.

Coverage reflects collected samples, not every published post. Indexed excerpts are not full transcripts. Missing captions and metadata are not invented.

Credits & billing

Create a standalone account and purchase credits through Stripe. Both endpoints use your existing TickerTrends credits balance. The dashboard shows the pack price before checkout, your balance, and social delivery receipts.

1 post = 1 credit

Zero returned posts = zero charge.

1 new trend = 10 credits

Cached results = zero charge.

Retries & pagination

Send a unique Idempotency-Key for each social-post request. If the outcome is uncertain, retry with the same key and parameters to recover the saved receipt without another charge. A different query using that key returns 409. Use a new key for each next_cursor page.

Invalid queries return 400, invalid API keys return 403, and insufficient social credits return 402. Temporary errors return 503. API responses carry their status, result, and billing information.

Open your API workspace

Built for agents and AI workflows

Give your agent the integration guide or import the OpenAPI schema into its tool registry. It can discover both endpoints, understand costs and response states, and handle social pagination and retries with explicit billing receipts.

Store credentials in your system’s secret store. Human account setup and credit purchases stay in the dashboard; source text remains evidence, never agent instructions.