ApivomApivom
Get Demo

Threads API Connector

Meta's Threads API — publish text, image, video and carousel posts, quote and reply, read post and account insights — connected to Apivom Mars: your marketing calendar publishes to Threads and reads back views, likes, replies, reposts, quotes and shares, with your own Threads access token.

What you can do

  • Mars publishes text, image and carousel posts to Threads from the content calendar and reads post insights back
  • Two-step publishing model (create container → publish) handled for you, including carousel item containers
  • Insights: views, likes, replies, reposts, quotes and shares per post; follower and account metrics
  • Quote posts, replies, reply management and the OAuth token exchange / long-lived token routes catalogued
  • 39 routes (22 read-only) on graph.threads.net; Mars records the Threads post id of every published item

Use cases

  • One calendar, Threads included — Schedule Threads posts next to your other channels in Mars and let them publish at the planned time without a separate tool.
  • Carousels without the manual steps — Mars creates each item container and the carousel container, then publishes — the multi-step Threads workflow runs unattended.
  • Engagement back in the calendar — Views, likes, replies, reposts, quotes and shares are fetched on a schedule so the team sees what worked without opening Threads.

The Threads API on graph.threads.net is Meta's programmatic interface to Threads, the text-first social network: it follows the familiar Graph pattern of creating a media container — text, image, video or the item containers of a carousel — and then publishing it, plus quote posts, replies and reply moderation, and an insights surface with views, likes, replies, reposts, quotes and shares per post and follower metrics for the account. Token handling is its own route family: exchange the authorisation code, obtain a long-lived token, refresh it. Apivom Atlas catalogues 39 of these routes. Apivom Mars, the marketing-automation product, uses the API directly: a post scheduled in the content calendar is published to your Threads account as text, image or carousel, and its performance metrics are read back on a schedule so the calendar shows real engagement next to each item. The access token is the one your Threads account grants during connection; Mars stores it encrypted, refreshes it before expiry and records the Threads post id of every published item.

Authentication

A Threads API user access token obtained through Threads' OAuth flow: Apivom Mars exchanges the code for a long-lived token (60 days), stores it encrypted and refreshes it daily before expiry. Calls made through Apivom Atlas send it as Bearer; Atlas stores nothing.

Frequently asked questions

What does Mars publish and read on Threads?

It publishes text, image and carousel posts and reads post insights (views, likes, replies, reposts, quotes, shares). Video posts, quote posts and reply moderation are catalogued routes you can call, but they are not part of the scheduled Mars workflow today.

How is the Threads account connected?

Through Threads' OAuth flow: you authorise the connection once, Apivom exchanges the code for a long-lived token and refreshes it before expiry. Mars keeps the token encrypted; you can revoke it from your Threads settings.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.