The following changes to the API will be effective on the date specified. Please review carefully for any potentially breaking changes. See What’s New for all new features.
​
September 1, 2025
  • Starting September 1, 2025, the get comments endpoint for Instagram will no longer include the text field in reply objects. Use the comment field instead to access reply content.
​
June 1, 2025
  • X (Twitter) get comments endpoint will move the user public metrics to the new publicMetrics object. The following fields will be moved from the top level to the publicMetrics object:
    • followersCount
    • followingCount
    • tweetCount
    • listedCount
    • mediaCount
  • Facebook will be deprecating the following fields for GET analytics/social:
    • pageVideoViews10S
    • pageVideoViews10SAutoplayed
    • pageVideoViews10SClickToPlay
    • pageVideoViews10SOrganic
    • pageVideoViews10SPaid
    • pageVideoViews10SRepeat
    • pageVideoViews10SUnique
​
May 7, 2025
  • YouTube has deprecated the setting allowed and blocked regions. You can still add in the allowed and blocked regions to the post endpoint, but they will be ignored.
​
April 20, 2025
  • The following metrics for Instagram post analytics will be deprecated:REELS:
    • playsCount
    • clipsReplaysCount
    • igReelsAggregatedAllPlaysCount
    FEED/STORY:
    • impressionsCount
  • The history endpoint will enforce the cache for 1 minute if the limit is greater than the default value of 25.
​
March 1, 2025
The get comments endpoint for TikTok will standardize field names to match other social networks.
  • The field replyList will be renamed to replies and profileImage will be renamed to profileImageUrl.
  • Both new field names are already available and can be used in your integration.
  • TikTok as the following updates:
    • social analytics endpoint: The following changes are coming: • The durationAverage field will be deprecated and removed. • Due to TikTok API limitations, the fields shareCountTotal, viewCountTotal and commentCountTotal will now only return totals for the past 60 days instead of all-time totals. • To start using the 60-day totals now, add period60Days: true to your API request body Note: Using this parameter will significantly improve response times.
    • history platform and post analytics endpoints: The undocumented fields caption, comments, shares, likes, shareUrl, and itemsId will be removed - the fields post, commentsCount, sharesCount, likesCount, postUrl, and id should be used instead.
​
February 1, 2025
The /user endpoint is changing how it reports API usage:
  • The monthlyApiCalls field will be expanded to count all API calls (posts, comments, analytics, etc.).
  • For post-specific counts, use the new monthlyPostCount field.
  • The monthlyApiCallsQuota field will be deprecated and replaced by the new monthlyPostQuota field.
​
January 5, 2025
  • Meta is deprecating the videoViews field on the Instagram post analytics endpoint.
  • Additionally, the emailContactsCount, getDirectionClicks, profileViewsCount, textMessageClicks, websiteClicksCount, and phoneCallClicksCount fields will be removed from the Instagram social analytics endpoint.
  • These fields will be removed on January 5, 2025.
​
December 15, 2024
  • For enhanced security, we will prevent Profile Keys from being used as API Keys. If you attempt to use a Profile Key in place of the API Key, the system will return an error. See here on how to properly use a Profile Key.
​
November 15, 2024
  • We’ve updated how errors for TikTok scheduled webhooks are reported. These errors will now appear in the errors array, consistent with our error handling for other scheduled webhook types. Note, the current top-level errors will still be returned, but we encourage use of the errors array.
  • The history endpoint will now return responses as objects by default. The objResponse parameter will be set to true automatically.
  • Get All History LinkedIn will return an array for the mediaUrls object. Previously an object was returned if only one media item and an array if multiple media items. Now an array will always be returned even if only a single media item. If you need the previous behavior, you can use the objResponse: false query parameter.
​
October 7, 2024
  • The media endpoint will no longer return url_1080. If you do need to resize an image, please see the resize endpoint.
​
September 16, 2024
​
June 3, 2024
  • The new linked shortener system will replace the shortener endpoint, which has been deprecated by Google. The new link shortener requires the add-on Max Pack.
  • Link shortening will be off (false) by default. To automatically shorten links use shortenLinks: true in the post endpoint call, which uses the new link endpoint.
​
April 22, 2024
  • Meta will be deprecating their Facebook Groups API. Please see the announcement.
​
April 16, 2024
  • Instagram has clarified the time period of the online followers data set. Please see here for details.
​
April 1, 2024
  • Reply to comment with comment ID default response will be an object as listed in the docs instead of an Array. You may use the objResponse parameter set to boolean false if wish to keep an Array response.
​
January 25, 2024
​
December 8, 2023
  • The /history/instagram endpoint fields caption, message, createdTime and timestamp fields were deprecated on April 1, 2023 and will be removed. Please use the post and created fields.
  • The /history/linkedin endpoint field mediaUrls will be returned as an array instead of an object to support multiple images. You can force the array being returned now by including the LinkedIn query parameter ?multiMedia=true. Please note, before December 1, 2023 the multiMedia query parameter must be used to return media with multiple images. After December 1, 2023 multiple images will be returned by default.
  • The Scheduled Action TikTok webhook will have the String platform deprecated. Please use the platforms array field as is done for other Scheduled Action webhooks.
  • The delete comment docs have been corrected to align with the correct return.
  • The TikTok commentId field will be replaced with the id field to align with the standard comment delete format.
  • The Twitter delete comment return will no longer contain a posts array so the return aligns with the standard comment delete format. The new return will be as follows:
​
October 18, 2023
​
May 30, 2023
  • We have upgrade to Twitter’s new API version 2. Twitter has deprecated a few fields in Version 2, which affects the /analytics/social and getAllHistory endpoints. These following fields will still be returned until September 1, 2023, but will have a zero or empty string value.
​
May 8, 2023
  • We’re excited to launch TikTok direct publishing, comment management, and advanced analytics. Your users will no longer need to open their TikTok mobile app to post and enter caption text. Now after sending via Ayrshare, the TikTok video and caption is directly published.
  • We’re also introducing adding, getting, and deleting TikTok comments + demographic analytics data.
  • Your user will need to unlink and relink their TikTok account to enable direct publishing. Existing connections will continue with the indirect method and require the TikTok mobile app to publish.
​
February 17, 2023
  • Google Business Profile has changed the available social analytics data available. The new fields available are the following. Previous fields will still be present, but with a zero value and fully removed on March 17, 2023.
​
October 1, 2022
  • Get All Posts descriptions, text, message fields standardized to post field.
​
September 12, 2022
  • TikTok fields deprecated: shareUrl. Use postUrl instead.
​
June 17, 2022
  • For all history endpoints the fields createdAt, createdTime, and timestamp will be replaced by the created field which returns the creation time in UTC format.
  • The scheduleDate field will no longer return an Object by a String containing the schedule time in UTC format.
  • The undocumented created_date field on /history will be removed. Use created instead.
​
April 22, 2022
  • Analytics on a Facebook post returns reactions as an object in the following format.
​
April 1, 2022
  • History by default will return the last 20 posts. Up to 500 can be returned with the lastRecords parameter.