Social account linking is about to look a little different in Ayrshare. 👀 We’ve been rethinking how your users connect their social accounts to your app. And we’re almost ready to show you what we built. If account linking is part of your product, you’ll want to turn on post notifications for this one!

Ayrshare is now available on @Aident_AI Loadout. Agents in Codex or Claude Code can draft, review, and publish a social launch through the Ayrshare MCP Server, with approval before anything goes live. Get started: aident.ai/loadout/apps/ayrsh…

Running “Comment to DM” campaigns on Instagram? Here’s how to automate them without setting up a new rule for every post. 1/ The usual workflow Publish a post. Set up the comment automation. Publish another post. Set it up again. And repeat. 2/ Set it up once instead With Ayrshare, one Instagram engagement automation can now work across every post and Reel on an account. Including future ones. 3/ Your next campaign could look like this: You publish a Reel: “Comment GUIDE and we’ll send you the link.” Someone comments “GUIDE.” The automation picks it up and sends the DM. 4/ The DM can be dynamic too Instead of sending everyone the exact same response, your own system can generate the message each person receives. For example, a unique tracking link for each commenter. 5/ Keep publishing. The automation keeps working. No need to create the same rule again for every new post or Reel. 6/ Build Instagram engagement automations with Ayrshare Explore the Automations API → ayrshare.com/blog/instagram-…

What’s new at Ayrshare? September brought a few big additions to the API 👇 📣 Boost Instagram posts through the API You can now turn an organic Instagram post into a paid ad through Ayrshare, including posts that weren’t originally published through our API. Set your audience, location, interests, campaign goal, and other targeting directly through the API. 🎵 Add licensed music to Instagram Reels Publishing a Reel? Search Instagram’s audio catalog, choose a licensed track, and add it when publishing through Ayrshare. You can also control the balance between the track and your video’s original audio. 🤖 One Instagram automation can now cover every post Previously, engagement automations had to be tied to a specific post. Now you can create one rule that works across every post and Reel on an account, including posts you publish in the future. We also added dynamic DMs, so your own server can generate the message sent when an automation is triggered. 🔗 Facebook boosts can send people off Facebook Facebook boosted posts now support traffic campaigns with CTA buttons that can point to an external URL. And behind all of this, we rewrote Ayrshare’s API backend over the summer to set a new standard for reliability. Ideally, you didn’t notice that part. Your integration kept working while we replaced the infrastructure underneath it. More on that here: ayrshare.com/blog/we-rebuilt… That’s September. Keep building with Ayrshare 🛠️

The Ayrshare API runs on a new backend. If you build on it, nothing changed on your side. The rule for the rebuild: no changes to routes, request bodies, response formats, error codes, headers, or database structure. Same hostname, same contract. How accounts moved: a per-account feature flag inside the old backend. Flagged requests were forwarded to the new system and returned unchanged. Rollback was one flag per customer, with no infrastructure changes. Three rules for moving background jobs: - Exactly one system owns each piece of work at any time. - Overlap is fine for idempotent work. Brief gaps are accepted for destructive work. - Verify writes with a fresh read, not a command confirmation. The guiding idea: choose failures that leave visible evidence over silent losses. Why rebuild at all? The previous backend had handled tens of millions of daily calls since 2020, but years of feature additions left files too large to work well with AI coding agents. Rebuild from a position of strength, or rebuild in a hurry later. What it made possible: the MCP servers, the Connect flow, the Automations engine, and the WhatsApp Business beta all shipped on the new backend. Each would have been impractical on the old one. The cutover itself: 42 gateway errors over about two minutes while the new system warmed up, then zero. Every step of the migration was logged in one file, never edited, only appended to, with timestamps and verification results. Full write-up by Christos Melas, Engineering Manager: ayrshare.com/blog/we-rebuilt…

Every social media metric you can pull from the Ayrshare API, in one place. We published the full field reference for the Analytics API: 715 documented fields across 12 social networks, through one integration. Four scopes: per post, per account, per comment, and reviews. What that covers in practice: ✅Per post: likes, comments, shares, video playback counts, watch time, completion rates, and reaction breakdowns by type (like, love, haha, wow, sorry, anger). ✅Per account: follower counts and engagement totals, plus the network-specific fields. LinkedIn page views by section. TikTok profile button clicks. YouTube subscribers gained and lost. ✅Per comment: likes, replies, quotes, reposts, bookmarks, and impressions on the comment itself. ✅Also in there: Instagram story metrics (taps forward and back, exits, replies), audience demographics by city, country, and gender-age split, link click tracking, and reviews with ratings from Facebook and Google Business Profile. One call to pull post analytics: POST app.ayrshare.com/api/analyti… Authorization: Bearer API_KEY { "id": "POST_ID", "platforms": ["facebook", "instagram", "linkedin"] } If you're building AI agents: an agent that posts but never reads the results is running open loop. Full field reference, by network and scope: ayrshare.com/social-media-an…

