TrendGuru FAQ

TrendGuru is a social media publishing API and dashboard. You connect Instagram, TikTok, YouTube, Facebook Pages, X and LinkedIn accounts once, then publish or schedule posts to any of them with a single REST request. Webhooks report results and analytics collect engagement and follower data.

Instagram, TikTok, YouTube, Facebook Pages, X (Twitter) and LinkedIn. Threads, Telegram, Pinterest, Reddit and Bluesky are planned for the next wave.

Nothing during the public beta. Profiles, accounts, posts, webhooks and analytics are unlimited and no card is required. Paid plans will be priced per connected account and announced in the dashboard before they start.

No. The beta is free. Paid per-account plans will follow, with advance notice inside the dashboard. Accounts connected during the beta keep working.

Yes. Profiles hold accounts, a post carries text, media and targets with typed per-platform options, media is uploaded through an upload URL and results arrive by HMAC-signed webhooks. Most integrations move in an afternoon; the docs list every endpoint and option.

Same job: connect accounts, post and schedule, get results by webhook, read analytics. TrendGuru differs by being free during beta, self-hostable and focused on publishing rather than inbox or team features.

Send POST /v1/posts with a Bearer API key, the content, optional mediaItems (public URLs) and a targets array of accountId entries. Set publishAt to "now" or an ISO 8601 time. The response contains the post with per-target status and url.

Set publishAt to an ISO 8601 timestamp and optionally timezone. The post gets status scheduled; the worker publishes it at that time and fires post.published or post.failed.

Yes. Each entry in targets can carry its own text and media. The main text and media are used when they are absent.

Per-target options validated per platform: Instagram kind and first comment, TikTok privacy and duet toggles, YouTube title and visibility, Facebook reel or story, X reply settings and threads, LinkedIn organization and document title. The full list is in the docs.

Use a public URL directly, or call POST /v1/media to get an upload URL and PUT the file to it (up to 5 GB), then reference the returned publicUrl. TrendGuru pulls the file into each platform's own upload flow.

Yes. YouTube uploads use the resumable API, TikTok uses PULL_FROM_URL, Instagram Reels and Facebook Reels use container and upload sessions, X and LinkedIn use chunked uploads.

Yes on Instagram (up to 10 items), TikTok photo posts (up to 35), Facebook multi-photo posts, LinkedIn multi-image posts and X (up to 4 images).

Yes on Instagram and Facebook Pages via options.kind = story.

The target is marked failed with error.message, error.category and error.source. Transient errors retry automatically up to three times. The post ends as failed or partial and webhooks post.failed or post.partial fire. You can retry with POST /v1/posts/{id}/retry.

A post that published on some targets and failed on others. Each platform target keeps its own status, id and error.

Create a webhook with a URL and a list of events. TrendGuru POSTs a JSON event with headers TrendGuru-Event, TrendGuru-Event-Id, TrendGuru-Timestamp and TrendGuru-Signature (t=…,v1=HMAC-SHA256 of "t.body" with your secret). Failed deliveries retry at 1 minute, 5 minutes, 15 minutes, 1 hour, 3 hours and 12 hours. Ten consecutive failures disable the endpoint.

post.scheduled, post.published, post.partial, post.failed, post.canceled, target.published, target.failed, account.connected, account.disconnected and analytics.synced; wildcards post.* and * are accepted.

OAuth access and refresh tokens are encrypted at rest with AES-256-GCM using a server-side key and are never returned by the API. Tokens are refreshed automatically before they expire.

As SHA-256 hashes. The full key is shown once when created. Keys can be read-only, scoped to specific profiles and given an expiry.

No independent security audit has been published yet. Tokens are encrypted at rest, API keys are stored as hashes and every request is logged.

TrendGuru publishes only to accounts their owners connected through the platforms' official OAuth flows and official APIs. It does not scrape, automate browsers or use unofficial endpoints for publishing.

Not on trend.guru; the hosted service uses TrendGuru's apps. If you self-host you register your own OAuth apps and add the credentials to the server environment. The Settings page shows which platforms are ready.

X charges for write access to its API. Posting to X works through the customer's own X developer app on the tier they pay for; TrendGuru does not resell X API access.

Yes. Each profile holds one account per platform, so create one profile per Instagram account (or per brand) and connect each account into its own profile.

A profile is a container for accounts, usually one brand or client. Posts target accounts inside profiles. API keys can be scoped to profiles.

Ask for the Facebook connect URL, authorize, then pick the Page from the list TrendGuru returns. The Page's own token is stored, so posting keeps working when the user token expires.

Either through Instagram Login (business or creator account, default) or through Facebook Login when the Instagram account is linked to a Facebook Page. Both are official Meta flows.

Yes. Likes, comments, shares, saves, views, impressions and reach per published post are synced hourly for 14 days after publishing; follower counts per account are refreshed daily; daily aggregates and per-post timelines are available through the API and dashboard.

Not yet. The beta covers publishing, scheduling, webhooks and analytics. Comments and messaging are on the roadmap.

No. TrendGuru is for organic publishing.

Yes. The API is plain JSON with a Bearer key, an Idempotency-Key header for idempotent retries, a validation endpoint and machine-readable error codes. An MCP server is planned.

Yes, through their HTTP request nodes. Send a fresh Idempotency-Key per logical post so retries never create duplicates.

Identical content to the same account within 24 hours returns HTTP 409 DUPLICATE_CONTENT with the existing post id. Change the text, media or account to post again intentionally.

600 requests per minute per API key by default, reported in RateLimit-* headers. Posting volume itself is not limited by TrendGuru; platform-side limits still apply.

Yes. It ships as one service plus a database that you run on your own server. One process serves the API, the dashboard and the publishing worker; the worker can also run separately. You supply your own OAuth app credentials.

TrendGuru is built by the team behind trend.guru, which also runs its own content and publishing pipelines on the platform. Contact through the dashboard.

On TrendGuru's own servers in the European Union for the hosted service, or on your servers when self-hosted.

POST /v1/posts/{id}/unpublish deletes it on platforms that allow deletion through their API (YouTube, X, LinkedIn, Facebook). Instagram and TikTok do not allow deletion through their APIs.

API request logs and publishing logs are kept for 30 days. Webhook delivery logs are kept with the webhook.