Every social tool eventually faces a shortcut: an unofficial bridge, a scraped endpoint, a wrapper around the app's private API. It works, it is faster to build, and it gets features the official API does not offer. It is also the single biggest account-safety risk in the industry, and the reason some tools can promise things their users later lose accounts over.
We build on official APIs only — YouTube Data API v3, the Meta Graph API, the TikTok Content Posting API, the LinkedIn Marketing API, X API v2, Pinterest API v5. This is what that choice buys, what it costs, and why the "missing" features are often missing for a reason.
What official APIs buy
Stability and legitimacy: publishing through the vendor's own front door means the vendor sees a compliant client, not an attacker. Rate limits are contractual instead of discovered. Credentials are scoped OAuth grants the user can see and revoke, not passwords handed to a middleware. And when something breaks — an API change, a quota, a scope removed — there is documentation and a changelog, not a silent format change to reverse-engineer at 2 a.m.
The trade is honest: official APIs are sometimes slower to gain new surfaces, and they enforce rules a scraper would happily ignore. Both of those are features wearing overalls.
Honest labels, including UNSUPPORTED
Official APIs do not do everything, and pretending otherwise is how tools end up faking capabilities. Our adapters label every capability per platform as AUTOMATED, PARTIALLY AUTOMATED, GUIDED, MANUAL or UNSUPPORTED — and UNSUPPORTED is the honest half. Publishing to YouTube is automated; advertising there is not supported through our integration. LinkedIn ads are guided, not autonomous. A capability matrix with no "no" in it is marketing, not a matrix.
For you as a buyer, the label to demand from any vendor is the same: which of these features talks to an official API, and which ones do something else. Vendors who can answer crisply are the ones who built it properly.
What platforms actually permit
The official APIs draw a line between what a platform stores (metrics, content) and what it will let a third party do (automate engagement, buy ads on your behalf). Analytics access varies by platform and scope; some surfaces are partially automated at best; direct messaging is the most guarded of all. Automation rules also differ: what counts as acceptable posting cadence, what counts as spam, what requires disclosure.
A tool built on official APIs can tell you exactly where those lines are, because it had to implement against them. Ask for that map before you buy; it is the difference between a plan that survives contact with the platforms and one that survives the demo.
The trade-off, stated plainly
Official-API-first means some things this product will never do — automate the surfaces platforms deliberately keep closed, promise reach numbers from endpoints that are not sanctioned, post through accounts in ways the platforms have not approved. We think a tool your account can trust is worth more than a feature your account can lose. If a competitor promises otherwise, ask them what their ban rate looks like.