Last month was one of our busiest shipping months yet at Ayrshare. WhatsApp. A completely rebuilt dashboard. More reliable webhooks. AI content labels. Better white-label customization. Here’s what changed 🧵 1/ WhatsApp is now part of the Ayrshare Messaging API in private beta. ayrshare.com/blog/whatsapp-a… Your users can connect their own WhatsApp Business Accounts, while Ayrshare handles the Meta registration, verification, and webhook setup. From there, you can send + receive messages and retrieve conversation history. 2/ We completely rebuilt the Ayrshare Dashboard. Dashboard 3.0 includes: Dark mode by default Searchable Post History API request + response inspection Webhook event logs Billing management View API Code That last one lets you compose a post and grab the exact API request to recreate it. 3/ Webhooks are much more resilient. Failed deliveries can now retry over a period of ~16 hours instead of disappearing after two quick retries. One important change for developers: persist your deduplication key for at least 24 hours. 4/ Comment + mention webhooks also got easier to work with. Payloads now include `postId` and `platform`. And a new `suspended` action fires when a User Profile is suspended or reactivated. 5/ You can now apply native AI content labels to posts on Instagram and X through the API. Set `isAIGenerated` to true in the relevant network options. The same parameter is already supported for TikTok. 6/ Max Pack users also have more CSS control over white-label account linking pages. Stable selectors, new custom properties, more layout controls, and no white flash while custom styles load. 7/ One more thing if you work with YouTube analytics: YouTube changed how views are counted on August 24. We added `engagedViews` to Post Analytics and Social Analytics so you can continue using the previous view methodology in your reporting. We are launching more exciting features this September. Check them out! ayrshare.com/blog/september-… Now back to building. 🫡

Let us introduce ourselves again 👋 youtube.com/watch?v=jA9KlwFV…

What if your users never had to log into a social media tool at all? That’s the experience Curbfeed built for real estate brokerages. When an MLS listing event happens, Curbfeed automatically turns it into branded videos and social posts, without asking agents to learn another platform, connect accounts manually, or add social publishing to their workflow. Behind the scenes, Ayrshare powers the publishing layer. Since 2023, Curbfeed has: → Sent 2M+ publish API calls → Achieved ~99% delivery across 7 social networks → Onboarded new brokerage offices in about a minute → Supported an NJ MLS deployment covering ~14,000 agents → Done it with zero engineers dedicated to social platform work If you’re building social publishing into a vertical SaaS product, how much of that complexity should your customers ever have to see? Read the Curbfeed story: ayrshare.com/case-study/curb…

WhatsApp is now in the Ayrshare Messaging API. 3.3 billion people use WhatsApp every month. Your product can now join those conversations through our API. No per-platform integration code. What you can do today: ✅ Send free-form text and media inside WhatsApp's 24-hour customer service window ✅ Receive inbound messages and media through webhooks ✅ Pull stored conversation history for support handoff, CRM context, or agent memory ✅ Link WhatsApp Business Accounts with Meta's embedded signup. We handle account verification and webhook subscription for you The API is built for customer support products, AI agents that need conversation context, CRM workflows, and multi-tenant SaaS where every tenant brings their own WhatsApp Business Account (and more) WhatsApp is offered on plans that include the Messaging API. Details and how to request access: ayrshare.com/blog/whatsapp-a…

Four updates that shipped at Ayrshare in early August in case you missed them: 1/ First up: Ayrshare got faster. We made performance improvements across some of our busiest endpoints, including: • /profiles p95 ↓ 88.7% • /analytics ↓ 75% • /post ↓ 63.1% • /messages ↓ 59.4% Nothing to change on your end. Your requests are just faster now. 2/ We also put all our social analytics fields in one place. That’s 715 documented fields across 12 networks, covering post, account, comment, and review analytics. Way less digging through platform docs just to figure out what data is available: ayrshare.com/social-media-an… 3/ Instagram linking got a little more flexible, too. You can now choose the Instagram linking method per session with instagramLinkMethod in generateJWT. So different users can go through different linking flows without changing your account-wide settings. 4/ We also made multiplatform comment and analytics reads more resilient. If one platform fails, you can still get the data from the platforms that worked. You’ll now see status: "partial" plus an errors[] array for the failed legs. More next week. Keep building with Ayrshare!

