Latest Updates

Follow us on X, listen to our Social Media API Podcast, or sign up for our Newsletter for the latest updates.

​

October 2026

• October 20 - Know When an Ad Account Is Connected, Disconnected or Loses Access. The ads webhook now tells you when a Google Ads or TikTok ad account is connected or disconnected, and when an ads call finds that Google Ads has lost access, so you can ask your users to reconnect. Register the ads action; see Ad Account Events.
• October 20 - Comment-to-DM Automations on Facebook Pages. A comment_keyword automation now accepts platform: “facebook”, so now you can send a Messenger DM to anyone who comments a keyword on your Facebook Page’s posts. The DM is a private reply to their comment, so they don’t need to have messaged your Page first. Set postId to the Facebook post ID from postIds[].id, or to “all” for every post. The profile needs Messaging activated for Facebook. See Comments on Facebook Page posts.
• October 20 - Comment Webhooks for Threads. Get a webhook the moment someone replies to a post on a connected Threads account, alongside Facebook and Instagram comments. Register the comments action to receive them, with the postId when you published the post through Ayrshare. See Comments Action. Check this if you already receive the comments webhook: it now also delivers Threads replies, with platform set to threads.
• October 20 - Two-Step Verification for Dashboard Sign-In. If you sign in to the dashboard with an email and password, you can now require a 6-digit code from an authenticator app, so a stolen password alone can’t open your account. Turn it on from the Account page; it’s optional and doesn’t affect your API key. See How to Turn On Two-Step Verification.
• October 19 - Know When Meta Withholds Message Content. Instagram and Facebook messages webhooks now carry unsupported: true when Meta sends a message type without its content, so you can tell your users why it is missing. Text, links and media arrive as before. See Unsupported Messages.
• October 16 - Stop Your X Videos Playing in Embeds. Send twitterOptions.embeddable: false on an X post with a single video to keep that video from playing inside embedded posts on other websites. It still plays on x.com as normal. See X Options.
• October 16 - Boost Instagram Posts From the Dashboard. Boost published Instagram posts and see their boosted ads from the dashboard’s Ads page, with daily or lifetime budgets, set on the ad set or the campaign. Instagram boosts need an Instagram Business account linked through Facebook with a Facebook Page. See Instagram Boost for the full requirements.
• October 16 - Bluesky Handles, Names and Avatars for Email-Linked Accounts. Bluesky accounts linked with an email now show their real handle, display name and avatar in User Profile Details, and work with Analytics on a Social Network. Check this if you store the Bluesky username for accounts linked with an email: it now returns the account handle instead of the email, and if one still shows an email, relink Bluesky.
• October 14 - Reliability and Performance. Square and vertical Bluesky videos display at their true shape.
• October 13 - Campaign Budgets for Facebook and Instagram Boosts. Hold a boost’s daily or lifetime budget on the campaign instead of the ad set with budget.level: “campaign”, using the nested form of the boost body. See Facebook Boost and Instagram Boost.
• October 13 - Clearer X Errors When API Credits Run Out. If your X Developer account runs out of API credits, media uploads now say so directly, with a link to top up at console.x.com. Check this if you match on code: 117 or 115 for X media errors: out-of-credit uploads now return code: 416.
• October 13 - Clearer X Errors for Locked Accounts. When X has temporarily locked an account, image and video posts now say so, with X’s explanation in details. Log in to x.com, complete X’s unlock steps and post again; no relink is needed. Check this if you match on code: 117 or 115 for X media errors: uploads from a locked account now return code: 224.
• October 13 - Comment Webhooks for Facebook Pages. Get a webhook the moment someone comments on a connected Facebook Page, alongside Instagram comments. Available on profiles with the Messaging Add-On; connected Pages are enabled automatically. See Comments Action. Check this if your comments webhook handler expects Instagram fields: Facebook Page events use comment_id, post_id and message, so branch on platform.
• October 13 - Boost Buttons That Open a Chat. Boost a Facebook or Instagram post whose button opens a Messenger, WhatsApp or Instagram Direct conversation. Send callToAction.destination with the matching button type, no link, and the engagement or interactions goal, using the nested form of the boost body. See Facebook Boost and Instagram Boost.
• October 13 - Ad Webhooks. Get a webhook when an ad or campaign is created, when an ad is paused, activated, deleted or archived, and once a night with each ads platform’s spend for the day. Register the ads action; the Ads Action lists every field.
• October 13 - Meta’s Ad Review in Get Boosted Ads. See whether Meta approved, rejected or is still reviewing each Facebook and Instagram ad, with Meta’s reasons, in the new review field of Get Boosted Ads.
• October 9 - Boost Into Your Existing Meta Campaigns. Add a boost to a campaign you already run in Meta with attachTo.campaignId, or to an existing ad set with attachTo.adSetId plus its attachTo.campaignId, leaving out budget, targeting and bidAmount. Both use the nested form of the boost body. Pausing or activating the boost changes only what it created. See Facebook Boost and Instagram Boost.
• October 9 - Reliability and Performance. More dependable Instagram publishing and faster carousels.
• October 8 - Faster Instagram and Threads Video Posts. Video posts now typically publish in about 5 seconds on Instagram and about 6 seconds on Threads. Nothing to change on your side.
• October 8 - Facebook and Instagram Boosted Ads by act_ Account ID. Facebook and Instagram Boosted Ads accept accountId with or without the act_ prefix, such as act_1234567890. The GraphQL ads query and the MCP list_ads tool do too. Check this if you use the GraphQL ads query or the MCP list_ads tool and treat an empty ads list as “no ads”: an accountId that is not a valid ad account id now returns code: 101 there, as the REST endpoints already did.
• October 8 - Clearer Facebook and Instagram Comment Errors. When Facebook or Instagram rejects a comment or reply sent with Post a Comment or Reply to a Comment, details now gives the platform’s reason with its error code and subcode, so you can see what to change.
• October 7 - More Dependable Threads Posting. Threads posts, comments, replies and first comments publish more dependably. When Threads isn’t ready to accept a post, the response tells you it is safe to retry. See Threads Media Not Ready. Check this if you retry Threads posts on code: 379 or HTTP 500: when Threads isn’t ready you now get code: 522 with HTTP 400 and retryAvailable: true, so retry on that.
• October 7 - Linking URLs Even When the Email Can’t Be Sent. When you ask us to email a linking URL, Generate a Linking URL and Create a Link Session still return the URL, with emailSent: false and an emailError object if the email can’t go out, so you can send it another way. Check this if you retry on code: 333: look for emailError in the success response instead, as described in Connect Accounts Email.
• October 7 - Know When Users Revoke YouTube Access. If a user removes Ayrshare’s access in their Google account, YouTube unlinks, requests return code: 250, and the social webhook fires with “source”: “system”, so you can ask them to relink. See Unlinking and Revoked Access. Check this if you read stored YouTube data or reply to YouTube comments by their Ayrshare ID: analytics, comment records and YouTube video IDs and URLs in post history are deleted 5 days after a profile unlinks YouTube unless the same Google account is relinked first, and records of comments sent through Ayrshare are kept for 28 days, so after that reply to or delete them with their YouTube comment ID and “searchPlatformId”: true.
• October 7 - YouTube Title and Description Length Checks. The YouTube result now includes a warnings entry when a youTubeOptions.title over 100 characters or a description over 5000 bytes was shortened to fit. See YouTube posting. Check this if you send long YouTube titles or descriptions: from October 21, 2026 over-limit text returns code: 176 instead of being shortened, and a post scheduled to publish on or after that date already returns it when you submit, so keep titles to 100 characters (counted in Unicode code points) and descriptions to 5000 bytes.
• October 6 - Lifetime Budgets for Facebook and Instagram Boosts. Spend a set total between a boost’s start and end dates with budget.type: “lifetime”, using the nested form of the boost body. See Facebook Boost and Instagram Boost.
• October 6 - Pinterest AI Disclosures on Pins. Label image, carousel and video Pins with pinterestOptions.aiDisclosures, sending AI_MODIFIED, SYNTHETIC_PERFORMER, or both. The disclosures apply to the whole Pin. See Pinterest posting.
• October 6 - Facebook Reels Collaborator Pages. Invite a Facebook Page to collaborate on a Reel by adding its Page ID to faceBookOptions.collaborators; one Page per Reel. Check the invite with Collaborator Request Status. To schedule such a Reel, use scheduleDate. See Facebook Reels.
• October 5 - Live Facebook and Instagram Ad Insights. Report on a campaign or ad for any range in the last 37 months, day by day, with spend, reach, clicks and more. Choose metrics, split by breakdowns such as age or country, and page with cursor. See Facebook Insights and Instagram Insights.
• October 5 - LinkedIn Daily Follower Growth for Personal Profiles. Track daily follower counts for the last 30 days on LinkedIn personal profiles with followersDaily on Analytics on a Social Network.
• October 5 - Pinterest Profile Links in User Profile Details. Pinterest profileUrl in User Profile Details now opens the account’s profile, with no relink needed. Check this if you show Pinterest username as a board name: it now returns the account username instead, so use displayName for the board name.
• October 5 - Threads Profile Links in User Profile Details. Threads profileUrl in User Profile Details now opens the account’s profile, with no relink needed. Check this if you show Threads username as the account’s name: it now returns the handle instead of the display name, so use displayName.
• October 2 - Special Ad Category Boosts Outside the US. Boost housing, employment and financial posts on Facebook and Instagram outside the US. Set specialAdCategories and target your locations as usual. See Boost Post.
• October 1 - Clear Messages When a Linking URL Expires. Users whose linking URL expires are now told so and asked for a new one. The Ayrshare Connect Widget error event includes code 503 for an expired link, so your code can create a new one. Raise expiresIn when you create the link up to 2880 minutes on the Max Pack, to give users more time.
• October 1 - Reliability and Performance. Clearer guidance when Facebook blocks an account.

​

September 2026

