TrendsAGI API implementation guides

Guide: Ads Platform Connection Pipeline

Connect ad accounts in one click, select a positive trend category, and run preview/apply targeting updates for mapped campaign entities with safety guardrails.

1) GET /api/integrations/ads/providers
2) GET /api/integrations/ads/{platform}/auth
3) Complete authorization in browser
4) PUT /api/integrations/ads/{platform}/selection (trend_category + strict_safety)
5) POST /api/integrations/ads/meta_ads/preview
6) POST /api/integrations/ads/meta_ads/apply

Guide: Social Listening Agent

Poll high-velocity signals, enrich with AI insights, gate with crisis events, and route approved summaries into your social response queue.

1) GET /api/trends?sort_by=volume
2) GET /api/trends/{id}/ai-insights
3) GET /api/intelligence/crisis-events?status=active
4) POST into your outbound social workflow only if no blocking event

Guide: Search Ops Agent

Combine recommendations + trend velocity to reprioritize SEO briefs and monitor query opportunities in your own search analytics workflows.

1) GET /api/intelligence/recommendations
2) GET /api/trends?category=...
3) Compare with your search analytics metrics
4) Generate briefs with top overlap topics

Guide: Slack Alerting Pipeline

Connect Slack once, select an alerts channel, and route high-priority trend events into an operator queue with minimal manual setup.

1) GET /api/integrations/slack/auth
2) Complete authorization in browser
3) GET /api/integrations/slack/channels
4) POST /api/integrations/slack/save-channel
5) PUT /api/integrations/slack/settings

Cookbook (Tested Scripts)

Pre-made scripts are included under `scripts/api_cookbook` and were validated on February 19, 2026 against the live API.

export TRENDSAGI_API_KEY="<TRENDSAGI_API_KEY>"
cd scripts/api_cookbook

bash ./01_status_and_trends.sh
bash ./02_webhook_lifecycle.sh
bash ./03_ads_reporting_preview_export.sh
node ./04_integration_status_matrix.mjs
python3 ./05_integration_status_matrix.py

Ads platform integrations are prioritized for conversion workflows, followed by social/search channel playbooks.

Social and search connectors are available after ads integrations.

Guide: Automation & Rollback

For any write action in ad or social runtimes, store prior state and idempotency keys so degraded outcomes can be rolled back deterministically.

- Generate run_id per workflow
- Persist request payload + prior target state
- Retry transient errors with same idempotency key
- Route 4xx validation failures to manual review