Most n8n social workflows start small. You wire up two networks for one brand, it posts some text and a link, and it works fine. A few months later you're on five platforms with different captions for each, and every one has its own node and its own OAuth credential that expires whenever it feels like it. There are three ways to structure this, and they solve different problems. 1. A separate node per platform @n8n_io ships native nodes for Facebook, Instagram, YouTube, and more. Each one needs its own OAuth app and carries its own quirks. This works for one brand posting text and links to a couple of platforms. It stops working when the platforms change their APIs and every update becomes your problem. 2. One REST call to a social media API Replace the wall of nodes with a single HTTP Request node: POST api.ayrshare.com/api/post { "post": "Excited to announce our new feature!", "platforms": ["facebook", "linkedin", "instagram"], "mediaUrls": ["example.com/image.jpg"] } One credential covers 13+ networks, and breaking platform changes get absorbed upstream instead of landing in your workflow. Best fit when the workflow is fixed and deterministic: same platforms, same format, every run. 3. An AI agent via MCP Point n8n's MCP Client Tool node at api.ayrshare.com/mcp and the agent discovers social tools on its own: posting, history, analytics, comments, messages, validation, error handling. Instead of hardcoding the logic, the agent decides at runtime which platforms fit the content, validates before publishing, and adapts the copy per network. Two guardrails worth stealing if you go the agent route: Make validate_post mandatory in the system prompt, so nothing publishes without a dry run Use n8n's "Send and Wait for Response" node to keep a human approval step before anything goes live The short version: nodes for simple single-brand posting, REST for fixed multi-network workflows, MCP when the workflow needs runtime decisions. Our engineer, Karan Suraj breaks down all three, with full setups: ayrshare.com/blog/n8n-social…

How to automate social posting with Ayrshare MCP + n8n 🧵 Here’s the workflow: n8n AI Agent → Ayrshare MCP Server → social networks. The agent handles the task. Ayrshare handles the social publishing layer. Step 1: Create your n8n workflow Start with whatever trigger makes sense for your use case: 💬 Chat trigger 📝 New content in a doc 📥 Form submission 📅 Scheduled workflow 🧠 AI-generated campaign idea This is what kicks off the posting flow. Step 2: Add an AI Agent node This is where the agent decides what to do. You can ask it to: * draft a post * rewrite copy for social * choose which platforms to publish to * schedule the post * check performance later Step 3: Connect the agent to Ayrshare MCP Add n8n’s MCP Client Tool node and point it to Ayrshare’s MCP Server. That gives your agent access to Ayrshare tools for publishing, scheduling, analytics, profiles, comments, and more. Step 4: Let the agent validate the post Before anything goes live, the agent can use Ayrshare to check whether the post is valid for each platform. That includes things like: ✅ Platform rules ✅ Posting limits ✅ Duplicate content ✅banned hashtags Step 5: Publish or schedule Once the post is ready, the same workflow can publish across 13+ social networks. You can also customize the post per platform, so LinkedIn, X/Twitter, Instagram, Facebook, and others don’t all need to use the exact same copy. Step 6: Pull analytics back into the workflow After publishing, your agent can check what happened. Views, engagement, comments, performance, and other analytics can come back into n8n, so the workflow doesn’t stop at “post published.” That’s the loop: Trigger → AI Agent → validate → publish/schedule → analyze If you’re building agentic workflows for social media, Ayrshare MCP gives n8n a way to move from “write the post” to “manage the publishing workflow.” Guide: ayrshare.com/docs/additional…

In 2021, two founders in Bengaluru built an AI that turns podcasts and webinars into short-form social clips. Today Quso.ai serves 4M+ users and publishes 309,839 posts every 30 days. They did it without a single engineer maintaining social platform APIs. 👇 Early on, Vedant Maheshwari and Kushagra Pandya hit the problem every AI content company hits: generating content is the easy half. Publishing eats engineering time. Every network has its own OAuth flow. Its own rate limits. Its own API changes shipping on its own schedule. As Vedant put it: "That's two engineers' bandwidth gone right there, and you have to keep updating with whatever Meta does next." For a startup, that math is brutal. Two engineers on integration maintenance means two engineers not working on the AI that actually sells the product. So in January 2022, they made a call: one Ayrshare integration instead of seven direct ones. Four years later, that same integration is still running. Unchanged. Through: ▸ A full company rebrand (vidyo.ai → Quso.ai) ▸ Meta tightening app review ▸ Instagram overhauling video submissions ▸ X restructuring API pricing ▸ Growth from launch to 4M+ users The numbers since 2022: ▸ 4.2M+ publish API calls ▸ 7 networks: TikTok, YouTube, Instagram, LinkedIn, X, Facebook, Pinterest ▸ Zero engineers reassigned to platform API maintenance When the platforms changed, Ayrshare absorbed the changes. Quso.ai's engineers kept shipping product. Vedant's summary: "Ayrshare is one of maybe three vendors we picked in 2022 that we'd still pick today." The full case study, including how they structured multi-tenant publishing for 4M users: ayrshare.com/case-study/vidy…