• September 29 - Query the Ayrshare API With GraphQL. Request several supported operations in one call with the new GraphQL endpoint at https://api.ayrshare.com/graphql, using the same API key, profile scoping and plan limits as REST. Each API-backed root field counts as one API call. A failed operation still returns HTTP 200, so check errors. Try it in the GraphQL Explorer or start with the GraphQL API Overview.
• September 29 - DM Automations on Facebook Pages. Auto-reply in Messenger when someone sends your Facebook Page a keyword or reacts to one of your messages. Create an automation with “platform”: “facebook” and a dm_keyword or dm_reaction trigger; the profile needs Messaging activated for Facebook. See Facebook Pages.
• September 29 - Unique Reach for Facebook Posts and Pages. See how many unique people saw your Facebook content. Analytics on a Post returns totalMediaViewUnique, and Analytics on a Social Network returns pageTotalMediaViewUnique for your Page. The Page value adds up daily counts, so someone who viewed on two different days counts twice.
• September 29 - Clearer Error When Meta Can’t Fetch Your Media. When Meta can’t fetch the media for an Instagram post or Facebook Reel, the error names the likely cause, such as your host blocking Meta’s crawlers, and how to resolve it. See Meta Media Crawler Blocked. Check this if you retry on code: 440 (Instagram) or code: 108 (Facebook Reels): media Meta cannot fetch now returns non-retryable code: 479 (HTTP 400), so allow Meta’s crawlers or serve the media from a reachable host instead of retrying.
• September 28 - Turn Comments On or Off With Update a Post. Send disableComments on its own to Update a Post to turn comments on or off. Requests with nothing to update, such as a bare id or an empty youTubeOptions, now return an error so typos surface right away. Check this if you send visibility at the top level or send updates with nothing to change: these now return code: 101 instead of status: “success”, so move visibility into youTubeOptions.
• September 28 - YouTube Videos Keep Their License When You Change Visibility. Changing youTubeOptions.visibility with Update a Post keeps the video’s license, including “creativeCommon”. Check this if you changed visibility on a Creative Commons video before September 28: its license may have been reset to the Standard YouTube License, so check it in YouTube Studio.
• September 25 - Gender Targeting for Facebook and Instagram Boosts. Reach the audience you choose: boosts sent through Boost a Facebook Post with “gender”: “male” or “female” target that gender on Facebook and Instagram. Requests without gender are unchanged. Check this if you send gender: male or female now narrow delivery to that gender instead of all genders, and any value other than all, male or female now returns code: 101, so send only those values.
• September 25 - See Exactly What Each Automation Sent. Each action result in Get Automation Activity has a new sent field with the DM text, queued email, or webhook data and delivery id, plus config with the action’s settings at that moment. See what each run sent, even after you edit the automation. See what sent contains.
• September 24 - Write Each Automation DM With Your Own Server. Set messageUrl on a send_dm action and your endpoint writes each DM, so every commenter can get a personal message, such as their own tracking link. The action’s regular message is the fallback, and messageSource in Get Activity shows which text was used. See dynamic message content.
• September 24 - Richer Automation Webhooks With Completion Events. Automation webhooks include activityId, actionId, eventId, commentId, commentText, postId and storyId, so you can match each one to its Get Activity row. Set “sendCompletedEvent”: true on a fire_webhook action to also receive automation.completed with the outcome. See webhook events.
• September 24 - Run a Comment Automation on Every Post. Set a comment_keyword trigger’s postId to “all” and the rule fires on any post or reel on the connected account, so you set it up once. Story triggers accept “all” for storyId too. See evergreen rules. Check this if you send a variant such as “ALL” or rely on your own keyword comments to run fire_webhook or send_email: variants are now rejected, so use lowercase “all”, and actions from your own comments are now recorded as skipped.
• September 24 - X Comments on Replies, With Clearer Errors. Get Comments returns the replies on an X post that is itself a reply. When your own X Developer account is out of credits or rate limited, you get a clear error to act on. Check this if you treat an empty X comments list as “no comments”: depleted credits now return code: 416 (HTTP 402), rate limits return code: 364 (HTTP 429), and multiplatform reads return status: “partial” with X in errors[] (see error codes 364 and 416).
• September 23 - Clearer X Direct Message Errors. When your own X app lacks Direct Message permission, Get Messages tells you how to resolve it: set the app to “Read and write and Direct messages”, then unlink and relink the X account. The response includes resolution: . Check this if you branch on 336 for X DM reads or treat an empty X DM response as “no messages”: missing DM permission now returns code: 520, and a User Profile without Messaging activated returns 403 / code: 361 instead of an empty 200.
• September 21 - Paginated X/Twitter Message History. Get Messages on X/Twitter returns stored history in pages of up to 100 messages or conversations, with a meta.pagination cursor. Follow meta.pagination.next while meta.pagination.hasMore is true, even after a short or empty filtered page. Requests that send limit are unchanged. Check this if you call X/Twitter Get Messages without limit and expect your full stored history in one response: it now returns the newest 100, so follow meta.pagination.next for the rest.
• September 21 - Date Ranges and Daily Values for Google Business Profile Analytics. Build last-month, last-quarter and time-series reports from Google Business Profile data. Analytics on a Social Network honours quarters (1–4) and daily: true for gmb, as it already does for Facebook, Instagram, Snapchat, TikTok and YouTube. Check this if you already send quarters or daily with gmb: the same request now returns a narrower window instead of 24-month totals, and with daily: true each gmb metric is a object instead of a number, so read total or values.
• September 21 - All-Time Analytics With quarters: 0 on Facebook and YouTube. Send quarters: 0 to Analytics on a Social Network for Facebook and YouTube to get the full all-time window, matching every other network. Requests with quarters from 1 to 4, or without it, are unchanged. Check this if you send quarters: 0, or a negative or non-numeric quarters, to Facebook or YouTube: the response now covers the full all-time window instead of one quarter, so send quarters: 1 to keep a single quarter.
• September 18 - Link Social Accounts From Inside Your Own Dashboard. Add the Ayrshare Connect widget with one script tag, and your users connect and unlink social accounts right in your layout. Ten events, including state, keep your app in sync, and design tokens let you style it. If your page sends a Content-Security-Policy, add script-src and frame-src entries. Requires the Max Pack; see Ayrshare Connect Widget.
• September 17 - Paginated Message History on Facebook, Instagram and WhatsApp. Get Messages returns up to 100 messages or conversations per page on Facebook, Instagram and WhatsApp; set limit from 1 to 100 for smaller pages. Pass meta.pagination.next as next, with the same profile and filters, while meta.pagination.hasMore is true. Check this if you call Get Messages on Facebook, Instagram or WhatsApp without limit and expect all history in one response: it now returns up to 100 items, so follow the cursor for the rest.
• September 14 - Long Videos and Full Options in X Threads. Posts with thread: true on X can include longVideo: true (up to 4 hours), plus altText, subtitles, geo restrictions, replySettings, subscribersOnly and Pro Media options; on Threads, allowCountries applies too. altText and subtitles apply to the first post’s media only. See which options apply to a thread. Check this if you send subscribersOnly or Threads allowCountries on threads from an account not entitled to them: the thread now fails with code: 111 or code: 101 instead of publishing without the option, so check isEligibleForGeoRestrictions on /user first.
• September 14 - Attach Licensed Music to an Instagram Reel. Search Instagram’s audio catalog with GET /media/instagram/audio/search and pass the track’s id as instagramOptions.audioConfiguration.audioId when you publish a Reel; audioVolume and videoVolume (0 to 100) set the mix. Requires an Instagram account connected through Facebook Login; see music attach eligibility.
• September 11 - Call-to-Action Buttons and a Traffic Goal for Facebook Boosts. Boost Post accepts a traffic goal for link clicks and a callToAction button such as SHOP_NOW or LEARN_MORE; in the dashboard, choose Drive Traffic. Interests accepts specialAdCategories, so regulated campaigns see only interests Meta allows them to target. Check this if you send callToAction without the traffic goal, an unrecognized specialAdCategories value on Boost Post, specialAdCategories on Interests without a numeric accountId (a leading act_ is fine): these now return code: 101 instead of being accepted, so send a valid goal, category and accountId.
• September 8 - One Call Returns Every Network’s Account State. Add include=state to GET /profiles to get one normalized state per social network for a User Profile, such as linked, suspended or rateLimited, with actionable, message and helpUrl. Use actionable to decide whether to show your user a button. Requires refId.
• September 7 - Cancel a Monthly Plan Immediately, With an Automatic Refund. Choose to end a monthly plan today, in the dashboard, for an automatic refund: in full within 48 hours of the charge, otherwise for the unused period. Access ends, and deletion of your posts, analytics and linked accounts starts, when you confirm; uninvoiced pay-as-you-go usage is billed separately. One use per account; see how to change or cancel your subscription. Check this if your most recent payment failed: canceling now ends any plan immediately instead of at the end of the period, and the unpaid invoice is voided only if that payment first failed less than 48 hours before you cancel.
• September 7 - Analytics Responses Tell You When to Poll Next. Every analytics response’s nextUpdate reports when that data will next refresh, so you can poll exactly when new numbers are available. See How fresh the data is. Check this if you poll analytics every eleven minutes or show LinkedIn analytics for posts older than about ten days: those LinkedIn numbers now refresh every 3 to 7 days, so read nextUpdate from each response instead of polling on a timer.
• September 7 - Know the Moment a User Connects an Account. Pass an origin when you create a link session and open the url in a popup; your page receives connect:success, connect:error or connect:cancelled, with no polling or redirect. Without a popup, Get a Link Session reports completedAt and completedNetworks, and Telegram, which completes outside the popup, is reported only there. See Link Completion Events.
• September 2 - Reels From Signed Video URLs. Publish Facebook and Instagram Reels from signed CDN or Firebase Storage URLs that carry a query string, such as https://cdn.example.com/reel.mp4?Expires=1756700000, without setting isVideo: true. See media guidelines. Check this if you post video URLs with a query string to Facebook, LinkedIn, Pinterest or TikTok: they now count against the per-post video limit instead of the image limit, so posts over that limit are rejected.
• September 1 - Bluesky Videos Up to 10 Minutes and 300 MB. Post Bluesky videos up to 10 minutes long and 300 MB, matching Bluesky’s new limits. Send the same mediaUrls as before; see Bluesky media guidelines.

​

August 2026

