> ## Documentation Index > Fetch the complete documentation index at: https://www.ayrshare.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Latest Updates > See what's new at Ayrshare. Check out our changelog for great new features. [Follow us on X](https://twitter.com/intent/user?screen_name=ayrshare), listen to our [Social Media API Podcast](https://ayrshare.podbean.com/), or sign up for our [Newsletter](https://dashboard.mailerlite.com/forms/42719/54642298519029076/share) for the latest updates. ## 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 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 - 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](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](/apis/post/social-networks/youtube#youtube-thumbnails) and the new [YouTube Thumbnail Not Applied (Unverified Channel)](/help-center/technical-support/youtube_thumbnail_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](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](/apis/comments/delete-comments) and [Comments Overview](/apis/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 per active conversation on Launch and Business plans (Premium remains a flat $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](/apis/profiles/create-profile) and [Update Profile](/apis/profiles/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](/apis/ads/facebook/boost-post) 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 Business / 5,000 Enterprise), and a cursor-paginated activity log. Available on 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) now return relink: true and retryAvailable: true with a remediation message instructing the user to unlink and relink the Instagram account granting all permissions. 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](/errors/errors-ayrshare) 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](/apis/post/social-networks/instagram) and [error codes](/errors/errors-ayrshare).

## 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](/errors/errors-ayrshare).
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](/errors/errors-ayrshare) and the [Instagram Post API](/apis/post/social-networks/instagram).
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](/dashboard/connect-social-accounts/x-twitter-byo-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](/apis/comments/post-comment) and [Reply to a Comment](/apis/comments/reply-to-comment) endpoints. Includes LinkedIn server-side resolution details and links to platform-specific mention syntax.
X/Twitter Paginated Messages. The [Get Messages](/apis/messages/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](/media-guidelines/overview) for full details.
X/Twitter Messages BYO Key Support. [Get Messages](/apis/messages/get-messages) and [Send Message](/apis/messages/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](/apis/post/social-networks/x-twitter) 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](/apis/links/update-short-link) 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](/apis/history/history-platform) and [/history/instagram](/apis/history/history-platform) 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](/dashboard/connect-social-accounts/x-twitter-byo-keys), 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](/apis/analytics/social-by-id) endpoint.
History Pagination. Added pagination support to the [posts history for a platform](/apis/history/history-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](/apis/messages/overview) and [Max Pack](/additional/maxpack) — you won't be charged until the end of the free trial period.
Improved Error Messages. Added additional detail to [X/Twitter](/apis/post/social-networks/x-twitter) and [LinkedIn](/apis/post/social-networks/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](/apis/comments/get-comments) endpoint.
Python SDK. Updated our [Python SDK](https://pypi.org/project/social-post-api/) with the latest features and improvements.
X/Twitter Webhook URL. A new ayrshareUrl field is now included in [Direct Message Event webhook](/apis/webhooks/actions#direct-message-event) payload, providing an unauthenticated URL for convenience.
Status Page Slack Integration. You can link updates from our [Status Page](https://status.ayrshare.com) 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](/apis/links/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](/apis/messages/get-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](/additional/mcp-server)! Connect your AI tools directly to the Ayrshare API.
Self-Serve Signup. Added a new [self-serve signup](https://www.ayrshare.com/pricing/) 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](/apis/post/social-networks/x-twitter#video-thumbnail) 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](/apis/post/social-networks/instagram) to 5 to align with new guidelines published by Instagram.
Bluesky Video Duration. Bluesky video media duration limit has been adjusted to [three minutes](/media-guidelines/bluesky#video) 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](/apis/history/history-platform) 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](/apis/analytics/post) and [platform history](/apis/history/history-platform) 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](/apis/analytics/post) including mediaView, mediaViewIsFromAds, and mediaViewIsFromFollowers to replace [deprecated impression metrics](/whatsnew/upcoming-api-changes#november-14%2C-2025).
Bluesky Comments. Improved support for [Bluesky comment retrieval](/apis/comments/get-comments) with proper handling of AT Protocol-style post and comment IDs.
Threads Linking. Enhanced [Threads account linking](/dashboard/connect-social-accounts/threads) 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](/apis/analytics/post) 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](/apis/analytics/social) fields added: pageFollows, pageMediaView, pageMediaViewIsFromAds, and pageMediaViewIsFromFollowers with both aggregate and daily breakdown support.
Instagram Analytics. [Instagram social analytics](/apis/analytics/social) viewsCount and reachCount metrics are now supported with both direct Instagram Login and Facebook-linked accounts.
LinkedIn Mentions. Fixed handling of [LinkedIn mentions](/apis/post/social-networks/linkedin#linkedin-mentions) to properly distinguish between mentioning organizations versus individuals.
Dashboard Improvements. The [Ayrshare web dashboard](https://app.ayrshare.com) 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](/apis/webhooks/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](/apis/ads/facebook/boost-post#param-locations) when boosting Facebook posts.
LinkedIn Video Thumbnails. The [LinkedIn history endpoint](/apis/history/history-platform) now returns the thumbnailUrl for video posts, making it easier to display video previews in your application.
Reddit Post Analytics. [Reddit post analytics](/apis/analytics/post) 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](/apis/history/history-platform) for accounts with many posts.
Facebook Ads. The [Facebook ads history endpoint](/apis/ads/facebook/get-ad-history) now includes clarification on which ads are returned based on the campaign structure.
Instagram Collaboration. Added documentation clarifying that [accepted collaboration posts](/apis/history/history-platform) may not return from the platform history endpoint due to Instagram API limitations.

## September 2025