Any MCP-aware agent can now read from and act through Ayrshare, including publishing, analytics, comments, and more. Here’s what that unlocks. 1. Your agent can pull 200–500 past posts from a profile, including posts published outside Ayrshare. That means it can understand the brand’s voice right away, instead of figuring it out after the twentieth post. 2. Before a post goes live, Ayrshare checks it against each platform’s rules: ✅Banned hashtags ✅Duplicate content ✅Posting limits ✅Platform-specific requirements A bad post never reaches the network. 3. One request can publish across 13+ social networks, with per-platform customization built in. So your agent can plan, check, and publish social posts from the same workflow. Social publishing is becoming part of your agent stack. Read more here: ayrshare.com/blog/ayrshare-c…

What’s New in Ayrshare? 1. Ayrshare has a new look We gave Ayrshare a makeover. Our new website, updated logo, and refreshed docs better reflect where we’re headed: helping developers and AI teams build social media automation into their products faster. Take a look around at ayrshare.com 2. Social publishing for AI agents Your AI agents can now plan, check, and publish social posts through Ayrshare. With the new Ayrshare MCP Server, agents can use the Ayrshare API to work with publishing, analytics, comments, profiles, history, and more. 3. Built for the tools you already use We also launched a Claude Code plugin and n8n connector, so you can bring Ayrshare into your existing workflows with less custom code. Agents can learn from past posts, check content against platform rules, and publish across 13+ social networks in one call. 4. More useful analytics LinkedIn personal profile analytics now go deeper, with richer post, video, and follower metrics like impressions, reach, engagement, reactions, video views, watch time, and follower growth. Meta also retired a few reach and video metrics, so we updated Ayrshare’s supported fields to match. We’re already working on some cool updates for July. Can’t wait to share what’s next.

Here’s everything you need to know about Ayrshare, now that our new website is live. 1. We’re the social media #API for teams building social into their own products. Not just “schedule a post,” but the social infrastructure for apps, platforms, and AI workflows. 2. Ayrshare supports 13 social platforms through one API. So instead of building and maintaining separate integrations for each network, you get a single, consistent way to connect accounts, publish content, retrieve data, and manage social workflows. 3. Publishing is just the starting point. Ayrshare also helps teams pull historical posts, track performance, manage conversations, and work with social data through one consistent schema. Your social workflow doesn’t have to end when a post goes live. 4. Ayrshare is built for multi-tenant products. That means platforms can support many users, customers, brands, or workspaces without rebuilding account logic, permissions, and social integrations from scratch every time. 5. We’re also building for AI agents. With MCP support, Ayrshare gives agents a structured way to interact with social platforms — publishing, retrieving data, and taking action through a controlled API layer. 6. We’re compliance-first. Ayrshare is the social media API with documented platform compliance, including X's 2026 BYOK mandate, and is building toward a full governance and brand-safety suite. 8. So yes, the new Ayrshare website has a glow-up. A new logo, brand colors, and a cleaner design. But the real point is that it tells the Ayrshare story more clearly: One API across your complete #social workflow. Check us out: ayrshare.com/

Your users want Instagram automations. “Comment LAUNCH for the link.” “DM DEMO to talk to sales.” “Reply VIP for the presale code.” But if you’re building those workflows into your own product, you need to think about compliance. Instagram automation is not just: “If comment contains X, send Y.” You have to account for Meta permissions, messaging rules, rate limits, user consent, duplicate events, failed sends, retries, and activity tracking. Miss one layer, and you might risk losing your Meta accounts. That’s why we built Instagram engagement automations for the Ayrshare API — designed to help platforms support these workflows within Meta’s requirements. Now, you can trigger a DM, webhook, email, or all three when someone engages with an Instagram account in specific ways. Comments, story replies, DM reactions, and DM keywords can all become workflow triggers. This means your product can support use cases like: Comment “WAITLIST” → send the signup link Reply “VIP” → send the presale code DM “DEMO” → route the lead to sales Without your team building and maintaining all the Meta-specific automation logic yourself. The goal is simple: Your users get the Instagram engagement workflows they already want. And your team gets one API instead of months of custom Meta integration work. Try it now: ayrshare.com/blog/instagram-…

X no longer allows API providers to use one shared developer app for every customer. Each customer needs their own X Developer app connected to the API. Here’s what to check before choosing a provider: ayrshare.com/blog/x-api-comp…

Ayrshare now supports X’s Amplify monetization programs in beta. This allows publishers to configure pre-roll ads and sponsorship programs directly at publish time, without switching to Media Studio. ayrshare.com/monetize-x-vide… cc @XDevelopers