• August 31 - Create Social Linking URLs Without a Private Key, and Revoke Them. Create a social-linking URL from your API key and a Profile-Key alone with Create a Link Session, with no privateKey to store or sign. Check whether a link was opened with Get a Link Session, and cancel it before it expires with Revoke a Link Session. Check this if you decode the token from Generate a Linking URL to read apiKey, profileKey or exp: it is now an opaque string beginning ayr_ls_ rather than a JWT, so read expiry from expiresIn and use the keys you sent.
• August 27 - Fewer Unneeded Instagram Relinks. Instagram “Generic Internal Error” responses now tell you to retry the post instead of relinking a healthy account. If the error persists, details includes the fbtrace_id to share with Meta support. See error codes. Check this if you relink accounts when code: 258 carries relink: true: Instagram Generic Internal Errors (error_subcode 2207085) now return code: 258 without relink: true, so retry the post in a few minutes instead.
• August 26 - Spot Expired Connections From Messages Webhooks. Facebook and Instagram message webhooks now carry connectionDegraded: true when a User Profile’s connection may need relinking. If every message from a profile carries it, ask that profile to relink; a single flagged message is a passing blip. Messages keep arriving, and the field is omitted on healthy connections. See New Message Events.
• August 25 - Webhooks That Ride Out Endpoint Outages. Webhook events now reach your endpoint even when it is down for hours during an incident or maintenance window. This covers timeouts, dropped connections, and 5xx, 429, 408 and 425 responses. See Webhooks Overview for the full contract. Check this if you deduplicate webhook events or your endpoint can return a 4xx: retries used to end within about 35 seconds and can now arrive up to about 16 hours after the event, so keep deduplication keys for at least 24 hours, and a 400, 401, 403, 404 or 410 is final on the first attempt, including a 404 while you deploy.
• August 24 - Ayrshare Post ID on Comment and Mention Webhooks. The comments and mentions webhooks now include postId, the Ayrshare id returned when you created the post, so you can match events to your posts without keeping your own id map. It is omitted when the post was not published through Ayrshare by that User Profile, or predates this change. See Correlating a comment with the post you created.
• August 24 - Network Name on Comment and Mention Webhooks. The comments and mentions webhooks now include a platform field (instagram or facebook on comments, always instagram on mentions), so one endpoint can branch on the network directly. Every other field is unchanged. See Comments Action.
• August 19 - WhatsApp Business Profile Editing Through the API. Send whatsapp to Update User to change your WhatsApp business profile: about, description, address, email, up to two websites, vertical, and the photo via profilePictureUrl. Read the current profile with WhatsApp Business Profile. The display name is not editable here.
• August 18 - Clearer Retryable Errors During Media Checks. If Ayrshare cannot complete its media check before posting, you now get a retryable error, so you know to try again rather than change a working media URL, CDN or user-agent rule. Genuine media-access problems keep their existing errors. See Media Fetch / Crawler Access Errors. Check this if you handle code: 164 on posts: when the media check itself is unavailable, posting now returns retryable code: 499 (HTTP 503) instead of code: 164 (HTTP 400), so retry the post.
• August 18 - YouTube Engaged Views in Analytics. Post Analytics and Social Analytics now return engagedViews for YouTube, counting views past the first seconds of playback. From August 24, 2026, YouTube counts views from the start of playback, so use engagedViews where reports need the previous methodology. See Upcoming API Changes.
• August 17 - Your Brand Colour on the Main Linking Dialog Button. The Submit and Yes buttons in the connect accounts dialogs now use your colour, with a readable label and spinner chosen for you. Set to pick your own label colour. See Linking Dialog Colors.
• August 17 - First Comments on Scheduled Instagram Posts. Scheduled Instagram posts now add their firstComment, the same as immediate posts. Check this if you add the first comment to scheduled Instagram posts yourself: remove that step or stop sending firstComment, or the comment will appear twice.
• August 17 - Suspended Webhook for Profile Suspension Events. Register the new suspended webhook action to hear the moment a User Profile is suspended or reactivated, so you can pause and resume posting automatically. Events include the reason, platform and origin when available. Register it with Register Webhook; payloads are in Suspended Action.
• August 16 - Custom Colors for Linking Dialogs. Style the dialogs on your white-labeled connect accounts page, from page pickers to credential forms, with ten new custom properties such as and . Set them on :root, not on a card, since dialogs render outside the page; anything unset keeps today’s colors. See Linking Dialog Colors.
• August 15 - Your Custom CSS From the First Frame. White-labeled connect accounts pages with your own CSS file now show your styling from the moment they open, including when users return after connecting an account. Linking pages without a CSS file are unchanged.
• August 14 - More Custom CSS Hooks Inside Connect Accounts Cards. Your Max Pack custom CSS can now target account avatars, network icons and names, and the page column and header, with five new class names such as social-account-avatar. Set and on social-account-card to color the Connected and Messaging badges. Use these names rather than generated Mui class names so your rules keep working.
• August 14 - More Space Above Your Linking Page Content. The white-labeled connect accounts page now gives your logo and heading more room below the top of the browser window. A stylesheet that already sets padding-top on main-content keeps its own value.
• August 13 - YouTube Channel Identity on the Social Webhook. The social webhook now includes an optional account object naming the account that was linked or unlinked, starting with YouTube, so you can identify the channel without a follow-up /api/user call. It carries account.id, account.title, account.handle and account.profileUrl. See the Social action webhook reference.
• August 12 - AI Disclosures Kept on Converted Images. AI disclosures on WebP, HEIC, HEIF and AVIF images now reach the network when those images are converted to JPEG, so Facebook and Instagram show their AI label. No EXIF, GPS, creator or copyright data from your original image is shared. Leave Instagram’s autoResize off if the disclosure needs to reach Instagram. See Image Metadata and Content Credentials.
• August 12 - Reliability and Performance. Faster LinkedIn company page selection for accounts that manage many pages, with more complete page lists.
• August 11 - Custom CSS Control Over Connect Accounts Card Layout. Control card spacing and cards per row on the white-labeled connect accounts page with two new class names for your Max Pack custom CSS: social-accounts-grid and social-account-card-wrapper. Your rules still need !important. See Change the Card Layout. Check this if your stylesheet reaches the card area by counting elements down from main-content, such as .main-content > div > div > div: those rules now match a different element, so rewrite them against social-accounts-grid and social-account-card-wrapper.
• August 11 - Custom CSS Linking Pages Stay on Your Colors. A social linking page with your own CSS file now always uses the light color scheme your stylesheet is written for, so network names stay readable on your cards. Linking pages without a CSS file keep the light/dark switch.
• August 11 - Streamlined Instagram Linking. Clicking Instagram on the linking page now goes straight to login, and when you use Instagram Login, Instagram’s own login offers to switch a personal account to a professional one along the way. A custom Instagram modal still appears exactly as before.
• August 10 - Stable CSS Class Hooks on the Connect Accounts Page. Your Max Pack custom CSS can target documented class names on the white-labeled connect accounts page, including main-content, close-button and connected-card. Rules built on these names keep working with no change. New unlinked-card and data-platform hooks let you style unconnected cards as buttons. Rules need !important. See CSS Class Hooks. Check this if your stylesheet uses generated class names (such as names beginning chakra-) or linked-tag: those are gone, so rewrite generated-name rules against the documented class names and style connected-card instead of linked-tag, as described in Updating an Older Stylesheet.
• August 7 - Dashboard 3.0. The Ayrshare Dashboard is rebuilt with a new design, dark mode and a faster, cleaner workflow on every page. Manage your plan, invoices and add-ons in the new Billing section, see the exact API request for a post with View API Code, and inspect webhook event logs in the new Events tab.
• August 6 - TikTok Video Visibility. Set tikTokOptions.visibility to “private”, “followers” or “friends” on TikTok video posts as well as image posts. See the visibility parameter. Check this if you send tikTokOptions.visibility on video posts: those videos now publish as “private”, “followers” or “friends” as requested instead of Public, and “private” posts stay pending with no TikTok webhook until made public, so drop the value for videos you want public.
• August 6 - Instagram AI Content Label. Set instagramOptions.isAIGenerated to true to add Instagram’s AI info label to images, videos, Reels, Stories and carousels. It matches tikTokOptions.isAIGenerated, and the label cannot be changed after publishing. See Instagram AI Content Label.
• August 4 - X “Made with AI” Label. Disclose AI-generated media on X posts with twitterOptions.isAIGenerated, which applies X’s native “Made with AI” label. See X posting options.
• August 4 - LinkedIn Comment Replies on Organic Company-Page Posts. Reply to comments on organic LinkedIn company-page posts by Social Comment ID. With searchPlatformId: true, pass the full commentUrn from get-comments. See the new commentUrn parameter on Reply to a Comment.
• August 4 - Clearer Instagram Automation Activity Statuses. Instagram automation activity now shows why a DM did not reach a recipient, with Meta’s reason on actionResults[].errorDetails, so you only relink when credentials truly need it. Testing on your own post records skipped with an explanation. See activity statuses. Check this if you treat auth_error automation activity as a relink signal: per-recipient DM delivery failures now record failed, comments from the sending account record skipped, and auth_error now means a genuine credential or permission problem.

​

July 2026

• July 31 - WhatsApp Messages in Private Beta. The Messaging API now supports WhatsApp in private beta. Approved accounts can link a WhatsApp Business Account through Meta’s embedded signup flow, send free-form messages during Meta’s 24-hour customer service window, receive incoming messages and media, and retrieve stored WhatsApp conversations. Email lotty@ayrshare.com to request access.
• July 31 - Instagram Comment & Mention Webhooks No Longer Require Messaging. Instagram comments and mentions webhooks are now fully independent of the Messaging add-on. Registering a webhook with action: “comments” or action: “mentions” subscribes the required Meta fields automatically using your existing linked accounts — no Messaging add-on and no relinking required (comment permissions are already part of the default grant). This works for every Instagram account type, including accounts linked through a Facebook Page, and disabling Messaging no longer disrupts an active comments or mentions webhook. This change applies to the Instagram scope; Facebook comment and mention events are not yet included. See the Webhooks overview to register a webhook.
• July 31 - Batch Analytics Attribution Fix. In a multi-post post analytics request, a failing entry could cause subsequent results in the same batch to be recorded under the wrong post ID. Results are now always attributed to the correct post, even when some entries in the batch fail.
• July 31 - Instagram Analytics Post-ID Validation. Invalid Instagram post IDs sent to post analytics are now rejected locally before any call is made to Meta, so malformed IDs no longer cost a Meta Graph API call — matching the protection already in place for Facebook, Threads, and X/Twitter. Numeric post IDs are also handled gracefully: an all-digit numeric id validates normally, and values that can’t form a valid ID return a clean code: 186 error instead of an unhandled failure. Valid string IDs behave exactly as before.
• July 31 - n8n Starter Workflow Refresh. The downloadable n8n MCP starter workflow has been updated: the suggested first prompt now targets LinkedIn and Facebook only (the previous prompt included Instagram, which requires media and caused first-run validation to fail), and the workflow’s chat model is now claude-sonnet-5 with version-agnostic setup instructions.
• July 29 - Instagram Comment Automations Now Use Private Replies. Comment-triggered automations (comment_keyword) now deliver their DM through Instagram private replies, anchored to the comment’s own 7-day window. This removes the requirement for a prior conversation, so an automation can now reach a commenter you have never messaged before — the rejection that previously blocked cold commenters. The comment’s own 7-day window still applies: a reply to a comment older than that fails with 491. Note that delivery is still ultimately dictated by the recipient’s Instagram Message requests setting: a DM can be accepted by Instagram (activity status: “sent”) and then silently dropped, with no signal on any API surface. Accordingly, sent means Instagram accepted the message, never that the recipient received it. New failure reasons surface on actionResults[].errorDetails with dedicated error codes 490–495. See the new Automation DM Sent but Not Delivered troubleshooting guide.
• July 23 - Post-Quantum Ready Encryption (PQC). The Ayrshare API now supports post-quantum cryptography at the TLS layer. We’ve enabled the X25519MLKEM768 hybrid key exchange on our global SSL policy, adding a quantum-safe (ML-KEM) algorithm alongside classical ECDHE in the TLS 1.3 handshake. This protects your API traffic against “harvest now, decrypt later” attacks — where an adversary records encrypted traffic today to decrypt once quantum computers mature. The change is fully backward compatible: because it’s a hybrid negotiation, a connection only upgrades to PQC when the client requests it, and every other client continues to connect normally over standard ECDHE. And since 74% of our API traffic is already on TLS 1.3, most integrations get post-quantum protection right now with no code changes — as long as your HTTP/TLS library supports the X25519MLKEM768 group (OpenSSL 3.5+ and other modern TLS stacks already do), it’s negotiated automatically.
• July 15 - Instagram Reels Aspect-Ratio Validation Fix. Tall and narrow Instagram Reels are no longer falsely rejected before reaching Meta. Ayrshare’s pre-flight video check was applying the Instagram image aspect rules (4:5 to 1.91:1, plus a 9:16 portrait exception) to Reels, so a valid portrait Reel (for example 886 x 1920, a 0.46:1 width-to-height ratio) was blocked locally with code: 182 even though Instagram would accept it. Reel videos are now validated against the documented Reel range of 0.01:1 to 10:1 (9:16 still recommended to avoid cropping), matching Meta’s own specification and the Instagram media guidelines. The code: 182 message for aspect-ratio failures has also been corrected — it previously read “Video does not meet duration requirement.” No API changes are required.
• July 14 - Partial Success on Multiplatform Comments & Analytics Reads. A multiplatform get-comments or post analytics read (one Ayrshare Post ID spanning several platforms) no longer collapses the whole response to an error when a single platform’s leg fails. When at least one leg succeeds and at least one fails, the response returns HTTP 200 with status: “partial”, preserving healthy platform data and listing each failed leg in top-level errors[]. All-success responses are unchanged. All-fail responses retain status: “error” and map the representative top-level error code to its configured HTTP status; code 485 maps to HTTP 404. Code 485 identifies expired or unavailable Instagram/Facebook Story comments and Instagram Story analytics when comments or insights cannot be retrieved; Facebook Story analytics remain unavailable and are not included. Clients should inspect errors[] and match the numeric code, not exact message text.
• July 8 - Faster API Response Times. We’ve shipped a round of backend performance work that meaningfully cuts latency across some of our most popular endpoints. Average and 95th-percentile (p95) response times are both down substantially, with the largest gains showing up when under heavy load. The biggest wins are on profiles and analytics. No API changes are required; every request is now faster automatically.

  Endpoint	Faster Avg	Faster p95
  GET /profiles	-71.6%	-88.7%
  GET /analytics	-59.5%	-75.0%
  GET /user	-51.0%	-48.6%
  GET /post	-47.6%	-63.1%
  GET /messages	-40.5%	-59.4%

• July 7 - Per-Session Instagram Link Method on generateJWT. The generateJWT endpoint now accepts an optional instagramLinkMethod body parameter that overrides your account-wide Instagram Login setting for a single linking session. Send “instagram” to start direct Instagram Login (no Facebook Page required) or “facebook” to link via a connected Facebook Page when the user clicks the Instagram button on the social linking page. The override applies only to the linking page opened from the returned JWT URL — it persists across the authorization redirect but never changes your account-wide setting, and omitting the parameter keeps the existing behavior. Invalid values return a 400 listing the valid options. See the new Instagram Link Method section for details, including the feature differences between the two flows.

​

June 2026

• June 24 - n8n Integration. Connect n8n to the Ayrshare MCP Server using n8n’s built-in MCP Client Tool node, with no custom code and no community node to install. See the new n8n integration page for an overview, and the full n8n guide for setup, three worked examples, multi-tenant profiles, X BYO, and a downloadable starter workflow (Chat Trigger to AI Agent to the Ayrshare MCP node). See also Connect & Setup and the Tool Catalog.
• June 17 - Facebook Analytics: Meta Retired Reach & 3-Second Video Metrics. Meta removed the unique-impression and 3-second video-view Insights metrics across all Graph API versions (effective June 15, 2026). Facebook post analytics no longer return impressionsUnique, impressionsFanUnique, impressionsOrganicUnique, impressionsPaidUnique, or videoViewsUnique, and social analytics no longer return the pagePostsImpressions* family (including pagePostsServedImpressionsOrganicUnique). The still-supported fields (reactionsByType, videoViews, mediaView, pagePostEngagements, pageVideoViews) are unaffected. Use mediaView / pageMediaView for reach; a Total Unique Media Views successor is planned. Reference: Meta Graph API v25 changelog.
• June 15 - Facebook Account Restriction Error Code 476. Facebook posts that fail because Meta has placed a restriction on the account (Meta subcodes 2424009 and 1404078, or Meta’s restriction wording when no subcode is present) now return a dedicated, non-retryable code: 476 (HTTP 400) instead of the generic retryable code: 108. The account stays linked — resolve the restriction via Meta’s Account Status page (Facebook → profile picture → Help → Account Status), which surfaces the specific reason and an appeal flow that the API can’t return. See Facebook Account Restriction for details.
• June 10 - LinkedIn Personal Profile Analytics. Personal (member) LinkedIn profiles now return an expanded analytics matrix. Post analytics include impressionCount, uniqueImpressionsCount (members reached), likeCount, commentCount, shareCount, engagement, reactions, and — for video posts — videoViews, videoViewers, and videoWatchTimeMs. Social analytics add lifetime followersCount, daily followersDaily growth, and aggregate post metrics. Aggregate reshare/reaction/comment counts are best-effort and may differ slightly from the LinkedIn UI. Existing linked accounts must re-link their LinkedIn profile on the Social Accounts page to grant the new analytics scopes — until then, analytics return code: 475 (“re-link your LinkedIn profile to enable analytics”). Posting is unaffected.
• June 10 - TikTok First Comments Now Event-Driven. A first comment on a TikTok post is no longer attempted on a fixed timed wait. Because TikTok processes videos asynchronously, the /post response now returns the TikTok first comment with status: “pending”, and the comment is posted automatically once TikTok finishes processing and the tikTokPublished webhook resolves the real video id. The video visibility must be public, otherwise a clear comment error is returned. Separately, get-comments on a still-processing TikTok post now returns code: 288 instead of a generic failure.
• June 8 - Webhook Signing-Secret Rotation. You can now safely rotate your webhook signing secret from the Webhooks dashboard in 2 clicks, or via the new POST /hook/webhook/secret endpoint with a secret body parameter. After a rotation, deliveries are signed with both your previous and new secret for a 24-hour grace window via the new X-Authorization-Content-SHA256-V2 header (v1=<current-sig>,v1=<previous-sig>, current first), so you can update your receiver with zero dropped or rejected deliveries. The existing X-Authorization-Content-SHA256 header is unchanged. The signing secret is profile-wide (one per User Profile, signing every action on that profile). See Rotate Signing Secret for the safe rotation procedure and a receiver verification example.
• June 8 - YouTube Thumbnail Failures Now Surfaced. When a YouTube video posts but its custom thumbnail fails to apply, the YouTube result now keeps status: “success” (the video stays live) and adds a warnings array (feature: “thumbnail”, code: 307) describing the failure — previously the failure was buried in the thumbNail sub-object, which is still retained for backward compatibility. The misleading 403 guidance has been corrected to lead with channel phone verification at https://www.youtube.com/verify (an unverified channel is the dominant cause), with OAuth re-link as a secondary step. New pre-publish validation also catches thumbnails that are not PNG/JPG, are over 2MB, or are unreachable before upload and skips them, so the video still posts with the reason reported in warnings (a thumbnail problem never fails the post). See the YouTube Post API and the new YouTube Thumbnail Not Applied (Unverified Channel) troubleshooting guide.
• June 8 - X BYOK Analytics Now Returns Code 416 on Depleted Credits. When an X/Twitter BYOK account’s enrolled X Developer account is out of API credits, the analytics and user-lookup paths now return code: 416 (HTTP 402, X CreditsDepleted) with the enrolled account id in the detail — previously these were masked as code: 294 (HTTP 400, “Unable to get X User”). The fix is to top up credits in the X Developer Portal. This aligns the analytics/lookup surface with the publish path (which already returns 416). If your integration branches on 294 from analytics to detect a bad handle, add handling for 416.
• June 4 - MCP Server & Claude Code plugin. AI agents can now drive the Ayrshare API through the new MCP Server (https://api.ayrshare.com/mcp), including the Claude Code plugin. See Connect & Setup and the Tool Catalog. The existing docs-search MCP is now Documentation MCP.

​

May 2026

• May 22 - Bulk Post Profile-Key Routing Fix. POST /post/bulk now honors the Profile-Key header, so CSV rows publish to the resolved User Profile instead of the Primary Profile. Previously bulk uploads sent with a Profile-Key were silently routed to the Primary Profile’s social accounts. See Bulk Post.
• May 21 - TikTok DELETE /comments scope clarified. Updated the Delete Comments and Comments Overview pages to document that DELETE /comments on TikTok only succeeds for comments authored by the authenticated TikTok account itself (your own replies). Attempting to delete a third-party comment returns Ayrshare code: 328. Customers who need to moderate third-party comments on their own TikTok videos should contact support. No API behavior change; documentation only.
• May 21 - Hide TikTok Comments. DELETE /comments now supports hiding a TikTok comment from public viewers via hide=true together with videoId. The success response returns action: “hide” and echoes the comment text; sending hide=true without videoId is rejected with a 400. Hidden comments remain visible to the video owner in TikTok Studio.
• May 20 - Node SDK v1.3.0 — X/Twitter BYO support. The official Node SDK now exposes setTwitterByo(apiKey, apiSecret) and clearTwitterByo() for X/Twitter Bring-Your-Own-Keys. Once set, every SDK request includes the required X-Twitter-OAuth1-Api-Key and X-Twitter-OAuth1-Api-Secret headers — required for X/Twitter operations now that Ayrshare’s BYO requirement is enforced (as of March 31, 2026). Install via npm install social-media-api@1.3.0; release notes on npm and GitHub.
• May 20 - Messaging Metered Pricing. Business Messaging is now billed via Stripe metered pricing at $0.09</code> per active conversation on Launch and Business plans (Premium remains a flat <code>$49/month add-on), with up to 1,000 active conversations per billing cycle. See Messaging pricing.
• May 20 - Instagram Analytics No Longer Unlinks on Permission Errors. When Instagram analytics hits a missing-permission error (Meta errCode 10), the account is no longer automatically unlinked. Previously a scope/permission issue was treated like a revoked token and silently disconnected the account even though posting still worked. Ayrshare now keeps the account linked and surfaces a permission-scope error instead.
• May 19 - Per-profile hideLogo. New hideLogo boolean on Create Profile and Update Profile suppresses the account-wide logo on an individual User Profile’s social linking page. Useful for white-labeling individual partner profiles.
• May 19 - Facebook Boost Ad Set Budget Sharing. The Boost endpoint now accepts a new optional adSetBudgetSharingEnabled boolean (default false). Meta now requires this wire field on every campaign created without a campaign-level budget, and Ayrshare sends it on every request — defaulting to false preserves prior behavior with no caller changes needed. Set it to true to enable Meta’s cross-ad-set optimization, which can shift up to ~20% of an ad set’s budget to other ad sets in the same campaign for better overall performance.
• May 19 - Reddit Banned-Subreddit Error. Posting to a subreddit you are banned from now returns a distinct, non-retry-safe error instead of the generic retry-safe code 121. This stops schedulers from retrying a permanently rejected post in a loop. See Ayrshare error codes.
• May 19 - Bluesky Video Size Limit. The maximum Bluesky video upload size is now 100 MB (previously advertised as 1 GB) to match Bluesky’s platform cap. Files above 100 MB are now rejected up front rather than failing late at upload. See the Bluesky media guidelines.
• May 19 - Dashboard X/Twitter Messaging for BYO Keys. The Ayrshare dashboard Messaging page now supports X/Twitter direct messages for Bring-Your-Own-Keys (BYO) accounts. Your X consumer key and secret are collected in the browser for the session and threaded through send, refresh, and image-fetch actions — no keys are stored. Required now that X/Twitter is BYO-only on Ayrshare.
• May 19 - Facebook Ads Cities Targeting Fix. The Facebook Ads Cities endpoint (GET /ads/facebook/cities) now correctly resolves cities and their associated region data. Each result includes region, regionId, and supportsRegion so you can target a city’s region when available. Use the search query parameter with a partial or full city name.
• May 18 - YouTube Status Field Controls. Three new optional parameters on the YouTube Post API youTubeOptions: license (“youtube” or “creativeCommon”), embeddable (boolean), and publicStatsViewable (boolean — controls the extended statistics panel on the watch page; basic view and like counts remain public regardless). The /history/youtube response now also returns these fields. Two new validation error codes — 455 (invalid license) and 456 (invalid embeddable or publicStatsViewable) — reject malformed requests at the Ayrshare edge. Monetization toggles (enabling/disabling ads) are not included; those require YouTube CMS credentials and are not available via the standard YouTube API.
• May 18 - GMB First Comment No Longer Masks Post Success. Fixed an issue where including firstComment on a Google Business Profile post returned code: 163 with no postIds even though the post succeeded. Google Business Profile does not support post comments, so firstComment is now skipped for GMB and the successful post result is returned normally.
• May 14 - Preventing Account Unlinking. Social networks have been quietly rolling out stricter anti-bot controls, which were causing an unusually high number of user accounts to get unlinked. We’ve rolled out several backend improvements to reduce unlinks and clarify error messages, and updated the account linking page to make the UI much clearer for users — including a new “Action required” state for Meta networks (Facebook, Instagram, FB Groups, Threads, Messenger) when an account hits identity-verification limbo, with a “Resolve with Meta” link and a “Check again” probe so users can fix the issue without unlinking and relinking.
• May 12 - Instagram Engagement Automations (Beta). New Automations API lets your users automatically react to Instagram engagement — fire a DM, webhook, or email when an end user comments on a post, replies to a story, sends a DM, or reacts to a DM. Four trigger types (comment_keyword, story_reply, dm_reaction, dm_keyword) and three action types (send_dm, fire_webhook, send_email) — up to 50 of each per rule. Includes per-action 7-day dedup (configurable per action via dedupWindowMinutes), daily DM caps (1,000 Launch & Business / 5,000 Enterprise), and a cursor-paginated activity log. Available on Launch, Business, and Enterprise plans. New error codes 462–472 cover validation, tier gating, the active-automation cap, missing linked accounts, and feature-flag opt-in. Beta — we are actively collecting feedback; please send bug reports and feature requests to support.
• May 12 - Scheduled Post Throughput Improvements. We’ve added more hardware for processing scheduled posts which is dramatically improving throughput and performance. We’ll be adding more platform specific hardware for YouTube and TikTok soon as well.
• May 12 - Instagram Relink Hint for Account-State Errors. Certain Instagram account-state failures (Meta error_subcode 2207085, previously surfaced as a generic code: 258 with no guidance) returned relink: true and retryAvailable: true with a remediation message instructing the user to unlink and relink the Instagram account granting all permissions. Superseded: 2207085 is now retried automatically and no longer sets relink: true. See error codes.
• May 11 - YouTube transient error codes. YouTube uploads that fail due to transient upstream issues now return new error codes 453 (HTTP 504, Google ingest timeout) and 454 (HTTP 503, service unavailable) with a retryAvailable: true flag your integration can use to retry automatically. See error codes for details.
• May 11 - X/Twitter Analytics & Lookups Open to All BYO Users. The legacy X add-on gate has been removed from /analytics/social and /lookups/x. Any X/Twitter Bring-Your-Own-Keys customer can now look up analytics for arbitrary handles and use the X lookups endpoint without hitting code: 3. Calls are signed with your own X Developer App credentials and count against your own X rate limits.
• May 8 - Python SDK v1.3.0 — X/Twitter BYO support. The official Python SDK now exposes set_twitter_byo(api_key, api_secret) and clear_twitter_byo() for X/Twitter Bring-Your-Own-Keys. Once set, every SDK request includes the required X-Twitter-OAuth1-Api-Key and X-Twitter-OAuth1-Api-Secret headers — required for X/Twitter operations now that Ayrshare’s BYO requirement is enforced (as of March 31, 2026). Install via pip install —upgrade social-post-api; release notes on GitHub and PyPI.
• May 4 - Automatic Image Format Conversion. WebP, HEIC, and AVIF images are now automatically converted to JPEG before posting to platforms that don’t accept them. WebP conversion applies to Instagram, LinkedIn, TikTok, Google My Business, Threads, and Snapchat. HEIC and AVIF are converted across all supported platforms. No API changes needed; conversion runs transparently at send time. New error codes 450 (conversion failure), 451 (source download failure), and 452 (converted-image upload failure) surface when conversion can’t complete.
• May 4 - Instagram errors now include Meta’s raw message. Instagram media-status failures now surface Meta’s underlying error text in the details field alongside the Ayrshare error code, so callers can distinguish causes (for example, robots.txt/crawler issues vs. token problems) without guessing from the generic code. See the Instagram Post API and error codes.

​

April 2026

• April 30 - X/Twitter BYOK in the API Explorer. The Ayrshare API Explorer now includes a collapsible X/Twitter BYOK (Bring Your Own Keys) section so you can paste your X API Key and API Secret once and have them attached as X-Twitter-OAuth1-Api-Key and X-Twitter-OAuth1-Api-Secret headers on every outgoing request — no more dropping to curl or Postman to test BYOK from the Explorer. Values are scoped to the current browser tab via sessionStorage, masked by default with a reveal toggle, and cleared with one click. See the X BYO Key Setup Guide for how to obtain your credentials.
• April 28 - Social Analytics Enhancements (rolling out). The Social Analytics endpoint is gaining Instagram shareCount (total shares aggregated over the 90-day rolling window) and YouTube lifetimeLikes (opt-in via youtube: { lifetime: true }); the new fields will appear in responses as the deployment reaches your account. Documentation corrections included in this update: Instagram viewsCount is a 90-day rolling window (not 180 days), mediaCount is always lifetime, YouTube likes is scoped by quarters, and TikTok profile-level metrics are capped at 60 days with per-post lifetime semantics when quarters is used.
• April 28 - Instagram Trial Reels. The /post endpoint now supports publishing Instagram Trial Reels — Reels visible only to non-followers when first published. Set instagramOptions.trialParams.graduationStrategy to “MANUAL” (graduate from inside the Instagram app) or “SS_PERFORMANCE” (Meta auto-graduates based on early performance). Three new validation error codes — 447, 448, 449 — reject invalid trial-reel requests at the Ayrshare edge.
• April 24 - Instagram Posting Reliability. Expanded automated retry handling for Instagram during busy times and improved error messages across the board. Instead of generic errors, you’ll now receive specific error codes for rate limits (code: 435) and media processing timeouts (code: 436) — making it easier to diagnose issues and build smarter retry logic in your integrations.
• April 23 - Facebook Analytics Rate Limit Error Code 444. Facebook Page per-Page analytics throttles (Meta error 80001) now return code: 444 (HTTP 429) on post and social analytics responses. Previously these throttles were misclassified as code: 161 (“relink your account”). If your integration branches on 161 to trigger a relink flow, update it to recognize 444 and retry with backoff instead. See Facebook Analytics Rate Limit for details.
• April 23 - Meta Media Crawler Troubleshooting. New help-center guide on fixing error code: 440 (“social network could not download media from this URL”) and the related Instagram code: 138 / Threads code: 379, all caused by robots.txt or bot rules blocking Meta’s publishing crawler. See Meta Media Crawler Blocked.
• April 21 - Moderation input errors now return 400. POST /validate/moderation now returns new error code 438 (HTTP 400) for caller-input problems (e.g. an unsupported file as imageUrl, or an unreachable/malformed URL) instead of a misleading 500 with retry guidance. Genuine processing failures still return code 331 (HTTP 500). See error codes.
• April 20 - Caption Enhancement Error Code 441. The Post endpoint now returns error code: 441 (HTTP 502) when a caption enhancement such as shortenLinks fails. When the failure affects only some platforms, the successful platforms still post and appear in postIds alongside a top-level status: “error” and per-platform entries in errors[]. See Caption Enhancement Errors for details.
• April 15 - Instagram dead-token detection. Instagram posts that fail because of an invalid/expired OAuth token — or a page-role/permission error (Meta subcode 492) — now return Ayrshare code 161 (authorization error) and automatically unlink the affected account so the user is notified to relink, instead of the misleading generic code 138 “please try again” response that previously masked these cases. See error codes and the Instagram Post API.
• April 9 - Instagram & TikTok Analytics All-Time Data & Date Filtering. The social analytics endpoint now returns all-time Instagram and TikTok data when neither daily nor quarters is specified. Use quarters (1–4, where 1 = 90 days) or daily=true to filter by date range — now supported on TikTok as well. When active, TikTok comment, share, and view period labels and totals reflect the filtered date range.
• April 9 - Analytics Reliability and Recovery. The Social Analytics and Post Analytics endpoints now automatically backfill cumulative metrics (followers, likes, views) from stored data when the social network temporarily returns zeros. Two new optional response fields, backfilledFrom and recoveredFrom, indicate when stored data was used. Additionally, requesting analytics when no platforms return data now returns a 400 error (code: 187) instead of an empty success response.
• April 1 - generateJWT Header-Based X Credentials. The Generate JWT endpoint now accepts X-Twitter-OAuth1-Api-Key and X-Twitter-OAuth1-Api-Secret headers for passing your X consumer keys — consistent with all other X/Twitter endpoints. Body parameters remain supported for backward compatibility.

​

March 2026

• March 30 - X Credit-Depletion Errors Surfaced. When a BYOK X/Twitter Developer account runs out of API credits, posts that previously got stuck in processing with no error now correctly fail with code: 416 (X Credits Depleted, HTTP 402). Detection for code: 416 has been broadened to also catch X’s HTTP 429 responses that mention credits. See error codes for details.
• March 28 - Instagram Post Null Response Fixed. Resolved an edge case where an Instagram post would succeed on the platform but the /post response returned null instead of the normal success body with postIds and id. Successful Instagram posts now always return a valid response your integration can parse.
• March 26 - Instagram Daily Reach Fix. Fixed an issue where Instagram Social Analytics omitted daily reach data when daily=true was set. The response now returns a nested reach object (with period and a values time-series) in daily mode; the scalar reachCount is still returned in non-daily mode and is preserved as a fallback when daily data is temporarily unavailable.
• March 26 - X/Twitter BYOK Enforcement Error Codes. With the Bring Your Own Keys requirement now enforced, X/Twitter requests return specific error codes you can branch on: 419 (HTTP 400, missing X-Twitter-OAuth1-Api-Key/Secret headers), 416 (HTTP 402, X Developer account out of credits), and 417 (HTTP 403, OAuth 1.0a app permissions not set to Read/Write/DM). See error codes for messages and resolutions.
• March 23 - Keyword Search on X. New keyword search endpoint for BYOK customers. Search X/Twitter for tweets matching keywords, hashtags, and advanced search operators. Supports pagination, filtering by language and location, and returns normalized tweet data.
• March 23 - Listening Section. A new Listening section has been added, expanding on the Brand endpoints with new features like keyword search.
• March 19 - @Mentions in Comments. Added documentation for @mention support in the comment text string on the Post a Comment and Reply to a Comment endpoints. Includes LinkedIn server-side resolution details and links to platform-specific mention syntax.
• X/Twitter Paginated Messages. The Get Messages endpoint now supports a limit query parameter for X/Twitter, allowing you to fetch only the latest N messages (1–100) without a full history sync. Combined with cursor-based pagination via the next parameter, this enables efficient polling — fetch a small batch, check if you already have them, and only page further if needed.
• Increased Video Size Limits. With so much of social publishing now focused on video content, we increased our video upload limits across multiple platforms: LinkedIn (200 MB → 500 MB), TikTok (1 GB → 10 GB), X Premium long video (1 GB → 16 GB), and added larger content-type-specific limits for Facebook (Reels 2 GB, Stories 4 GB, Feed 10 GB) and Pinterest (2 GB). See the Media Guidelines for full details.
• X/Twitter Messages BYO Key Support. Get Messages and Send Message endpoints now support BYO (Bring Your Own) X/Twitter API credentials. Real-time DM notifications via webhooks are not available for BYO users; use polling via the GET Messages endpoint instead.
• Bring Your Own Keys on X. A major change to how X/Twitter accounts are connected. The new Bring Your Own Keys approach gives you more control of your account, better data portability, and a branded OAuth flow. All users need to make the transition by March 31, 2026.
• Editable Short Links. You can now update short links after they’ve been published.
• Scheduled Post Processing Reliability. Resolved an issue where the scheduled post processing job could run out of memory and return 503 errors. Increased resource allocation, added paginated query processing, and introduced a distributed application lock to prevent duplicate execution — ensuring single, reliable runs for all scheduled post processing.
• Facebook & Instagram History Improvements. Improved the /history/facebook and /history/instagram endpoints: for Facebook, expired/archived Stories are now filtered out by default so only active Stories appear alongside regular posts, and new since and until query parameters allow time-based filtering with ISO UTC date strings. For both Facebook and Instagram, a new dataType parameter lets you request only posts, only stories, or both (default).
• X Rate Limits Removed. As part of the X/Twitter BYO Keys migration, Ayrshare no longer enforces monthly or daily rate limits on X analytics. Your usage is now governed by your own X Developer account limits.

​

February 2026

• February 25 - X/Twitter Video Titles & Descriptions. Videos posted to X/Twitter now support setting a videoTitle and videoDescription (sent on the twitterOptions object of the X Post API) for media uploaded to X Media Studio. These accompany the existing thumbNail support for richer video metadata.
• Batch Analytics. Added support for batch analytics of social post IDs, allowing up to 100 posts per analytics call using the new postIds parameter. Read about it on our Analytics on a Post by Social ID endpoint.
• History Pagination. Added pagination support to the posts history for a platform API for Threads and X/Twitter. No more 500 post limit — you can now pull longer history using pagination, and split calls into smaller chunks for faster, more efficient responses.
• Free Trial Enhancements. Free trial users can now test the Messaging API and Max Pack — you won’t be charged until the end of the free trial period.
• Improved Error Messages. Added additional detail to X/Twitter and LinkedIn error messages, making it easier to diagnose issues with your API calls.
• Instagram Comments Fix. Fixed an issue where top-level Instagram comments with nested replies were not being returned correctly from the Get Comments endpoint.
• Python SDK. Updated our Python SDK with the latest features and improvements.
• X/Twitter Webhook URL. A new ayrshareUrl field is now included in Direct Message Event webhook payload, providing an unauthenticated URL for convenience.
• Status Page Slack Integration. You can link updates from our Status Page into Slack automatically. Just click “Get Updates” in the upper right and select the Slack option.

​

January 2026

• January 21 - Link Analytics Custom Domain Fix. The Link Analytics endpoint (GET /links/:id) now returns short links using your configured custom domain instead of the default Ayrshare domain. If you use a custom short-link domain (Business/Enterprise), analytics URLs now match your live links.
• January 15 - Instagram Outbound Message Deletion Sync. When an Instagram outbound (sent) message is deleted in the native Instagram app, it is now correctly marked as deleted in Ayrshare’s Messages data — matching the existing behavior for inbound messages. Conversation history now stays accurate for both directions.
• MCP Server. Back by popular demand — we’ve relaunched our MCP Server! Connect your AI tools directly to the Ayrshare API.
• Self-Serve Signup. Added a new self-serve signup for the Business Plan and Launch Plan. New customers can now access a 14-day free trial of the Launch Plan to test the Ayrshare platform.
• X/Twitter Video Thumbnails. X/Twitter video posts now support including a thumbnail preview image (as a URL). This is sent as part of the metadata when uploading a video.
• Instagram Hashtag Limit. Changed the hashtag limit on Instagram posts to 5 to align with new guidelines published by Instagram.
• Bluesky Video Duration. Bluesky video media duration limit has been adjusted to three minutes to be in line with Bluesky API requirements.

​

December 2025

We’re ending this year focused on transparency and reliability, with a ton of new feature releases planned in Q1 2026.

• December 23 - X/Twitter URL Entities in Response. X/Twitter post and history responses now include URL entity data for links in a tweet’s body: a top-level urls array carrying X’s raw fields (display_url, expanded_url) plus a camelCased entities object where the same links appear as entities.urls[].displayUrl / expandedUrl — making it easier to render link previews and detect outbound links in your integration.
• X/Twitter Entities. The post analytics and platform history endpoints for X/Twitter now return parsed entities from the tweet text, including URLs, mentions, hashtags, and cashtags with their positions and display URLs.
• Facebook Post Analytics. New metrics added to Facebook post analytics including mediaView, mediaViewIsFromAds, and mediaViewIsFromFollowers to replace deprecated impression metrics.
• Bluesky Comments. Improved support for Bluesky comment retrieval with proper handling of AT Protocol-style post and comment IDs.
• Threads Linking. Enhanced Threads account linking to handle cases where the name or username fields are not present on the account.
• 24/7 Monitoring. Onboarded a dedicated DevOps team to monitor the platform around the clock for improved reliability.
• Monthly Receipts. Automatic monthly receipts are now emailed to the primary account holder, providing better transparency around pricing and payments.

​

November 2025

• Instagram Token Refresh. Added automated refresh for long-life Instagram tokens for users who link to Instagram using direct IG login (without Facebook Page).
• Facebook Analytics Updates. Facebook post analytics now returns enhanced impression metrics including post_impressions_paid_unique, post_impressions_fan_unique, post_impressions_organic_unique, and post_impressions_unique.
• Facebook Page Insights. New Facebook social analytics fields added: pageFollows, pageMediaView, pageMediaViewIsFromAds, and pageMediaViewIsFromFollowers with both aggregate and daily breakdown support.
• Instagram Analytics. Instagram social analytics viewsCount and reachCount metrics are now supported with both direct Instagram Login and Facebook-linked accounts.
• LinkedIn Mentions. Fixed handling of LinkedIn mentions to properly distinguish between mentioning organizations versus individuals.
• Dashboard Improvements. The Ayrshare web dashboard API page has been refactored with improved performance and a better organized messaging usage card.
• Team Expansion. Expanding the development team to speed up support and feature development.

​

October 2025

• Ayrshare Acquired by Saas.group. Ayrshare has been acquired by Saas.group. The team is expanding to deliver faster feature development and better customer support.
• Webhook History. New endpoint to get webhook history per action for the past 6 months.
• Facebook Ads Location Targeting. In addition to country targeting, you can now specify a region or city when boosting Facebook posts.
• LinkedIn Video Thumbnails. The LinkedIn history endpoint now returns the thumbnailUrl for video posts, making it easier to display video previews in your application.
• Reddit Post Analytics. Reddit post analytics reliability has been improved with enhanced authentication handling to avoid rate limiting issues.
• Instagram History. Improved handling of large result sets in Instagram post history for accounts with many posts.
• Facebook Ads. The Facebook ads history endpoint now includes clarification on which ads are returned based on the campaign structure.
• Instagram Collaboration. Added documentation clarifying that accepted collaboration posts may not return from the platform history endpoint due to Instagram API limitations.

​

September 2025

• TikTok Drafts. Sending a post to TikTok drafts now supports images as well as videos.
• Facebook Ads. As part of the requirements set forth by the European Union Digital Services Act (DSA), Facebook requires ads targeting any part of the EU to provide values defining the beneficiary and payor of the ad being created. You can now look up the DSA recommendations and add it to the ad.
• Media Management. The GET media endpoint has been enhanced to include large media files uploaded, and now shows the expireAt field.
• Threads Posting. Easily create a thread on Threads (aka threadstorms), which is a series of connected posts on Meta Threads.
• Direct Messaging. Facebook and Instagram Messaging now support sending audio files (AAC or WAV).

​

August 2025

• Reddit Analytics. New Reddit social analytics data on a user. This includes friend count, follower acceptance, suspension expiration date if the account was suspended, and more.
• Threads Analytics. New Threads social analytics data on a user. This includes bio, geo restriction eligibility, username, and more.
• Threads Geo Restrictions. On Threads, you can set geographic restrictions to only allow posts to show in certain countries.
• LinkedIn Distribution. Disable the ability for other users to re-share your LinkedIn posts.
• Ayrshare Status. In addition to email alerts, you can get the social network and Ayrshare system status via an endpoint.
• YouTube Watermark. Set a watermark image on your YouTube channel that will appear on all your videos. The watermark can be configured to appear at specific times during video playback.

​

July 2025

• Instagram Login. The Instagram Login feature is generally available on July 6, 2025. All new Instagram connections will use the new Instagram Login feature. Current connections will not be affected. If you don’t want to use the new Instagram Login feature, you can disable it in your account settings.
• LinkedIn Mentions. You can now mention another LinkedIn profile either by their vanity name or actual name.
• LinkedIn Search. Search for LinkedIn companies or people based on a search query. This endpoint is commonly used for typeahead mention completion in social media posts.
• LinkedIn Videos. LinkedIn now accepts video files up to 500 MB in size, up from 200 MB previously.
• X Account Activity. Get the full account activity from X via a webhook including posts, likes, mentions, DMs, and more. The X Account Activity feature must be enabled for your linked X account to receive these webhooks. Please contact your account representative to enable this feature.
• X Geographic Restrictions. Set allowed and blocked countries for your X media.
• X Posts Limited to Subscribers. You can set a X post to only be visible to subscribers.
• X Reply Settings. On X, you can allow only certain types of users to reply to your post. You can choose either followers, mentioned, subscribers, or verified users.
• TikTok Thumbnail. Set a custom thumbnail for TikTok videos.
• Instagram Analytics. Instagram analytics on a post now includes the direct link to the media.
• Developer Dashboard. You can now register Webhooks directly in the Ayrshare dashboard.
• Skip Pre-Validation. There is now an option to skip pre-validation on scheduled posts.
• Premium Plan History. Premium plans now have access to the history by platform to get all posts, even those not sent via Ayrshare.
• Auto Repost. You can now get post history by auto repost ID. When creating an auto repost, an ID is assigned to track that series of posts. You can now retrieve the auto repost either by the ID or by getting all.

​

June 2025

• Instagram Login (coming soon). Enable or disable Instagram Login on the social linking page. Instagram Login will be enabled by default in the coming weeks. If you require the advanced features listed including hashtag search, collaborations, location tagging, or brand data, you must manually disable this option to use Facebook Page authentication instead. We recommend most clients use the new direct Instagram Login since it is a simpler work flow and does not require a Facebook Page.
• Introducing Snapchat. Ayrshare now supports Snapchat. The Snapchat API enables direct publishing of content to both Stories and Spotlight, and getting analytics and history. Stories are temporary posts that disappear after 24 hours, while Spotlight posts are permanent and can help creators and businesses reach a wider audience.
• MCP Server. Connect the Ayrshare API Docs MCP server with your AI agent. By connecting the Ayrshare API documentation MCP server to your AI development tools like Cursor or Claude Desktop, you can give your AI agent direct access to Ayrshare’s documentation.
• Copy a Post. Copy an existing post to another platform. This new endpoint allows you to reuse successful posts across different platforms or with different configurations.
• Developer Dashboard. Two new improvements in the posting flow in the developer dashboard. In addition to uploading media files, you can now also use URLs to post your media. And you can now view the JSON used to publish your post which helps verify the correctness of your JSON.
• User Management. The User endpoint now returns the real-time state of connected social networks, automatically updating whenever users connect or disconnect their social media accounts.
• YouTube. Publishing a video on YouTube now allows disclosure of realistic Altered or Synthetic (A/S) content by setting the containsSyntheticMedia parameter. View docs.
• Facebook. Getting comments on Facebook now returns the direct URL to the specific comment.

​

May 2025

• Introducing Threads. Ayrshare now supports posting and scheduling to Threads, getting analytics, managing comments, and retrieving history.
• Messaging. Messaging is now a standard feature included in the Business Plan. Key features include managing your users’ conversations with correspondents, sending text, image, video, and emoji messages, setting up automated message responses, and webhooks.
• X Analytics. X comment analytics and post analytics now include impression, quote, and bookmark count.
• Linking Page Languages. You can now set the language for the social linking page. Currently supported languages include English, Chinese (Simplified), French, German, and Spanish.
• LinkedIn Posting. Set the LinkedIn post visibility to public, 1st degree connections, or logged-in user.
• LinkedIn Posting. You can now include media in the LinkedIn first comment.
• Instagram Hashtag Search. Search the most popular or recent Instagram posts for a given hashtag to inform your content strategy and identify trending topics.

​

April 2025

• Facebook Ads. Boost Facebook Posts as Ads. The Ayrshare Ads API includes boosting posts, managing ads, tracking performance, and analyzing ad spend.
• User Profile Management. Get a historical log of created and deleted user profiles.
• User Profile Management. In the User Profile section of the web dashboard, if a User Profile is suspended you can now click the “Suspended” badge to get the reason.
• Post History. The history endpoint now allows you to filter by start and end dates.
• Social Linking. We introduced an upgraded X authentication linking. This is a better experience for you and your users.
• Social Linking. Specify the allowed social networks directly when creating the Business Plan linking page using the allowedSocial parameter.
• Instagram Posting. Instagram images now support alt text.
• Bluesky Posting. Bluesky image and video posting now support alt text.
• Pinterest. Add a private note to a Pinterest Pin.
• YouTube Shorts. YouTube Shorts now can be up to 3 minutes long, an increase from the prior limit of 60 seconds.

​

March 2025

• X Analytics. New X social analytics data including like count, add to list count, profile banner image, and more.
• X Rate Limits. The monthly call limits for X have been increased to 100,000 for the Business Plan and 5,000 for the Premium Plan.
• LinkedIn Analytics. LinkedIn personal pages now return a basic set of data including the website url and profile image.
• Facebook Reels. You can now add a thumbnail which is a cover image for a reel video.
• Linking Page. You can set the image height of your custom logo on the social linking page. Specify the height in pixels in your account settings in the web dashboard.
• Linking Page. When linking Facebook and Instagram pages, long lists of pages now have a search field that allows you to filter by the page name or location.
• Team Member Management. Individual team members can now be restricted from accessing other user profiles.
• Media. The upload media endpoint now supports uploads of images and videos up to 30 MB.
• Media. Google Drive and Dropbox share URLs can now be used directly in the mediaUrls post parameter, eliminating the need to create a separate download URL.

​

February 2025

• TikTok Posting. Create a draft video post in the TikTok app. The draft video will be in the notification Inbox in the app, and the user can edit the video before publishing.
• TikTok Analytics. Additional TikTok analytics data fields were added, including demographics such as audience cities and gender. Other new profile fields include profile views and email, address, and bio link clicks.
• Instagram Collaboration. In addition to images and Reels, users can now add collaborators to carousels.
• Instagram Analytics. Instagram post analytics now includes the view count, which is the total number of times your post has been seen.
• Instagram Details. Get additional Instagram details for a user profile, such as used quota and whether the account type is Creator or Business.
• Compression. Compression now supports Brotli for all endpoints, which is faster and offers better compression.
• LinkedIn Comments. LinkedIn comments and replies to comments now support images.
• Reddit Mentions. Reddit posts now support mentions of other users or subreddits.
• Bluesky Posting. Link previews are now supported in Bluesky posts. Include a link in a post, and a preview will automatically be generated.
• Max Pack. Image resizing and conversion now supports converting to WebP.
• Max Pack. Image resizing and watermarking now support positioning the watermark, such as the northeast corner.
• Dashboard. The Ayrshare web dashboard has been refreshed with a new color scheme, enhanced alerts, and improved workflows for a smoother user experience.

​

January 2025

• Bluesky API. Bluesky social media management is now available as the 11th social network that Ayrshare supports.
• LinkedIn Targeting. LinkedIn allows you to target your organic posts to specific groups of users. You can target by countries, industry, job title, and more.
• YouTube Targeting. Block or allow countries and regions for a YouTube video.
• Auto Schedule. Reset an auto-schedule to start scheduling from the current time. This is accomplished by deleting the last scheduled date.
• TikTok Analytics. TikTok social network analytics on a user profile is now available as a historical daily time series.
• TikTok Posting. If the post is completely or mostly created with AI, you can label the post as “Creator labeled as AI-generated”.
• X Posting. X now supports up to 4 videos in a single Tweet.

​

December 2024

• Dashboard. The User Profiles page performance in the web dashboard has been optimized. You will now get a smooth scrolling and loading experience regardless of how many user profiles you have in your account.
• Dashboard. The Posts page in the web dashboard now allows you to include deleted posts in your history timeline. This lets you access, filter, and search deleted posts in the same way as successful posts.
• Deleted Posts. If you or your users have manually deleted a post on a social network, you can mark it as manually deleted in Ayrshare. This will prevent Ayrshare from trying to delete the post in the future and allow you to access a more accurate post history.
• Webhooks. You can now get all the registered webhooks for all your user profiles in a single call.
• Analytics. Instagram post analytics now includes share, followers gained, profile visits, and profile activity counts.
• Comments. TikTok comments now return the name of the person who made the comment.
• Comments. X comments now return the ID of the Tweet the comment was replied to.

​

November 2024

• All New Docs. Check out the new Ayrshare docs. We migrated to a more advanced Documentation platform with many user experience improvements versus the prior version.
• Instagram Analytics. Instagram post analytics now includes the metrics for how many times your reel replayed after the first time and how total times your reel played after the first impression.
• Hashtags. The hashtags endpoint now allows you to specify a language hint to keep the hashtags in the same language as the post.
• X Analytics. X/Twitter Social analytics now returns the most recent Tweet and the Pinned Tweet, if a pinned Tweet has been set.
• Dashboard. In the developer dashboard, Auto-Scheduled Posts are now tagged as “Auto-Schedule”.
• Auto-Schedule. Get all the pending Auto-Scheduled Posts via the API. This returns the list of posts that have been scheduled but not yet published.
• TikTok. You can check if a linked TikTok account is a business account with the Social Analytics endpoint.
• Instagram Comments. The comments endpoint now returns the Instagram top-level post ID to identify the original post.
• History. The history endpoint now returns “paused” scheduled posts. In addition the number of past posts returned was increased to 1000.
• Linking Page. Add a footer and copyright info on the user profile social linking page. Max Pack required.
• Image Conversion. The image resizing endpoint can now convert a PNG or other image type to a JPG as part of the conversion process. Max Pack required.

​

October 2024

• First Comment. Automatically add a first comment to your published social media posts. The first social media posts. The first comment is a great feature that allows you to add more details and context, boost engagement, and set the tone of the conversation.
• Comment Errors. Comment errors also are returned in an errors array field to align with how post errors are returned. how post errors are returned.
• X/Twitter Comments. You can now add media to X/Twitter comments and comment replies, which includes both images and videos.
• Pinterest Analytics. Pinterest metrics were enhanced and now include one full year of analytics data, lifetime now include one full year of analytics data, lifetime comments, and reactions for both images and videos.
• RSS Feeds. When adding an RSS feed you can now select which social networks the article is published. This is available both on the dashboard and via the API.
• Dashboard. In the Ayrshare Dashboard API page there is a new Monthly API Calls overview, which now includes comment API calls as well as post API calls.

• PyPi Package. The Python PyPi package has been updated with new endpoints.

​

September 2024

• Facebook Analytics. The History Get All Posts and Analytics endpoints now return the users who liked a Facebook post. For each user, you can get the user name and the user ID.
• Content Moderation. There is a new Moderation endpoint which checks if the content is harmful or inappropriate. This endpoint supports both text and images.
• LinkedIn Linking. Connecting LinkedIn company pages previously required the user to be a Super Admin on the page. Now Content Admins who manage the LinkedIn company page can connect, allowing them to post, get analytics, and manage comments.
• User Management. The User endpoint now returns both the Page ID and User ID for Facebook and Instagram.
• Dashboard. The web dashboard Post page now shows an icon indicator if the post was published from an rss feed.
• Facebook Reviews. Facebook Reviews now return the profile picture of the reviewer.
• Google Reviews. Google Business Profile Reviews now return all your reviews, even if there are thousands.

​

August 2024

• LinkedIn History. Now you can get the post history for LinkedIn personal pages. Previously only LinkedIn company pages returned history. Requires relinking of LinkedIn with Ayrshare.
• LinkedIn Analytics. There are new data points available for LinkedIn personal and company pages including likedBy and comment details.
• LinkedIn Lookup. The brand endpoint now allows you to look up a person or company. This is useful to see details of who liked one of your posts.
• Facebook History. You can limit the results for a Facebook Page history to only show posts that were published by the page itself. This will filter out all the content that was not published by the page.
• User Profile. The user endpoint now returns a new field with the timestamp of the last time that an API call was made for this user profile.
• X Long Posts. You can publish long posts to Premium X Accounts. Long posts can be up to 25,000 characters long. You can also now get full long Post data including the full body and URL in the long Post body when calling analytics or history.
• Web Dashboard. The post page design was improved and several new content types were added. You can now post Facebook and Instagram Reels or Stories or YouTube Shorts directly from the dashboard.

• Team Management. When you invite a team member you can now see if they accepted the invite or resend the invite from the Dashboard User Profiles page.
• AI Video Titles. The video transcripts now include a suggested title. This is useful for posting to YouTube which requires a title for every video upload. (Max Pack Required)
• Pausing Posts. You can pause and unpause scheduled posts with the post endpoint.
• Sentiment Analysis. The generate endpoint now can generate sentiment analysis for a post or comment to understand if it is negative, positive, or neutral. The result also includes recommendations on how to improve.
• Instagram Analytics. Instagram analytics has been enhanced to return additional demographic data on the engaged audience.
• TikTok Photos. You can now post to TikTok with a photo. Previously a video was required.

​

July 2024

• Post History. Filter the history endpoint based on the social network platform, whether the post was immediate or scheduled, and the status.
• Web Dashboard. The list of user profiles can now be sorted by title or create date and the scheduling modal for posts has been improved.
• Webhooks. Webhooks now automatically retry two times with the same hookId if the initial webhook does not get a success response.
• Reddit. Check if a subreddit exists based on the subreddit name.
• Facebook Stories. A Facebook Story returned via the history endpoint now includes the cover image and direct url to the video.
• Cropping Images. There are new “crop” mode options for resizing an image. Now you can specify the dimensions and starting coordinates to crop an image.
• Demo Social Media Posting App. We released the code for a demo React + Node.js web application that allows users to compose, schedule, and post content to multiple social media platforms simultaneously.
• Multi-Platform Posts. The post endpoint was enhanced to allow you to customize your post content and media for different social networks in a single API call.
• Instagram Analytics. Instagram profile analytics are now available in a daily historical time-series.
• Linkedin Comments. Getting comments from Linkedin now return the comment media link for images or videos.

​

June 2024

• Ayrshare Messaging API. The Ayrshare Messaging Add-On is an optional paid add-on that allows your platform to manage the direct messaging for your users including Facebook Messenger, Instagram Messaging, and X/Twitter Messaging.
• YouTube Comments. You can now delete comments on YouTube by using the YouTube comment ID.
• Auto Hashtags. Introducing the new fully rebuilt auto-hashtag system with more relevant hashtags and no limit on post length. The amount of hashtags has also been increased to allow up to 10 hashtags per post.
• Web Dashboard. The dashboard UI has been updated with the ability to remove all the target social networks in the post page with a single click, and a new code example section in the API Key page.
• User Profile Management. The Profiles endpoint has been enhanced to allow you to filter the results to profiles that have active social accounts or contain certain platforms.

​

May 2024

• Google Business. You can now update your Google Business Profile location data including phone numbers, website URL, map location, and more.
• History Search. With the History endpoint you can now search post IDs across all your user profiles. This is useful if you have a post ID and do not know which user profile posted it.
• User Profile Tags. Add your own tags to a user profile so you can better organize and manage profiles. The web dashboard also allows you to see the tags assigned and search for tags in the User Profiles page.
• YouTube Captions. Add your own custom captions to a YouTube video with a SRT or SVB file.
• NPM Package. An updated Node.js NPM package was released with new endpoints and more detailed documentation. The package was also renamed to social-media-api.
• Facebook Comments. You can now add an image as part of your comment on Facebook.
• Linkedin Comments. Linkedin Comments now return the like count for that specific comment.
• Linkedin Brands. The Brands endpoint for Linkedin data was enhanced with the localized name of the account, company specialities, and company description.
• Disable Comments. You can disable comments on a post on Instagram, LinkedIn, and TikTok. This works on new posts or already published posts.
• Historical Posts. Get historical post data from TikTok on posts that were not posted via Ayrshare.
• Instagram Analytics. New data points available for Instagram Stories including replies, shares, and exit counts.
• AI Generate. Generate social media post text with AI based on one or more images. This can also be used to write an image caption.
• Web Dashboard. For each user profile listed in the dashboard, you can see the connected social networks. Each social network icon can be hovered to see the name on the social network.
• Social Linking. In the web dashboard and in your social linking page, there are now profile images shown next to the page or company name.

​

April 2024

• Auto-Schedule. Enhanced to allow selection of the days of the week for auto-schedule publishing or select specific dates to exclude.
• Facebook Analytics. Facebook Post analytics now includes impressions.
• Instagram Comments. Instagram Get comments response now include additional reply information, such as the username, like count, and hidden status.
• Facebook Page Location. You can now tag a post with a Facebook Page Location.
• Facebook Audience Targeting. When creating a Page post on Facebook, you have the option to limit its visibility to a specific audience using different demographic factors such as age, county, education, and others.
• Linkedin Comments. LinkedIn comments from a company now have additional fields including organization type, company website, and the company description.
• Instagram History. The history for Instagram now returns all the images and videos in a carousel.
• YouTube Analytics. Get a daily breakdown of YouTube analytics at the channel level.

​

March 2024

• Instagram Collaborators. Instagram collaboration allows you to co-author content with other accounts. The public original author can tag another private or public account as a collaborator. Add Instagram collaborators to media posts.
• Google Business Profile. Additional data on Google Business Profile is now available including links to the reviews and map, place Id, and other data. Getting this additional data requires relinking of the Google Business Profile.
• Facebook Page, Instagram, Google Profile Location. On the page linking screen, you can now display the page location for a Facebook Page, Instagram account, and Google Business profile.
• Facebook Profile Analytics. Facebook Social Profile Analytics now returns up to 4 quarters of data. You can set the data to be returned either aggregated or daily.
• Facebook History. Facebook Stories now returned in the Get All History endpoint.
• Social Linking Page. The Ayrshare Social Linking page now supports redirecting to the origin opening tab or window.
• Facebook Reviews. You can now reply to a review on Facebook.
• Instagram Followers. Instagram Get Followers Online has an enhanced UTC Format. This data returns the total historical count of your Instagram followers online per hour, which allows you to optimize posting for maximum engagement.
• Instagram Carousel. Now publish both videos and images in an Instagram carousel. Up to a combined 10 media items can be included.
• TikTok. TikTok captions now support line breaks with the “\n” character.

​

February 2024

• Reviews. Get, reply, and delete reviews on Google Business Profile and Facebook Pages using the new /reviews endpoint.
• Linkedin Comments. Get LinkedIn comments by comment ID for comments done outside of Ayrshare.
• Linkedin Mentions. Linkedin mentions in comments and reply to comments now resolve to the referenced organization handle.
• Public Profile Data. Now you can search for Facebook Pages and Linkedin names in the brand endpoint. Look up users’ or companies’ social media public information, such as followers, profile image, and websites. These users and companies do not need to be a linked Ayrshare user.
• Facebook Comments. The comments endpoint API for Facebook Comments now returns replies directly in the response body.
• Instagram Banned Hashtags. Check for banned hashtags by using the new API endpoint or the new web tool. This is helpful to keep your accounts safe from suspensions or shadow banning.
• Facebook Groups. Facebook has announced that they will be removing API access to Facebook Groups. Learn more.

​

January 2024

• Longer Instagram Videos. Instagram Video posts now support up to 15 minute lengths and 1 GB. This is an increase from the prior 60 seconds and 100 MB.
• Translate Post Text. Choose over 100 different languages to translate your post text. For example, translate English to French or Spanish to German. The source language is automatically detected.
• Error Translation. Error messages can be automatically translated to the language of your choice. This is useful if you want to display the error directly to your user in their preferred language.
• Pinterest Analytics. Additional Pinterest data points are available for get all history including post title, notes, and board id.
• Check Post Length. The Check Post Length endpoint now includes validations for Facebook, Google Business Profile, LinkedIn, Pinterest, and YouTube.
• New User Batch Endpoints. When you need a large data set, the batch endpoints are a great option. You can use the batch endpoints to get json files for all your user profiles and then use the webhook to let you know when the file is ready.
• Linkedin Historical Posts. Get historical data for a Linkedin post published outside of Ayrshare.
• Linkedin Posts Reactions. The Get All Post endpoint for LinkedIn now returns reactions for the post, such as Likes, Praise, Maybe, and Appreciation.
• Last API Call Time. Access the time that you last used the API key in the web dashboard in the API Key section.
• Ayrshare Dashboard History. The web dashboard now allows you to load all your historical posts or webhook logs with a new “Load more” button.
• Webhook Errors. View the error rate of your webhooks to see the percentage of success vs error responses.

​

Older Updates

Check the Update Archive to see older updates.